[jira] [Updated] (CASSANDRASC-124) Fix wait time acquired in SidecarRateLimiter
[ https://issues.apache.org/jira/browse/CASSANDRASC-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-124: - Test and Documentation Plan: Tested with unit tests Status: Patch Available (was: Open) Patch: [https://github.com/apache/cassandra-sidecar/pull/115] > Fix wait time acquired in SidecarRateLimiter > > > Key: CASSANDRASC-124 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-124 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Labels: pull-request-available > > Currently the wait time retrieved is a future timestamp instead of exact > micros to wait. Hence wait time header is never sent from `FileStreamer` and > only 429s are sent when throttled. In this patch, we calculate the wait time > separately. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-124) Fix wait time acquired in SidecarRateLimiter
[ https://issues.apache.org/jira/browse/CASSANDRASC-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-124: - Bug Category: Parent values: Correctness(12982) Complexity: Low Hanging Fruit Component/s: Rest API Discovered By: User Report Reviewers: Francisco Guerrero, Yifan Cai Severity: Low Assignee: Saranya Krishnakumar Status: Open (was: Triage Needed) Tested with unit tests > Fix wait time acquired in SidecarRateLimiter > > > Key: CASSANDRASC-124 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-124 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Labels: pull-request-available > > Currently the wait time retrieved is a future timestamp instead of exact > micros to wait. Hence wait time header is never sent from `FileStreamer` and > only 429s are sent when throttled. In this patch, we calculate the wait time > separately. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRASC-124) Fix wait time acquired in SidecarRateLimiter
Saranya Krishnakumar created CASSANDRASC-124: Summary: Fix wait time acquired in SidecarRateLimiter Key: CASSANDRASC-124 URL: https://issues.apache.org/jira/browse/CASSANDRASC-124 Project: Sidecar for Apache Cassandra Issue Type: Bug Reporter: Saranya Krishnakumar Currently the wait time retrieved is a future timestamp instead of exact micros to wait. Hence wait time header is never sent from `FileStreamer` and only 429s are sent when throttled. In this patch, we calculate the wait time separately. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRASC-117) Record additional metrics for improved observability
[ https://issues.apache.org/jira/browse/CASSANDRASC-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838267#comment-17838267 ] Saranya Krishnakumar commented on CASSANDRASC-117: -- Latest Green CI [https://app.circleci.com/pipelines/github/sarankk/cassandra-sidecar/277] > Record additional metrics for improved observability > > > Key: CASSANDRASC-117 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-117 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Labels: pull-request-available > > With this patch increasing the number of metrics captured on sidecar side for > improved observability. This includes, capturing resource level metrics, > Cassandra instance health metrics, SSTable import metrics etc. Also as part > of this patch, migrating existing metrics to Dropwizard registry. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRASC-117) Record additional metrics for improved observability
[ https://issues.apache.org/jira/browse/CASSANDRASC-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837017#comment-17837017 ] Saranya Krishnakumar commented on CASSANDRASC-117: -- Latest Green CI [https://app.circleci.com/pipelines/github/sarankk/cassandra-sidecar/263] > Record additional metrics for improved observability > > > Key: CASSANDRASC-117 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-117 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Labels: pull-request-available > > With this patch increasing the number of metrics captured on sidecar side for > improved observability. This includes, capturing resource level metrics, > Cassandra instance health metrics, SSTable import metrics etc. Also as part > of this patch, migrating existing metrics to Dropwizard registry. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRASC-115) Add FilteringMetricRegistry to allow filtering of metrics
[ https://issues.apache.org/jira/browse/CASSANDRASC-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835937#comment-17835937 ] Saranya Krishnakumar commented on CASSANDRASC-115: -- Latest Green CI [https://app.circleci.com/pipelines/github/sarankk/cassandra-sidecar/241] > Add FilteringMetricRegistry to allow filtering of metrics > - > > Key: CASSANDRASC-115 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-115 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Labels: pull-request-available > > This patch is to add FilteringMetricRegistry to filter out metrics by adding > filters to sidecar.yaml file. This is useful in cases when metrics recorded > by sidecar are high is number and for fine grain control over metrics exposed > from sidecar -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-117) Record additional metrics for improved observability
[ https://issues.apache.org/jira/browse/CASSANDRASC-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-117: - Authors: Saranya Krishnakumar Test and Documentation Plan: Tested with unit tests Status: Patch Available (was: Open) Patch: [https://github.com/apache/cassandra-sidecar/pull/111], Green CI [https://app.circleci.com/pipelines/github/sarankk/cassandra-sidecar/229] > Record additional metrics for improved observability > > > Key: CASSANDRASC-117 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-117 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > With this patch increasing the number of metrics captured on sidecar side for > improved observability. This includes, capturing resource level metrics, > Cassandra instance health metrics, SSTable import metrics etc. Also as part > of this patch, migrating existing metrics to Dropwizard registry. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-117) Record additional metrics for improved observability
[ https://issues.apache.org/jira/browse/CASSANDRASC-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-117: - Change Category: Operability Complexity: Normal Component/s: Rest API Reviewers: Francisco Guerrero, Yifan Cai Assignee: Saranya Krishnakumar Status: Open (was: Triage Needed) > Record additional metrics for improved observability > > > Key: CASSANDRASC-117 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-117 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > With this patch increasing the number of metrics captured on sidecar side for > improved observability. This includes, capturing resource level metrics, > Cassandra instance health metrics, SSTable import metrics etc. Also as part > of this patch, migrating existing metrics to Dropwizard registry. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRASC-117) Record additional metrics for improved observability
Saranya Krishnakumar created CASSANDRASC-117: Summary: Record additional metrics for improved observability Key: CASSANDRASC-117 URL: https://issues.apache.org/jira/browse/CASSANDRASC-117 Project: Sidecar for Apache Cassandra Issue Type: Improvement Reporter: Saranya Krishnakumar With this patch increasing the number of metrics captured on sidecar side for improved observability. This includes, capturing resource level metrics, Cassandra instance health metrics, SSTable import metrics etc. Also as part of this patch, migrating existing metrics to Dropwizard registry. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-115) Add FilteringMetricRegistry to allow filtering of metrics
[ https://issues.apache.org/jira/browse/CASSANDRASC-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-115: - Test and Documentation Plan: Tested with Unit tests Status: Patch Available (was: Open) Patch: [https://github.com/apache/cassandra-sidecar/pull/109,|https://github.com/apache/cassandra-sidecar/pull/109] Green CI [https://app.circleci.com/pipelines/github/sarankk/cassandra-sidecar/210] > Add FilteringMetricRegistry to allow filtering of metrics > - > > Key: CASSANDRASC-115 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-115 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Labels: pull-request-available > > This patch is to add FilteringMetricRegistry to filter out metrics by adding > filters to sidecar.yaml file. This is useful in cases when metrics recorded > by sidecar are high is number and for fine grain control over metrics exposed > from sidecar -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-115) Add FilteringMetricRegistry to allow filtering of metrics
[ https://issues.apache.org/jira/browse/CASSANDRASC-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-115: - Change Category: Operability Complexity: Normal Component/s: Rest API Assignee: Saranya Krishnakumar Status: Open (was: Triage Needed) > Add FilteringMetricRegistry to allow filtering of metrics > - > > Key: CASSANDRASC-115 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-115 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > This patch is to add FilteringMetricRegistry to filter out metrics by adding > filters to sidecar.yaml file. This is useful in cases when metrics recorded > by sidecar are high is number and for fine grain control over metrics exposed > from sidecar -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRASC-115) Add FilteringMetricRegistry to allow filtering of metrics
Saranya Krishnakumar created CASSANDRASC-115: Summary: Add FilteringMetricRegistry to allow filtering of metrics Key: CASSANDRASC-115 URL: https://issues.apache.org/jira/browse/CASSANDRASC-115 Project: Sidecar for Apache Cassandra Issue Type: Improvement Reporter: Saranya Krishnakumar This patch is to add FilteringMetricRegistry to filter out metrics by adding filters to sidecar.yaml file. This is useful in cases when metrics recorded by sidecar are high is number and for fine grain control over metrics exposed from sidecar -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-105) RestoreSliceTask could be stuck due to missing exception handling
[ https://issues.apache.org/jira/browse/CASSANDRASC-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-105: - Authors: Saranya Krishnakumar Test and Documentation Plan: Unit tests Status: Patch Available (was: Open) patch: [https://github.com/apache/cassandra-sidecar/pull/107] > RestoreSliceTask could be stuck due to missing exception handling > - > > Key: CASSANDRASC-105 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-105 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Yifan Cai >Assignee: Saranya Krishnakumar >Priority: Normal > > In RestoreSliceTask, there are a few places could throw exceptions but > missing exception handling in call-sites. As a result, the RetoreSliceTask > never fulfill the promise, i.e. the task is stuck. > For example, downloadObjectIfAbsent could throw instead of returning a > future, in such case, the task will never fail or complete. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-105) RestoreSliceTask could be stuck due to missing exception handling
[ https://issues.apache.org/jira/browse/CASSANDRASC-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-105: - Bug Category: Parent values: Correctness(12982) Complexity: Normal Discovered By: User Report Reviewers: Francisco Guerrero, Yifan Cai Severity: Normal Status: Open (was: Triage Needed) > RestoreSliceTask could be stuck due to missing exception handling > - > > Key: CASSANDRASC-105 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-105 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Yifan Cai >Assignee: Saranya Krishnakumar >Priority: Normal > > In RestoreSliceTask, there are a few places could throw exceptions but > missing exception handling in call-sites. As a result, the RetoreSliceTask > never fulfill the promise, i.e. the task is stuck. > For example, downloadObjectIfAbsent could throw instead of returning a > future, in such case, the task will never fail or complete. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-111) Improve observability in Sidecar
[ https://issues.apache.org/jira/browse/CASSANDRASC-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-111: - Description: Currently we capture minimal metrics in Sidecar, through this patch we want to improve observability in Sidecar. For this we want to record more metrics in Sidecar with Dropwizard. Introduce setup changes needed for capturing sidecar metrics through Dropwizard. Some of the metric kinds we will capture through this patch are, HTTP metrics like number of requests created per route, response time taken endpoint wise. Capture metrics per Cassandra instance maintained by Sidecar, such as, instance specific restore metrics, instance specific stream and upload metrics. We will also turn on registering, server route metrics emitted by Vert.x. was: Currently we capture minimal metrics in Sidecar, through this patch we want to improve observability in Sidecar. For this we want to record more metrics in Sidecar with Dropwizard. Introduce setup changes needed for capturing sidecar metrics through Dropwizard. Remove existing metric interfaces with default methods, in place capture metrics with Dropwizard APIs. Some of the metric kinds we will capture through this patch are, HTTP metrics like number of requests created per route, response time taken endpoint wise. Capture metrics per Cassandra instance maintained by Sidecar, such as, instance specific restore metrics, instance specific stream and upload metrics. We will also turn on registering, server route specific metrics emitted by Vert.x. > Improve observability in Sidecar > - > > Key: CASSANDRASC-111 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-111 > Project: Sidecar for Apache Cassandra > Issue Type: Task > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Labels: pull-request-available > > Currently we capture minimal metrics in Sidecar, through this patch we want > to improve observability in Sidecar. > For this we want to record more metrics in Sidecar with Dropwizard. Introduce > setup changes needed for capturing sidecar metrics through Dropwizard. > Some of the metric kinds we will capture through this patch are, HTTP metrics > like number of requests created per route, response time taken endpoint wise. > Capture metrics per Cassandra instance maintained by Sidecar, such as, > instance specific restore metrics, instance specific stream and upload > metrics. We will also turn on registering, server route metrics emitted by > Vert.x. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19424) Add certificate expiry check to start up validations done in Cassandra Analytics library
[ https://issues.apache.org/jira/browse/CASSANDRA-19424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRA-19424: - Test and Documentation Plan: unit tests Status: Patch Available (was: In Progress) > Add certificate expiry check to start up validations done in Cassandra > Analytics library > > > Key: CASSANDRA-19424 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19424 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Time Spent: 40m > Remaining Estimate: 0h > > Want to add certificate expiry check to startup Keystore validations done in > Cassandra Analytics library. This is to fail fast if user certificates are > expired. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19424) Add certificate expiry check to start up validations done in Cassandra Analytics library
[ https://issues.apache.org/jira/browse/CASSANDRA-19424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17824160#comment-17824160 ] Saranya Krishnakumar commented on CASSANDRA-19424: -- Green CI after addressing comments [https://app.circleci.com/pipelines/github/sarankk/cassandra-analytics/53] > Add certificate expiry check to start up validations done in Cassandra > Analytics library > > > Key: CASSANDRA-19424 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19424 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Time Spent: 20m > Remaining Estimate: 0h > > Want to add certificate expiry check to startup Keystore validations done in > Cassandra Analytics library. This is to fail fast if user certificates are > expired. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-111) Improve observability in Sidecar
[ https://issues.apache.org/jira/browse/CASSANDRASC-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-111: - Authors: Saranya Krishnakumar Test and Documentation Plan: Patch: [https://github.com/apache/cassandra-sidecar/pull/102]. Tested with unit tests. Status: Patch Available (was: Open) > Improve observability in Sidecar > - > > Key: CASSANDRASC-111 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-111 > Project: Sidecar for Apache Cassandra > Issue Type: Task > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > Currently we capture minimal metrics in Sidecar, through this patch we want > to improve observability in Sidecar. > For this we want to record more metrics in Sidecar with Dropwizard. Introduce > setup changes needed for capturing sidecar metrics through Dropwizard. Remove > existing metric interfaces with default methods, in place capture metrics > with Dropwizard APIs. > Some of the metric kinds we will capture through this patch are, HTTP metrics > like number of requests created per route, response time taken endpoint wise. > Capture metrics per Cassandra instance maintained by Sidecar, such as, > instance specific restore metrics, instance specific stream and upload > metrics. We will also turn on registering, server route specific metrics > emitted by Vert.x. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-111) Improve observability in Sidecar
[ https://issues.apache.org/jira/browse/CASSANDRASC-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-111: - Test and Documentation Plan: Tested with unit tests. (was: Patch: [https://github.com/apache/cassandra-sidecar/pull/102]. Tested with unit tests.) > Improve observability in Sidecar > - > > Key: CASSANDRASC-111 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-111 > Project: Sidecar for Apache Cassandra > Issue Type: Task > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > Currently we capture minimal metrics in Sidecar, through this patch we want > to improve observability in Sidecar. > For this we want to record more metrics in Sidecar with Dropwizard. Introduce > setup changes needed for capturing sidecar metrics through Dropwizard. Remove > existing metric interfaces with default methods, in place capture metrics > with Dropwizard APIs. > Some of the metric kinds we will capture through this patch are, HTTP metrics > like number of requests created per route, response time taken endpoint wise. > Capture metrics per Cassandra instance maintained by Sidecar, such as, > instance specific restore metrics, instance specific stream and upload > metrics. We will also turn on registering, server route specific metrics > emitted by Vert.x. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-111) Improve observability in Sidecar
[ https://issues.apache.org/jira/browse/CASSANDRASC-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-111: - Change Category: Operability Complexity: Normal Component/s: Rest API Reviewers: Francisco Guerrero, Yifan Cai Assignee: Saranya Krishnakumar Status: Open (was: Triage Needed) > Improve observability in Sidecar > - > > Key: CASSANDRASC-111 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-111 > Project: Sidecar for Apache Cassandra > Issue Type: Task > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > Currently we capture minimal metrics in Sidecar, through this patch we want > to improve observability in Sidecar. > For this we want to record more metrics in Sidecar with Dropwizard. Introduce > setup changes needed for capturing sidecar metrics through Dropwizard. Remove > existing metric interfaces with default methods, in place capture metrics > with Dropwizard APIs. > Some of the metric kinds we will capture through this patch are, HTTP metrics > like number of requests created per route, response time taken endpoint wise. > Capture metrics per Cassandra instance maintained by Sidecar, such as, > instance specific restore metrics, instance specific stream and upload > metrics. We will also turn on registering, server route specific metrics > emitted by Vert.x. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRASC-111) Improve observability in Sidecar
Saranya Krishnakumar created CASSANDRASC-111: Summary: Improve observability in Sidecar Key: CASSANDRASC-111 URL: https://issues.apache.org/jira/browse/CASSANDRASC-111 Project: Sidecar for Apache Cassandra Issue Type: Task Reporter: Saranya Krishnakumar Currently we capture minimal metrics in Sidecar, through this patch we want to improve observability in Sidecar. For this we want to record more metrics in Sidecar with Dropwizard. Introduce setup changes needed for capturing sidecar metrics through Dropwizard. Remove existing metric interfaces with default methods, in place capture metrics with Dropwizard APIs. Some of the metric kinds we will capture through this patch are, HTTP metrics like number of requests created per route, response time taken endpoint wise. Capture metrics per Cassandra instance maintained by Sidecar, such as, instance specific restore metrics, instance specific stream and upload metrics. We will also turn on registering, server route specific metrics emitted by Vert.x. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19442) Update access of ClearSnapshotStrategy
[ https://issues.apache.org/jira/browse/CASSANDRA-19442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRA-19442: - Test and Documentation Plan: Tested with unit tests Status: Patch Available (was: Open) > Update access of ClearSnapshotStrategy > -- > > Key: CASSANDRA-19442 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19442 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > Want to update access of ClearSnapshotStrategy added to Cassandra Analytics > library to allow setting TTL for snapshots created by bulk reader. Currently > the access of the class is package private, for plugging in custom > implementation, we need access outside the package. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19442) Update access of ClearSnapshotStrategy
[ https://issues.apache.org/jira/browse/CASSANDRA-19442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820876#comment-17820876 ] Saranya Krishnakumar commented on CASSANDRA-19442: -- Green CI [https://app.circleci.com/pipelines/github/sarankk/cassandra-analytics/52] > Update access of ClearSnapshotStrategy > -- > > Key: CASSANDRA-19442 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19442 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > Want to update access of ClearSnapshotStrategy added to Cassandra Analytics > library to allow setting TTL for snapshots created by bulk reader. Currently > the access of the class is package private, for plugging in custom > implementation, we need access outside the package. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19442) Update access of ClearSnapshotStrategy
[ https://issues.apache.org/jira/browse/CASSANDRA-19442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRA-19442: - Change Category: Code Clarity Complexity: Low Hanging Fruit Component/s: Analytics Library Reviewers: Francisco Guerrero, Yifan Cai Assignee: Saranya Krishnakumar Status: Open (was: Triage Needed) Patch: [https://github.com/apache/cassandra-analytics/pull/42]. > Update access of ClearSnapshotStrategy > -- > > Key: CASSANDRA-19442 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19442 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > Want to update access of ClearSnapshotStrategy added to Cassandra Analytics > library to allow setting TTL for snapshots created by bulk reader. Currently > the access of the class is package private, for plugging in custom > implementation, we need access outside the package. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19442) Update access of ClearSnapshotStrategy
Saranya Krishnakumar created CASSANDRA-19442: Summary: Update access of ClearSnapshotStrategy Key: CASSANDRA-19442 URL: https://issues.apache.org/jira/browse/CASSANDRA-19442 Project: Cassandra Issue Type: Task Reporter: Saranya Krishnakumar Want to update access of ClearSnapshotStrategy added to Cassandra Analytics library to allow setting TTL for snapshots created by bulk reader. Currently the access of the class is package private, for plugging in custom implementation, we need access outside the package. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-108) Update access of ClearSnapshotStrategy
[ https://issues.apache.org/jira/browse/CASSANDRASC-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-108: - Resolution: Not A Problem Status: Resolved (was: Open) > Update access of ClearSnapshotStrategy > -- > > Key: CASSANDRASC-108 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-108 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > Want to update access of ClearSnapshotStrategy added to allow setting TTL for > snapshots created by bulk reader. Currently the access of the class is > package private, for plugging in custom implementation, we need access > outside the package. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRASC-108) Update access of ClearSnapshotStrategy
[ https://issues.apache.org/jira/browse/CASSANDRASC-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820867#comment-17820867 ] Saranya Krishnakumar commented on CASSANDRASC-108: -- This is JIRA related to Cassandra Analytics project. Hence closing it here > Update access of ClearSnapshotStrategy > -- > > Key: CASSANDRASC-108 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-108 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > Want to update access of ClearSnapshotStrategy added to allow setting TTL for > snapshots created by bulk reader. Currently the access of the class is > package private, for plugging in custom implementation, we need access > outside the package. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-108) Update access of ClearSnapshotStrategy
[ https://issues.apache.org/jira/browse/CASSANDRASC-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-108: - Change Category: Code Clarity Complexity: Low Hanging Fruit Component/s: Configuration Reviewers: Francisco Guerrero, Yifan Cai Assignee: Saranya Krishnakumar Status: Open (was: Triage Needed) > Update access of ClearSnapshotStrategy > -- > > Key: CASSANDRASC-108 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-108 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > Want to update access of ClearSnapshotStrategy added to allow setting TTL for > snapshots created by bulk reader. Currently the access of the class is > package private, for plugging in custom implementation, we need access > outside the package. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRASC-108) Update access of ClearSnapshotStrategy
[ https://issues.apache.org/jira/browse/CASSANDRASC-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820227#comment-17820227 ] Saranya Krishnakumar commented on CASSANDRASC-108: -- Patch: [https://github.com/apache/cassandra-analytics/pull/42]. Green circle CI [https://app.circleci.com/pipelines/github/sarankk/cassandra-analytics/49] > Update access of ClearSnapshotStrategy > -- > > Key: CASSANDRASC-108 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-108 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement >Reporter: Saranya Krishnakumar >Priority: Normal > > Want to update access of ClearSnapshotStrategy added to allow setting TTL for > snapshots created by bulk reader. Currently the access of the class is > package private, for plugging in custom implementation, we need access > outside the package. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19424) Add certificate expiry check to start up validations done in Cassandra Analytics library
[ https://issues.apache.org/jira/browse/CASSANDRA-19424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820149#comment-17820149 ] Saranya Krishnakumar commented on CASSANDRA-19424: -- Green CI: [https://app.circleci.com/pipelines/github/sarankk/cassandra-analytics/46] > Add certificate expiry check to start up validations done in Cassandra > Analytics library > > > Key: CASSANDRA-19424 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19424 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > Want to add certificate expiry check to startup Keystore validations done in > Cassandra Analytics library. This is to fail fast if user certificates are > expired. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19424) Add certificate expiry check to start up validations done in Cassandra Analytics library
[ https://issues.apache.org/jira/browse/CASSANDRA-19424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRA-19424: - Change Category: Code Clarity Complexity: Low Hanging Fruit Component/s: Analytics Library Reviewers: Francisco Guerrero, Yifan Cai Assignee: Saranya Krishnakumar Status: Open (was: Triage Needed) Tested with unit test. Patch: [https://github.com/apache/cassandra-analytics/pull/43] > Add certificate expiry check to start up validations done in Cassandra > Analytics library > > > Key: CASSANDRA-19424 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19424 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > Want to add certificate expiry check to startup Keystore validations done in > Cassandra Analytics library. This is to fail fast if user certificates are > expired. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19424) Add certificate expiry check to start up validations done in Cassandra Analytics library
Saranya Krishnakumar created CASSANDRA-19424: Summary: Add certificate expiry check to start up validations done in Cassandra Analytics library Key: CASSANDRA-19424 URL: https://issues.apache.org/jira/browse/CASSANDRA-19424 Project: Cassandra Issue Type: Improvement Reporter: Saranya Krishnakumar Want to add certificate expiry check to startup Keystore validations done in Cassandra Analytics library. This is to fail fast if user certificates are expired. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRASC-109) Add certificate expiry check to start up validations done in Cassandra Analytics library
[ https://issues.apache.org/jira/browse/CASSANDRASC-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819924#comment-17819924 ] Saranya Krishnakumar commented on CASSANDRASC-109: -- This issue belongs in Cassandra Analytics project, hence closing it. > Add certificate expiry check to start up validations done in Cassandra > Analytics library > > > Key: CASSANDRASC-109 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-109 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement >Reporter: Saranya Krishnakumar >Priority: Normal > > Want to add certificate expiry check to startup Keystore validations done in > Cassandra Analytics library. This is to fail fast if user certificates are > expired. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-109) Add certificate expiry check to start up validations done in Cassandra Analytics library
[ https://issues.apache.org/jira/browse/CASSANDRASC-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-109: - Resolution: Not A Problem Status: Resolved (was: Triage Needed) > Add certificate expiry check to start up validations done in Cassandra > Analytics library > > > Key: CASSANDRASC-109 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-109 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement >Reporter: Saranya Krishnakumar >Priority: Normal > > Want to add certificate expiry check to startup Keystore validations done in > Cassandra Analytics library. This is to fail fast if user certificates are > expired. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRASC-109) Add certificate expiry check to start up validations done in Cassandra Analytics library
Saranya Krishnakumar created CASSANDRASC-109: Summary: Add certificate expiry check to start up validations done in Cassandra Analytics library Key: CASSANDRASC-109 URL: https://issues.apache.org/jira/browse/CASSANDRASC-109 Project: Sidecar for Apache Cassandra Issue Type: Improvement Reporter: Saranya Krishnakumar Want to add certificate expiry check to startup Keystore validations done in Cassandra Analytics library. This is to fail fast if user certificates are expired. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-108) Update access of ClearSnapshotStrategy
[ https://issues.apache.org/jira/browse/CASSANDRASC-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-108: - Epic Link: (was: CASSANDRA-18090) > Update access of ClearSnapshotStrategy > -- > > Key: CASSANDRASC-108 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-108 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement >Reporter: Saranya Krishnakumar >Priority: Normal > > Want to update access of ClearSnapshotStrategy added to allow setting TTL for > snapshots created by bulk reader. Currently the access of the class is > package private, for plugging in custom implementation, we need access > outside the package. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRASC-108) Update access of ClearSnapshotStrategy
Saranya Krishnakumar created CASSANDRASC-108: Summary: Update access of ClearSnapshotStrategy Key: CASSANDRASC-108 URL: https://issues.apache.org/jira/browse/CASSANDRASC-108 Project: Sidecar for Apache Cassandra Issue Type: Improvement Reporter: Saranya Krishnakumar Want to update access of ClearSnapshotStrategy added to allow setting TTL for snapshots created by bulk reader. Currently the access of the class is package private, for plugging in custom implementation, we need access outside the package. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRASC-101) Upgrade Vert.x version in Sidecar to 4.5
[ https://issues.apache.org/jira/browse/CASSANDRASC-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816821#comment-17816821 ] Saranya Krishnakumar commented on CASSANDRASC-101: -- Green CI after latest commits [https://app.circleci.com/pipelines/github/sarankk/cassandra-sidecar/151] > Upgrade Vert.x version in Sidecar to 4.5 > > > Key: CASSANDRASC-101 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-101 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > Labels: pull-request-available > > There was a memory leak identified in 4.4 branch in Vert.x > [https://github.com/eclipse-vertx/vert.x/pull/5082]. This leak is caused when > connection pools are recreated for vert.x HttpClient. This was fixed in 4.5 > branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x > version, hence we need to upgrade to 4.5.3 Vert.x version. As part of this we > will also pick up dynamic update capability added for read and write > thresholds set for servers > [https://github.com/eclipse-vertx/vert.x/pull/5088]. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRASC-101) Upgrade Vert.x version in Sidecar to 4.5
[ https://issues.apache.org/jira/browse/CASSANDRASC-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816259#comment-17816259 ] Saranya Krishnakumar edited comment on CASSANDRASC-101 at 2/10/24 1:04 AM: --- Makes sense, updated patch to pick up 4.5.3 version [https://github.com/apache/cassandra-sidecar/pull/97]. Added changes to allow for dynamic traffic shaping options update. Green CI [https://app.circleci.com/pipelines/github/sarankk/cassandra-sidecar/146] was (Author: saranya_k): Makes sense, updated patch to pick up 4.5.3 version [https://github.com/apache/cassandra-sidecar/pull/97]. Green CI [https://app.circleci.com/pipelines/github/sarankk/cassandra-sidecar/146] > Upgrade Vert.x version in Sidecar to 4.5 > > > Key: CASSANDRASC-101 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-101 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > > There was a memory leak identified in 4.4 branch in Vert.x > [https://github.com/eclipse-vertx/vert.x/pull/5082]. This leak is caused when > connection pools are recreated for vert.x HttpClient. This was fixed in 4.5 > branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x > version, hence we need to upgrade to 4.5.3 Vert.x version. As part of this we > will also pick up dynamic update capability added for read and write > thresholds set for servers > [https://github.com/eclipse-vertx/vert.x/pull/5088]. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRASC-101) Upgrade Vert.x version in Sidecar to 4.5
[ https://issues.apache.org/jira/browse/CASSANDRASC-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816259#comment-17816259 ] Saranya Krishnakumar commented on CASSANDRASC-101: -- Makes sense, updated patch to pick up 4.5.3 version [https://github.com/apache/cassandra-sidecar/pull/97]. Green CI [https://app.circleci.com/pipelines/github/sarankk/cassandra-sidecar/146] > Upgrade Vert.x version in Sidecar to 4.5 > > > Key: CASSANDRASC-101 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-101 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > > There was a memory leak identified in 4.4 branch in Vert.x > [https://github.com/eclipse-vertx/vert.x/pull/5082]. This leak is caused when > connection pools are recreated for vert.x HttpClient. This was fixed in 4.5 > branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x > version, hence we need to upgrade to 4.5.3 Vert.x version. As part of this we > will also pick up dynamic update capability added for read and write > thresholds set for servers > [https://github.com/eclipse-vertx/vert.x/pull/5088]. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRASC-100) Fix flaky SSTableImportHandlerTest
[ https://issues.apache.org/jira/browse/CASSANDRASC-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816131#comment-17816131 ] Saranya Krishnakumar commented on CASSANDRASC-100: -- Repeated run CI [https://app.circleci.com/pipelines/github/sarankk/cassandra-sidecar/142] > Fix flaky SSTableImportHandlerTest > -- > > Key: CASSANDRASC-100 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-100 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Labels: pull-request-available > > Few of SSTableImportHandlerTest are flaky, causing multiple re-triggers for > PR green: > - testSucceeds > - testSucceedsWithClearRepaired > - testSucceedsWithExtendedVerify > They are failing with error: > org.mockito.exceptions.misusing.CannotStubVoidMethodWithReturnValue: > 'healthCheck' is a *void method* and it *cannot* be stubbed with a *return > value*! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRASC-100) Fix flaky SSTableImportHandlerTest
[ https://issues.apache.org/jira/browse/CASSANDRASC-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815911#comment-17815911 ] Saranya Krishnakumar commented on CASSANDRASC-100: -- thanks for review > Fix flaky SSTableImportHandlerTest > -- > > Key: CASSANDRASC-100 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-100 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Labels: pull-request-available > > Few of SSTableImportHandlerTest are flaky, causing multiple re-triggers for > PR green: > - testSucceeds > - testSucceedsWithClearRepaired > - testSucceedsWithExtendedVerify > They are failing with error: > org.mockito.exceptions.misusing.CannotStubVoidMethodWithReturnValue: > 'healthCheck' is a *void method* and it *cannot* be stubbed with a *return > value*! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-101) Upgrade Vert.x version in Sidecar to 4.5
[ https://issues.apache.org/jira/browse/CASSANDRASC-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-101: - Description: There was a memory leak identified in 4.4 branch in Vert.x [https://github.com/eclipse-vertx/vert.x/pull/5082]. This leak is caused when connection pools are recreated for vert.x HttpClient. This was fixed in 4.5 branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x version, hence we need to upgrade to 4.5.3 Vert.x version. As part of this we will also pick up dynamic update capability added for read and write thresholds set for servers [https://github.com/eclipse-vertx/vert.x/pull/5088]. (was: There was a memory leak identified in 4.4 branch in Vert.x [https://github.com/eclipse-vertx/vert.x/pull/5082]. This was fixed in 4.5 branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x version, hence we need to upgrade to 4.5 Vert.x version. ) > Upgrade Vert.x version in Sidecar to 4.5 > > > Key: CASSANDRASC-101 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-101 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > > There was a memory leak identified in 4.4 branch in Vert.x > [https://github.com/eclipse-vertx/vert.x/pull/5082]. This leak is caused when > connection pools are recreated for vert.x HttpClient. This was fixed in 4.5 > branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x > version, hence we need to upgrade to 4.5.3 Vert.x version. As part of this we > will also pick up dynamic update capability added for read and write > thresholds set for servers > [https://github.com/eclipse-vertx/vert.x/pull/5088]. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-101) Upgrade Vert.x version in Sidecar to 4.5
[ https://issues.apache.org/jira/browse/CASSANDRASC-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-101: - Summary: Upgrade Vert.x version in Sidecar to 4.5 (was: Upgrade Vert.x version in Sidecar to 4.5.2) > Upgrade Vert.x version in Sidecar to 4.5 > > > Key: CASSANDRASC-101 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-101 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > > There was a memory leak identified in 4.4 branch in Vert.x > [https://github.com/eclipse-vertx/vert.x/pull/5082]. This was fixed in 4.5 > branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x > version, hence we need to upgrade to 4.5 Vert.x version. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-101) Upgrade Vert.x version in Sidecar to 4.5.2
[ https://issues.apache.org/jira/browse/CASSANDRASC-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-101: - Summary: Upgrade Vert.x version in Sidecar to 4.5.2 (was: Upgrade Vert.x version in Sidecar to 4.5) > Upgrade Vert.x version in Sidecar to 4.5.2 > -- > > Key: CASSANDRASC-101 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-101 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > > There was a memory leak identified in 4.4 branch in Vert.x > [https://github.com/eclipse-vertx/vert.x/pull/5082]. This was fixed in 4.5 > branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x > version, hence we need to upgrade to 4.5 Vert.x version. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-101) Upgrade Vert.x version in Sidecar to 4.5
[ https://issues.apache.org/jira/browse/CASSANDRASC-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-101: - Summary: Upgrade Vert.x version in Sidecar to 4.5 (was: Upgrade Vert.x version in Sidecar to 4.5.3) > Upgrade Vert.x version in Sidecar to 4.5 > > > Key: CASSANDRASC-101 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-101 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > > There was a memory leak identified in 4.4 branch in Vert.x > [https://github.com/eclipse-vertx/vert.x/pull/5082]. This was fixed in 4.5 > branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x > version, hence we need to upgrade to 4.5.3 Vert.x version. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-101) Upgrade Vert.x version in Sidecar to 4.5
[ https://issues.apache.org/jira/browse/CASSANDRASC-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-101: - Description: There was a memory leak identified in 4.4 branch in Vert.x [https://github.com/eclipse-vertx/vert.x/pull/5082]. This was fixed in 4.5 branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x version, hence we need to upgrade to 4.5 Vert.x version. (was: There was a memory leak identified in 4.4 branch in Vert.x [https://github.com/eclipse-vertx/vert.x/pull/5082]. This was fixed in 4.5 branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x version, hence we need to upgrade to 4.5.3 Vert.x version. ) > Upgrade Vert.x version in Sidecar to 4.5 > > > Key: CASSANDRASC-101 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-101 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > > There was a memory leak identified in 4.4 branch in Vert.x > [https://github.com/eclipse-vertx/vert.x/pull/5082]. This was fixed in 4.5 > branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x > version, hence we need to upgrade to 4.5 Vert.x version. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-101) Upgrade Vert.x version in Sidecar to 4.5.3
[ https://issues.apache.org/jira/browse/CASSANDRASC-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-101: - Summary: Upgrade Vert.x version in Sidecar to 4.5.3 (was: Upgrade Vert.x version in Sidecar to 4.5.2) > Upgrade Vert.x version in Sidecar to 4.5.3 > -- > > Key: CASSANDRASC-101 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-101 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > > There was a memory leak identified in 4.4 branch in Vert.x > [https://github.com/eclipse-vertx/vert.x/pull/5082]. This was fixed in 4.5 > branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x > version, hence we need to upgrade to 4.5.2 Vert.x version. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-101) Upgrade Vert.x version in Sidecar to 4.5.3
[ https://issues.apache.org/jira/browse/CASSANDRASC-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-101: - Description: There was a memory leak identified in 4.4 branch in Vert.x [https://github.com/eclipse-vertx/vert.x/pull/5082]. This was fixed in 4.5 branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x version, hence we need to upgrade to 4.5.3 Vert.x version. (was: There was a memory leak identified in 4.4 branch in Vert.x [https://github.com/eclipse-vertx/vert.x/pull/5082]. This was fixed in 4.5 branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x version, hence we need to upgrade to 4.5.2 Vert.x version. ) > Upgrade Vert.x version in Sidecar to 4.5.3 > -- > > Key: CASSANDRASC-101 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-101 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > > There was a memory leak identified in 4.4 branch in Vert.x > [https://github.com/eclipse-vertx/vert.x/pull/5082]. This was fixed in 4.5 > branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x > version, hence we need to upgrade to 4.5.3 Vert.x version. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-101) Upgrade Vert.x version in Sidecar to 4.5.2
[ https://issues.apache.org/jira/browse/CASSANDRASC-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-101: - Test and Documentation Plan: unit and integration tests Status: Patch Available (was: Open) > Upgrade Vert.x version in Sidecar to 4.5.2 > -- > > Key: CASSANDRASC-101 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-101 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > > There was a memory leak identified in 4.4 branch in Vert.x > [https://github.com/eclipse-vertx/vert.x/pull/5082]. This was fixed in 4.5 > branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x > version, hence we need to upgrade to 4.5.2 Vert.x version. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRASC-101) Upgrade Vert.x version in Sidecar to 4.5.2
[ https://issues.apache.org/jira/browse/CASSANDRASC-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815030#comment-17815030 ] Saranya Krishnakumar commented on CASSANDRASC-101: -- Patch [https://github.com/apache/cassandra-sidecar/pull/97] CI green [https://app.circleci.com/pipelines/github/sarankk/cassandra-sidecar/129/workflows/6dc931d2-afdc-4c12-ae83-9259eae19e92] > Upgrade Vert.x version in Sidecar to 4.5.2 > -- > > Key: CASSANDRASC-101 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-101 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > > There was a memory leak identified in 4.4 branch in Vert.x > [https://github.com/eclipse-vertx/vert.x/pull/5082]. This was fixed in 4.5 > branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x > version, hence we need to upgrade to 4.5.2 Vert.x version. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-101) Upgrade Vert.x version in Sidecar to 4.5.2
[ https://issues.apache.org/jira/browse/CASSANDRASC-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-101: - Reviewers: Francisco Guerrero, Yifan Cai (was: Francisco Guerrero) > Upgrade Vert.x version in Sidecar to 4.5.2 > -- > > Key: CASSANDRASC-101 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-101 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > > There was a memory leak identified in 4.4 branch in Vert.x > [https://github.com/eclipse-vertx/vert.x/pull/5082]. This was fixed in 4.5 > branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x > version, hence we need to upgrade to 4.5.2 Vert.x version. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-101) Upgrade Vert.x version in Sidecar to 4.5.2
[ https://issues.apache.org/jira/browse/CASSANDRASC-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-101: - Change Category: Quality Assurance Complexity: Normal Reviewers: Francisco Guerrero Assignee: Saranya Krishnakumar Priority: High (was: Normal) Status: Open (was: Triage Needed) Test new version with existing unit tests and integration tests > Upgrade Vert.x version in Sidecar to 4.5.2 > -- > > Key: CASSANDRASC-101 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-101 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > > There was a memory leak identified in 4.4 branch in Vert.x > [https://github.com/eclipse-vertx/vert.x/pull/5082]. This was fixed in 4.5 > branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x > version, hence we need to upgrade to 4.5.2 Vert.x version. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRASC-101) Upgrade Vert.x version in Sidecar to 4.5.2
Saranya Krishnakumar created CASSANDRASC-101: Summary: Upgrade Vert.x version in Sidecar to 4.5.2 Key: CASSANDRASC-101 URL: https://issues.apache.org/jira/browse/CASSANDRASC-101 Project: Sidecar for Apache Cassandra Issue Type: Improvement Components: Configuration Reporter: Saranya Krishnakumar There was a memory leak identified in 4.4 branch in Vert.x [https://github.com/eclipse-vertx/vert.x/pull/5082]. This was fixed in 4.5 branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x version, hence we need to upgrade to 4.5.2 Vert.x version. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-100) Fix flaky SSTableImportHandlerTest
[ https://issues.apache.org/jira/browse/CASSANDRASC-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-100: - Bug Category: Parent values: Code(13163) Complexity: Normal Component/s: Rest API Discovered By: Unit Test Severity: Normal Status: Open (was: Triage Needed) > Fix flaky SSTableImportHandlerTest > -- > > Key: CASSANDRASC-100 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-100 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Saranya Krishnakumar >Priority: Normal > > Few of SSTableImportHandlerTest are flaky, causing multiple re-triggers for > PR green: > - testSucceeds > - testSucceedsWithClearRepaired > - testSucceedsWithExtendedVerify > They are failing with error: > org.mockito.exceptions.misusing.CannotStubVoidMethodWithReturnValue: > 'healthCheck' is a *void method* and it *cannot* be stubbed with a *return > value*! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRASC-100) Fix flaky SSTableImportHandlerTest
Saranya Krishnakumar created CASSANDRASC-100: Summary: Fix flaky SSTableImportHandlerTest Key: CASSANDRASC-100 URL: https://issues.apache.org/jira/browse/CASSANDRASC-100 Project: Sidecar for Apache Cassandra Issue Type: Bug Reporter: Saranya Krishnakumar Few of SSTableImportHandlerTest are flaky, causing multiple re-triggers for PR green: - testSucceeds - testSucceedsWithClearRepaired - testSucceedsWithExtendedVerify They are failing with error: org.mockito.exceptions.misusing.CannotStubVoidMethodWithReturnValue: 'healthCheck' is a *void method* and it *cannot* be stubbed with a *return value*! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19273) Allow setting TTL for snapshots created by Analytics bulk reader
[ https://issues.apache.org/jira/browse/CASSANDRA-19273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809669#comment-17809669 ] Saranya Krishnakumar commented on CASSANDRA-19273: -- Latest CircleCl green: [https://app.circleci.com/pipelines/github/sarankk/cassandra-analytics/38/workflows/e9ce6765-c035-4620-afc4-8545957633a9] > Allow setting TTL for snapshots created by Analytics bulk reader > > > Key: CASSANDRA-19273 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19273 > Project: Cassandra > Issue Type: New Feature > Components: Analytics Library >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Time Spent: 1h 40m > Remaining Estimate: 0h > > Analytics user can add an existing snapshot's name or create a new snapshot > through reader options, from which data is bulk read from. Incase of creating > new snapshot, we want to allow users to set TTL option and have a default > value for the TTL. This is to make sure, in case of job failures, the > snapshots are cleared, to release space. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-19273) Allow setting TTL for snapshots created by Analytics bulk reader
[ https://issues.apache.org/jira/browse/CASSANDRA-19273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17807957#comment-17807957 ] Saranya Krishnakumar edited comment on CASSANDRA-19273 at 1/18/24 1:03 AM: --- Latest Circle CI green: [https://app.circleci.com/pipelines/github/sarankk/cassandra-analytics/31/workflows/0de00d4e-6cf8-4a8f-9dec-930278a6a5e4] was (Author: saranya_k): Latest Circle CI green: [https://app.circleci.com/pipelines/github/sarankk/cassandra-analytics?branch=add-snapshot-ttl] > Allow setting TTL for snapshots created by Analytics bulk reader > > > Key: CASSANDRA-19273 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19273 > Project: Cassandra > Issue Type: New Feature > Components: Analytics Library >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > Analytics user can add an existing snapshot's name or create a new snapshot > through reader options, from which data is bulk read from. Incase of creating > new snapshot, we want to allow users to set TTL option and have a default > value for the TTL. This is to make sure, in case of job failures, the > snapshots are cleared, to release space. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19273) Allow setting TTL for snapshots created by Analytics bulk reader
[ https://issues.apache.org/jira/browse/CASSANDRA-19273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17807957#comment-17807957 ] Saranya Krishnakumar commented on CASSANDRA-19273: -- Latest Circle CI green: [https://app.circleci.com/pipelines/github/sarankk/cassandra-analytics?branch=add-snapshot-ttl] > Allow setting TTL for snapshots created by Analytics bulk reader > > > Key: CASSANDRA-19273 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19273 > Project: Cassandra > Issue Type: New Feature > Components: Analytics Library >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > Analytics user can add an existing snapshot's name or create a new snapshot > through reader options, from which data is bulk read from. Incase of creating > new snapshot, we want to allow users to set TTL option and have a default > value for the TTL. This is to make sure, in case of job failures, the > snapshots are cleared, to release space. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19273) Allow setting TTL for snapshots created by Analytics bulk reader
[ https://issues.apache.org/jira/browse/CASSANDRA-19273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17807924#comment-17807924 ] Saranya Krishnakumar commented on CASSANDRA-19273: -- Circle CI green: [https://app.circleci.com/pipelines/github/sarankk/cassandra-analytics?branch=add-snapshot-ttl] > Allow setting TTL for snapshots created by Analytics bulk reader > > > Key: CASSANDRA-19273 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19273 > Project: Cassandra > Issue Type: New Feature > Components: Analytics Library >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > Analytics user can add an existing snapshot's name or create a new snapshot > through reader options, from which data is bulk read from. Incase of creating > new snapshot, we want to allow users to set TTL option and have a default > value for the TTL. This is to make sure, in case of job failures, the > snapshots are cleared, to release space. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19275) Flaky Host replacement tests and shrink tests
Saranya Krishnakumar created CASSANDRA-19275: Summary: Flaky Host replacement tests and shrink tests Key: CASSANDRA-19275 URL: https://issues.apache.org/jira/browse/CASSANDRA-19275 Project: Cassandra Issue Type: Bug Reporter: Saranya Krishnakumar During Circle CI runs there are some flaky integration tests, some noticed are * HostReplacementMultiDCTest * HostReplacementMultiDCFailureTest * HostReplacementFailureTest * LeavingSingleFailureTest Some of the error message I see in these tests are e.g. `java.lang.RuntimeException: java.lang.IllegalStateException: Can't load org.apache.cassandra.utils.concurrent.Ref$OnLeak. Instance class loader is already closed.` `java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Failed to bind port 42611 on 127.0.0.2.` On repeated run, these tests pass. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19273) Allow setting TTL for snapshots created by Analytics bulk reader
[ https://issues.apache.org/jira/browse/CASSANDRA-19273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRA-19273: - Change Category: Performance Complexity: Low Hanging Fruit Component/s: Analytics Library Reviewers: Francisco Guerrero, Yifan Cai Assignee: Saranya Krishnakumar Status: Open (was: Triage Needed) Patch: [https://github.com/apache/cassandra-analytics/pull/31] > Allow setting TTL for snapshots created by Analytics bulk reader > > > Key: CASSANDRA-19273 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19273 > Project: Cassandra > Issue Type: New Feature > Components: Analytics Library >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > Analytics user can add an existing snapshot's name or create a new snapshot > through reader options, from which data is bulk read from. Incase of creating > new snapshot, we want to allow users to set TTL option and have a default > value for the TTL. This is to make sure, in case of job failures, the > snapshots are cleared, to release space. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19273) Allow setting TTL for snapshots created by Analytics bulk reader
[ https://issues.apache.org/jira/browse/CASSANDRA-19273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRA-19273: - Test and Documentation Plan: Tested with both unit test and in-jvm integration tests Status: Patch Available (was: Open) > Allow setting TTL for snapshots created by Analytics bulk reader > > > Key: CASSANDRA-19273 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19273 > Project: Cassandra > Issue Type: New Feature > Components: Analytics Library >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > Analytics user can add an existing snapshot's name or create a new snapshot > through reader options, from which data is bulk read from. Incase of creating > new snapshot, we want to allow users to set TTL option and have a default > value for the TTL. This is to make sure, in case of job failures, the > snapshots are cleared, to release space. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19273) Allow setting TTL for snapshots created by Analytics bulk reader
Saranya Krishnakumar created CASSANDRA-19273: Summary: Allow setting TTL for snapshots created by Analytics bulk reader Key: CASSANDRA-19273 URL: https://issues.apache.org/jira/browse/CASSANDRA-19273 Project: Cassandra Issue Type: New Feature Reporter: Saranya Krishnakumar Analytics user can add an existing snapshot's name or create a new snapshot through reader options, from which data is bulk read from. Incase of creating new snapshot, we want to allow users to set TTL option and have a default value for the TTL. This is to make sure, in case of job failures, the snapshots are cleared, to release space. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-92) Add restore SSTables from S3 into Cassandra feature to Cassandra Sidecar
[ https://issues.apache.org/jira/browse/CASSANDRASC-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-92: Description: Through this proposal we want to add restore capability to Sidecar, for Sidecar to allow restoring data from S3. As part of this patch we want to add APIs for creating, updating and getting information about the restore jobs. We also want to add background tasks for managing these restore jobs. (was: Through this proposal we want to add restore capability to Sidecar, for Sidecar to allow restoring data from S3. As part of this patch we want to add APIs for creating, updating and getting information about the restore jobs. We also want to add background tasks for managing these restore jobs. Patch: [https://github.com/apache/cassandra-sidecar/pull/89]) > Add restore SSTables from S3 into Cassandra feature to Cassandra Sidecar > > > Key: CASSANDRASC-92 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-92 > Project: Sidecar for Apache Cassandra > Issue Type: New Feature > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > Through this proposal we want to add restore capability to Sidecar, for > Sidecar to allow restoring data from S3. As part of this patch we want to add > APIs for creating, updating and getting information about the restore jobs. > We also want to add background tasks for managing these restore jobs. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] (CASSANDRASC-92) Add restore SSTables from S3 into Cassandra feature to Cassandra Sidecar
[ https://issues.apache.org/jira/browse/CASSANDRASC-92 ] Saranya Krishnakumar deleted comment on CASSANDRASC-92: - was (Author: saranya_k): Tested with unit tests > Add restore SSTables from S3 into Cassandra feature to Cassandra Sidecar > > > Key: CASSANDRASC-92 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-92 > Project: Sidecar for Apache Cassandra > Issue Type: New Feature > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > Through this proposal we want to add restore capability to Sidecar, for > Sidecar to allow restoring data from S3. As part of this patch we want to add > APIs for creating, updating and getting information about the restore jobs. > We also want to add background tasks for managing these restore jobs. > Patch: [https://github.com/apache/cassandra-sidecar/pull/89] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-92) Add restore SSTables from S3 into Cassandra feature to Cassandra Sidecar
[ https://issues.apache.org/jira/browse/CASSANDRASC-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-92: Authors: Saranya Krishnakumar, Yifan Cai Test and Documentation Plan: Tested with unit tests Status: Patch Available (was: Open) Patch: [https://github.com/apache/cassandra-sidecar/pull/89] > Add restore SSTables from S3 into Cassandra feature to Cassandra Sidecar > > > Key: CASSANDRASC-92 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-92 > Project: Sidecar for Apache Cassandra > Issue Type: New Feature > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > Through this proposal we want to add restore capability to Sidecar, for > Sidecar to allow restoring data from S3. As part of this patch we want to add > APIs for creating, updating and getting information about the restore jobs. > We also want to add background tasks for managing these restore jobs. > Patch: [https://github.com/apache/cassandra-sidecar/pull/89] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-92) Add restore SSTables from S3 into Cassandra feature to Cassandra Sidecar
[ https://issues.apache.org/jira/browse/CASSANDRASC-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-92: Description: Through this proposal we want to add restore capability to Sidecar, for Sidecar to allow restoring data from S3. As part of this patch we want to add APIs for creating, updating and getting information about the restore jobs. We also want to add background tasks for managing these restore jobs. Patch: [https://github.com/apache/cassandra-sidecar/pull/89] was:Through this proposal we want to add restore capability to Sidecar, for Sidecar to allow restoring data from S3. As part of this patch we want to add APIs for creating, updating and getting information about the restore jobs. We also want to add background tasks for managing these restore jobs. > Add restore SSTables from S3 into Cassandra feature to Cassandra Sidecar > > > Key: CASSANDRASC-92 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-92 > Project: Sidecar for Apache Cassandra > Issue Type: New Feature > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > Through this proposal we want to add restore capability to Sidecar, for > Sidecar to allow restoring data from S3. As part of this patch we want to add > APIs for creating, updating and getting information about the restore jobs. > We also want to add background tasks for managing these restore jobs. > Patch: [https://github.com/apache/cassandra-sidecar/pull/89] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-92) Add restore SSTables from S3 into Cassandra feature to Cassandra Sidecar
[ https://issues.apache.org/jira/browse/CASSANDRASC-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-92: Change Category: Performance Complexity: Normal Component/s: Rest API Reviewers: Francisco Guerrero, Yifan Cai Assignee: Saranya Krishnakumar Status: Open (was: Triage Needed) Tested with unit tests > Add restore SSTables from S3 into Cassandra feature to Cassandra Sidecar > > > Key: CASSANDRASC-92 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-92 > Project: Sidecar for Apache Cassandra > Issue Type: New Feature > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > Through this proposal we want to add restore capability to Sidecar, for > Sidecar to allow restoring data from S3. As part of this patch we want to add > APIs for creating, updating and getting information about the restore jobs. > We also want to add background tasks for managing these restore jobs. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRASC-92) Add restore SSTables from S3 into Cassandra feature to Cassandra Sidecar
Saranya Krishnakumar created CASSANDRASC-92: --- Summary: Add restore SSTables from S3 into Cassandra feature to Cassandra Sidecar Key: CASSANDRASC-92 URL: https://issues.apache.org/jira/browse/CASSANDRASC-92 Project: Sidecar for Apache Cassandra Issue Type: New Feature Reporter: Saranya Krishnakumar Through this proposal we want to add restore capability to Sidecar, for Sidecar to allow restoring data from S3. As part of this patch we want to add APIs for creating, updating and getting information about the restore jobs. We also want to add background tasks for managing these restore jobs. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19003) Get Sidecar port through CassandraContext for more flexibility
[ https://issues.apache.org/jira/browse/CASSANDRA-19003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRA-19003: - Status: Patch Available (was: In Progress) > Get Sidecar port through CassandraContext for more flexibility > --- > > Key: CASSANDRA-19003 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19003 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > We get sidecar port from `BulkSparkConf` but it will be better if we get it > from `CassandraContext` provides more flexibility -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19003) Get Sidecar port through CassandraContext for more flexibility
[ https://issues.apache.org/jira/browse/CASSANDRA-19003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRA-19003: - Status: In Progress (was: Patch Available) > Get Sidecar port through CassandraContext for more flexibility > --- > > Key: CASSANDRA-19003 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19003 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > We get sidecar port from `BulkSparkConf` but it will be better if we get it > from `CassandraContext` provides more flexibility -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19003) Get Sidecar port through CassandraContext for more flexibility
[ https://issues.apache.org/jira/browse/CASSANDRA-19003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17784227#comment-17784227 ] Saranya Krishnakumar commented on CASSANDRA-19003: -- Green CircleCI run: [https://app.circleci.com/pipelines/github/sarankk/cassandra-analytics/16/workflows/09eb16ea-b503-4bb5-9681-ee5f4a584099/jobs/64] > Get Sidecar port through CassandraContext for more flexibility > --- > > Key: CASSANDRA-19003 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19003 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > We get sidecar port from `BulkSparkConf` but it will be better if we get it > from `CassandraContext` provides more flexibility -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19003) Get Sidecar port through CassandraContext for more flexibility
[ https://issues.apache.org/jira/browse/CASSANDRA-19003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRA-19003: - Test and Documentation Plan: Unit test Status: Patch Available (was: In Progress) [https://github.com/apache/cassandra-analytics/pull/18] > Get Sidecar port through CassandraContext for more flexibility > --- > > Key: CASSANDRA-19003 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19003 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > We get sidecar port from `BulkSparkConf` but it will be better if we get it > from `CassandraContext` provides more flexibility -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19003) Get Sidecar port through CassandraContext for more flexibility
[ https://issues.apache.org/jira/browse/CASSANDRA-19003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRA-19003: - Change Category: Code Clarity Complexity: Low Hanging Fruit Component/s: Analytics Library Status: Open (was: Triage Needed) > Get Sidecar port through CassandraContext for more flexibility > --- > > Key: CASSANDRA-19003 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19003 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > We get sidecar port from `BulkSparkConf` but it will be better if we get it > from `CassandraContext` provides more flexibility -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19003) Get Sidecar port through CassandraContext for more flexibility
Saranya Krishnakumar created CASSANDRA-19003: Summary: Get Sidecar port through CassandraContext for more flexibility Key: CASSANDRA-19003 URL: https://issues.apache.org/jira/browse/CASSANDRA-19003 Project: Cassandra Issue Type: Task Reporter: Saranya Krishnakumar Assignee: Saranya Krishnakumar We get sidecar port from `BulkSparkConf` but it will be better if we get it from `CassandraContext` provides more flexibility -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-68) Add Metrics publisher interface to Sidecar to expose metrics for capture
[ https://issues.apache.org/jira/browse/CASSANDRASC-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-68: Description: We need metrics publisher interface in Sidecar to capture some of the metrics like bytes written/streamed. (was: We need metrics publisher interface in Sidecar to capture some of the metrics like bytes written/streamed. PR: [https://github.com/apache/cassandra-sidecar/pull/64] CircleCI run: [https://app.circleci.com/pipelines/github/sarankk/cassandra-sidecar] ) > Add Metrics publisher interface to Sidecar to expose metrics for capture > > > Key: CASSANDRASC-68 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-68 > Project: Sidecar for Apache Cassandra > Issue Type: New Feature > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > Labels: pull-request-available > > We need metrics publisher interface in Sidecar to capture some of the metrics > like bytes written/streamed. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRASC-68) Add Metrics publisher interface to Sidecar to expose metrics for capture
[ https://issues.apache.org/jira/browse/CASSANDRASC-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17759762#comment-17759762 ] Saranya Krishnakumar commented on CASSANDRASC-68: - PR: [https://github.com/apache/cassandra-sidecar/pull/64] CircleCI run: [https://app.circleci.com/pipelines/github/sarankk/cassandra-sidecar] For reference > Add Metrics publisher interface to Sidecar to expose metrics for capture > > > Key: CASSANDRASC-68 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-68 > Project: Sidecar for Apache Cassandra > Issue Type: New Feature > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > Labels: pull-request-available > > We need metrics publisher interface in Sidecar to capture some of the metrics > like bytes written/streamed. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-68) Add Metrics publisher interface to Sidecar to expose metrics for capture
[ https://issues.apache.org/jira/browse/CASSANDRASC-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-68: Description: We need metrics publisher interface in Sidecar to capture some of the metrics like bytes written/streamed. PR: [https://github.com/apache/cassandra-sidecar/pull/64] CircleCI run: [https://app.circleci.com/pipelines/github/sarankk/cassandra-sidecar] was: We need metrics publisher interface in Sidecar to capture some of the metrics like bytes written/streamed. PR: [https://github.com/apache/cassandra-sidecar/pull/64] > Add Metrics publisher interface to Sidecar to expose metrics for capture > > > Key: CASSANDRASC-68 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-68 > Project: Sidecar for Apache Cassandra > Issue Type: New Feature > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > > We need metrics publisher interface in Sidecar to capture some of the metrics > like bytes written/streamed. > PR: [https://github.com/apache/cassandra-sidecar/pull/64] > CircleCI run: > [https://app.circleci.com/pipelines/github/sarankk/cassandra-sidecar] > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-68) Add Metrics publisher interface to Sidecar to expose metrics for capture
[ https://issues.apache.org/jira/browse/CASSANDRASC-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-68: Authors: Saranya Krishnakumar Test and Documentation Plan: Added a small interface, so far no tests added Status: Patch Available (was: Open) > Add Metrics publisher interface to Sidecar to expose metrics for capture > > > Key: CASSANDRASC-68 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-68 > Project: Sidecar for Apache Cassandra > Issue Type: New Feature > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > > We need metrics publisher interface in Sidecar to capture some of the metrics > like bytes written/streamed. > PR: [https://github.com/apache/cassandra-sidecar/pull/64] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-68) Add Metrics publisher interface to Sidecar to expose metrics for capture
[ https://issues.apache.org/jira/browse/CASSANDRASC-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-68: Change Category: Operability Complexity: Low Hanging Fruit Reviewers: Yifan Cai Priority: High (was: Normal) Status: Open (was: Triage Needed) > Add Metrics publisher interface to Sidecar to expose metrics for capture > > > Key: CASSANDRASC-68 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-68 > Project: Sidecar for Apache Cassandra > Issue Type: New Feature > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > > We need metrics publisher interface in Sidecar to capture some of the metrics > like bytes written/streamed. > PR: [https://github.com/apache/cassandra-sidecar/pull/64] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-68) Add Metrics publisher interface to Sidecar to expose metrics for capture
[ https://issues.apache.org/jira/browse/CASSANDRASC-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-68: Description: We need metrics publisher interface in Sidecar to capture some of the metrics like bytes written/streamed. PR: [https://github.com/apache/cassandra-sidecar/pull/64] was:We need metrics publisher interface in Sidecar to capture some of the metrics like bytes written/streamed. > Add Metrics publisher interface to Sidecar to expose metrics for capture > > > Key: CASSANDRASC-68 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-68 > Project: Sidecar for Apache Cassandra > Issue Type: New Feature > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > We need metrics publisher interface in Sidecar to capture some of the metrics > like bytes written/streamed. > PR: [https://github.com/apache/cassandra-sidecar/pull/64] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRASC-68) Add Metrics publisher interface to Sidecar to expose metrics for capture
Saranya Krishnakumar created CASSANDRASC-68: --- Summary: Add Metrics publisher interface to Sidecar to expose metrics for capture Key: CASSANDRASC-68 URL: https://issues.apache.org/jira/browse/CASSANDRASC-68 Project: Sidecar for Apache Cassandra Issue Type: New Feature Components: Rest API Reporter: Saranya Krishnakumar Assignee: Saranya Krishnakumar We need metrics publisher interface in Sidecar to capture some of the metrics like bytes written/streamed. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17870) nodetool/rebuild: Add flag to exclude nodes from local datacenter
[ https://issues.apache.org/jira/browse/CASSANDRA-17870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635583#comment-17635583 ] Saranya Krishnakumar commented on CASSANDRA-17870: -- Circle CI run: [https://app.circleci.com/pipelines/github/sarankk/cassandra?branch=fix-nodetool-rebuild] > nodetool/rebuild: Add flag to exclude nodes from local datacenter > - > > Key: CASSANDRA-17870 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17870 > Project: Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Attachments: fix_nodetool_rebuild.diff > > Time Spent: 1.5h > Remaining Estimate: 0h > > During expansion by Dc, when we issue nodetool/rebuild from new dc to rebuild > the data from other DCs. If src-dc is not passed explicitly, then C* tries to > rebuild the data from the same (new dc) dc. > We don’t exclude other nodes in the same DC. Only down sources and the local > node itself are excluded. > ``` > // We're _always_ filtering out a local node and down sources > addSourceFilter(new > RangeStreamer.FailureDetectorSourceFilter(failureDetector)); > addSourceFilter(new RangeStreamer.ExcludeLocalNodeFilter()); > ``` > We should fix nodetool/rebuild to exclude the local DC (from where we’re > executing the command) while issuing nodetool/rebuild without passing src dc > > Example: > in a 3 DC cluster, > ks1 has DC1, DC2 > ks2 has DC1, DC2, DC3 > ks3 has DC2 > now, we add a new DC [DC4] and configured it to all 3 keyspaces. > if we run rebuild with src DC as DC1, ks3 will fail as it does not have DC1. > Now, without src DC, the expectation is rebuild would auto pick up DCs for > each keyspace (let's say ks1: DC1, ks2: DC1, ks3: DC2) and would never fail > due to under-replicated keyspaces. > The issue with this approach (without src dc) is that, DC4 is getting picked > up during rebuild (as src), but DC4 does not have any data yet! > so, with the patch (ignore local dc flag), DC4 can be filtered out and let > the database pick up the right dc for each keyspace [from existing 3 DCs]. > -- this is what is the expectation after the patch. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17870) nodetool/rebuild: Add flag to exclude nodes from local datacenter
[ https://issues.apache.org/jira/browse/CASSANDRA-17870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17620650#comment-17620650 ] Saranya Krishnakumar edited comment on CASSANDRA-17870 at 11/7/22 7:08 PM: --- [~yifanc] I created a PR as you had asked https://github.com/apache/cassandra/pull/1931 was (Author: saranya_k): [~yifanc] created a PR [https://github.com/apache/cassandra/pull/1931 |https://github.com/apache/cassandra/pull/1931,] > nodetool/rebuild: Add flag to exclude nodes from local datacenter > - > > Key: CASSANDRA-17870 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17870 > Project: Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Attachments: fix_nodetool_rebuild.diff > > Time Spent: 40m > Remaining Estimate: 0h > > During expansion by Dc, when we issue nodetool/rebuild from new dc to rebuild > the data from other DCs. If src-dc is not passed explicitly, then C* tries to > rebuild the data from the same (new dc) dc. > We don’t exclude other nodes in the same DC. Only down sources and the local > node itself are excluded. > ``` > // We're _always_ filtering out a local node and down sources > addSourceFilter(new > RangeStreamer.FailureDetectorSourceFilter(failureDetector)); > addSourceFilter(new RangeStreamer.ExcludeLocalNodeFilter()); > ``` > We should fix nodetool/rebuild to exclude the local DC (from where we’re > executing the command) while issuing nodetool/rebuild without passing src dc > > Example: > in a 3 DC cluster, > ks1 has DC1, DC2 > ks2 has DC1, DC2, DC3 > ks3 has DC2 > now, we add a new DC [DC4] and configured it to all 3 keyspaces. > if we run rebuild with src DC as DC1, ks3 will fail as it does not have DC1. > Now, without src DC, the expectation is rebuild would auto pick up DCs for > each keyspace (let's say ks1: DC1, ks2: DC1, ks3: DC2) and would never fail > due to under-replicated keyspaces. > The issue with this approach (without src dc) is that, DC4 is getting picked > up during rebuild (as src), but DC4 does not have any data yet! > so, with the patch (ignore local dc flag), DC4 can be filtered out and let > the database pick up the right dc for each keyspace [from existing 3 DCs]. > -- this is what is the expectation after the patch. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17870) nodetool/rebuild: Add flag to exclude nodes from local datacenter
[ https://issues.apache.org/jira/browse/CASSANDRA-17870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRA-17870: - Description: During expansion by Dc, when we issue nodetool/rebuild from new dc to rebuild the data from other DCs. If src-dc is not passed explicitly, then C* tries to rebuild the data from the same (new dc) dc. We don’t exclude other nodes in the same DC. Only down sources and the local node itself are excluded. ``` // We're _always_ filtering out a local node and down sources addSourceFilter(new RangeStreamer.FailureDetectorSourceFilter(failureDetector)); addSourceFilter(new RangeStreamer.ExcludeLocalNodeFilter()); ``` We should fix nodetool/rebuild to exclude the local DC (from where we’re executing the command) while issuing nodetool/rebuild without passing src dc Example: in a 3 DC cluster, ks1 has DC1, DC2 ks2 has DC1, DC2, DC3 ks3 has DC2 now, we add a new DC [DC4] and configured it to all 3 keyspaces. if we run rebuild with src DC as DC1, ks3 will fail as it does not have DC1. Now, without src DC, the expectation is rebuild would auto pick up DCs for each keyspace (let's say ks1: DC1, ks2: DC1, ks3: DC2) and would never fail due to under-replicated keyspaces. The issue with this approach (without src dc) is that, DC4 is getting picked up during rebuild (as src), but DC4 does not have any data yet! so, with the patch (ignore local dc flag), DC4 can be filtered out and let the database pick up the right dc for each keyspace [from existing 3 DCs]. -- this is what is the expectation after the patch. was: During expansion by Dc, when we issue nodetool/rebuild from new dc to rebuild the data from other DCs. If src-dc is not passed explicitly, then C* tries to rebuild the data from the same (new dc) dc. We don’t exclude other nodes in the same DC. Only down sources and the local node itself are excluded. ``` // We're _always_ filtering out a local node and down sources addSourceFilter(new RangeStreamer.FailureDetectorSourceFilter(failureDetector)); addSourceFilter(new RangeStreamer.ExcludeLocalNodeFilter()); ``` We should fix nodetool/rebuild to exclude the local DC (from where we’re executing the command) while issuing nodetool/rebuild without passing src dc > nodetool/rebuild: Add flag to exclude nodes from local datacenter > - > > Key: CASSANDRA-17870 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17870 > Project: Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Attachments: fix_nodetool_rebuild.diff > > Time Spent: 40m > Remaining Estimate: 0h > > During expansion by Dc, when we issue nodetool/rebuild from new dc to rebuild > the data from other DCs. If src-dc is not passed explicitly, then C* tries to > rebuild the data from the same (new dc) dc. > We don’t exclude other nodes in the same DC. Only down sources and the local > node itself are excluded. > ``` > // We're _always_ filtering out a local node and down sources > addSourceFilter(new > RangeStreamer.FailureDetectorSourceFilter(failureDetector)); > addSourceFilter(new RangeStreamer.ExcludeLocalNodeFilter()); > ``` > We should fix nodetool/rebuild to exclude the local DC (from where we’re > executing the command) while issuing nodetool/rebuild without passing src dc > > Example: > in a 3 DC cluster, > ks1 has DC1, DC2 > ks2 has DC1, DC2, DC3 > ks3 has DC2 > now, we add a new DC [DC4] and configured it to all 3 keyspaces. > if we run rebuild with src DC as DC1, ks3 will fail as it does not have DC1. > Now, without src DC, the expectation is rebuild would auto pick up DCs for > each keyspace (let's say ks1: DC1, ks2: DC1, ks3: DC2) and would never fail > due to under-replicated keyspaces. > The issue with this approach (without src dc) is that, DC4 is getting picked > up during rebuild (as src), but DC4 does not have any data yet! > so, with the patch (ignore local dc flag), DC4 can be filtered out and let > the database pick up the right dc for each keyspace [from existing 3 DCs]. > -- this is what is the expectation after the patch. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17870) nodetool/rebuild: Add flag to exclude nodes from local datacenter
[ https://issues.apache.org/jira/browse/CASSANDRA-17870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17620650#comment-17620650 ] Saranya Krishnakumar commented on CASSANDRA-17870: -- [~yifanc] created a PR [https://github.com/apache/cassandra/pull/1931 |https://github.com/apache/cassandra/pull/1931,] > nodetool/rebuild: Add flag to exclude nodes from local datacenter > - > > Key: CASSANDRA-17870 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17870 > Project: Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Attachments: fix_nodetool_rebuild.diff > > Time Spent: 10m > Remaining Estimate: 0h > > During expansion by Dc, when we issue nodetool/rebuild from new dc to rebuild > the data from other DCs. If src-dc is not passed explicitly, then C* tries to > rebuild the data from the same (new dc) dc. > We don’t exclude other nodes in the same DC. Only down sources and the local > node itself are excluded. > ``` > // We're _always_ filtering out a local node and down sources > addSourceFilter(new > RangeStreamer.FailureDetectorSourceFilter(failureDetector)); > addSourceFilter(new RangeStreamer.ExcludeLocalNodeFilter()); > ``` > We should fix nodetool/rebuild to exclude the local DC (from where we’re > executing the command) while issuing nodetool/rebuild without passing src dc -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17870) nodetool/rebuild: Add flag to exclude nodes from local datacenter
[ https://issues.apache.org/jira/browse/CASSANDRA-17870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRA-17870: - Attachment: fix_nodetool_rebuild.diff > nodetool/rebuild: Add flag to exclude nodes from local datacenter > - > > Key: CASSANDRA-17870 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17870 > Project: Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Attachments: fix_nodetool_rebuild.diff > > > During expansion by Dc, when we issue nodetool/rebuild from new dc to rebuild > the data from other DCs. If src-dc is not passed explicitly, then C* tries to > rebuild the data from the same (new dc) dc. > We don’t exclude other nodes in the same DC. Only down sources and the local > node itself are excluded. > ``` > // We're _always_ filtering out a local node and down sources > addSourceFilter(new > RangeStreamer.FailureDetectorSourceFilter(failureDetector)); > addSourceFilter(new RangeStreamer.ExcludeLocalNodeFilter()); > ``` > We should fix nodetool/rebuild to exclude the local DC (from where we’re > executing the command) while issuing nodetool/rebuild without passing src dc -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17870) nodetool/rebuild: Add flag to exclude nodes from local datacenter
[ https://issues.apache.org/jira/browse/CASSANDRA-17870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRA-17870: - Test and Documentation Plan: Unit test Status: Patch Available (was: Open) > nodetool/rebuild: Add flag to exclude nodes from local datacenter > - > > Key: CASSANDRA-17870 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17870 > Project: Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Attachments: fix_nodetool_rebuild.diff > > > During expansion by Dc, when we issue nodetool/rebuild from new dc to rebuild > the data from other DCs. If src-dc is not passed explicitly, then C* tries to > rebuild the data from the same (new dc) dc. > We don’t exclude other nodes in the same DC. Only down sources and the local > node itself are excluded. > ``` > // We're _always_ filtering out a local node and down sources > addSourceFilter(new > RangeStreamer.FailureDetectorSourceFilter(failureDetector)); > addSourceFilter(new RangeStreamer.ExcludeLocalNodeFilter()); > ``` > We should fix nodetool/rebuild to exclude the local DC (from where we’re > executing the command) while issuing nodetool/rebuild without passing src dc -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17870) nodetool/rebuild: C* rebuilds from local (new dc) dc nodes if src-dc is not passed
[ https://issues.apache.org/jira/browse/CASSANDRA-17870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRA-17870: - Change Category: Operability Complexity: Low Hanging Fruit Component/s: Tool/nodetool Status: Open (was: Triage Needed) > nodetool/rebuild: C* rebuilds from local (new dc) dc nodes if src-dc is not > passed > -- > > Key: CASSANDRA-17870 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17870 > Project: Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > During expansion by Dc, when we issue nodetool/rebuild from new dc to rebuild > the data from other DCs. If src-dc is not passed explicitly, then C* tries to > rebuild the data from the same (new dc) dc. > We don’t exclude other nodes in the same DC. Only down sources and the local > node itself are excluded. > ``` > // We're _always_ filtering out a local node and down sources > addSourceFilter(new > RangeStreamer.FailureDetectorSourceFilter(failureDetector)); > addSourceFilter(new RangeStreamer.ExcludeLocalNodeFilter()); > ``` > We should fix nodetool/rebuild to exclude the local DC (from where we’re > executing the command) while issuing nodetool/rebuild without passing src dc -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17870) nodetool/rebuild: C* rebuilds from local (new dc) dc nodes if src-dc is not passed
Saranya Krishnakumar created CASSANDRA-17870: Summary: nodetool/rebuild: C* rebuilds from local (new dc) dc nodes if src-dc is not passed Key: CASSANDRA-17870 URL: https://issues.apache.org/jira/browse/CASSANDRA-17870 Project: Cassandra Issue Type: Improvement Reporter: Saranya Krishnakumar Assignee: Saranya Krishnakumar During expansion by Dc, when we issue nodetool/rebuild from new dc to rebuild the data from other DCs. If src-dc is not passed explicitly, then C* tries to rebuild the data from the same (new dc) dc. We don’t exclude other nodes in the same DC. Only down sources and the local node itself are excluded. ``` // We're _always_ filtering out a local node and down sources addSourceFilter(new RangeStreamer.FailureDetectorSourceFilter(failureDetector)); addSourceFilter(new RangeStreamer.ExcludeLocalNodeFilter()); ``` We should fix nodetool/rebuild to exclude the local DC (from where we’re executing the command) while issuing nodetool/rebuild without passing src dc -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-37) Optimize file path builder and have a new handler for streaming files
[ https://issues.apache.org/jira/browse/CASSANDRASC-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-37: Authors: Francisco Guerrero, Saranya Krishnakumar Test and Documentation Plan: Tested with unit tests Status: Patch Available (was: Open) > Optimize file path builder and have a new handler for streaming files > - > > Key: CASSANDRASC-37 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-37 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > This patch optimizes file path builder and creates a new handler for > streaming files. This handler is chained along with validation handlers for > an endpoint > PR: https://github.com/apache/cassandra-sidecar/pull/29 -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRASC-37) Optimize file path builder and have a new handler for streaming files
[ https://issues.apache.org/jira/browse/CASSANDRASC-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17555712#comment-17555712 ] Saranya Krishnakumar commented on CASSANDRASC-37: - [https://app.circleci.com/pipelines/github/sarankk] Top pipeline run here > Optimize file path builder and have a new handler for streaming files > - > > Key: CASSANDRASC-37 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-37 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > This patch optimizes file path builder and creates a new handler for > streaming files. This handler is chained along with validation handlers for > an endpoint > PR: https://github.com/apache/cassandra-sidecar/pull/29 -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-37) Optimize file path builder and have a new handler for streaming files
[ https://issues.apache.org/jira/browse/CASSANDRASC-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-37: Change Category: Performance Complexity: Normal Reviewers: Dinesh A. Joshi, Yifan Cai Assignee: Saranya Krishnakumar Status: Open (was: Triage Needed) > Optimize file path builder and have a new handler for streaming files > - > > Key: CASSANDRASC-37 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-37 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > This patch optimizes file path builder and creates a new handler for > streaming files. This handler is chained along with validation handlers for > an endpoint -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-37) Optimize file path builder and have a new handler for streaming files
[ https://issues.apache.org/jira/browse/CASSANDRASC-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-37: Description: This patch optimizes file path builder and creates a new handler for streaming files. This handler is chained along with validation handlers for an endpoint PR: https://github.com/apache/cassandra-sidecar/pull/29 was:This patch optimizes file path builder and creates a new handler for streaming files. This handler is chained along with validation handlers for an endpoint > Optimize file path builder and have a new handler for streaming files > - > > Key: CASSANDRASC-37 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-37 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > This patch optimizes file path builder and creates a new handler for > streaming files. This handler is chained along with validation handlers for > an endpoint > PR: https://github.com/apache/cassandra-sidecar/pull/29 -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRASC-37) Optimize file path builder and have a new handler for streaming files
Saranya Krishnakumar created CASSANDRASC-37: --- Summary: Optimize file path builder and have a new handler for streaming files Key: CASSANDRASC-37 URL: https://issues.apache.org/jira/browse/CASSANDRASC-37 Project: Sidecar for Apache Cassandra Issue Type: Improvement Components: Rest API Reporter: Saranya Krishnakumar This patch optimizes file path builder and creates a new handler for streaming files. This handler is chained along with validation handlers for an endpoint -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15297) nodetool can not create snapshot with snapshot name that have special character
[
https://issues.apache.org/jira/browse/CASSANDRA-15297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488516#comment-17488516
]
Saranya Krishnakumar commented on CASSANDRA-15297:
--
Thanks for pointing, made the change to use
{code:java}
File.pathSeparator() {code}
> nodetool can not create snapshot with snapshot name that have special
> character
> ---
>
> Key: CASSANDRA-15297
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15297
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/nodetool
>Reporter: maxwellguo
>Assignee: Saranya Krishnakumar
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.x
>
> Attachments: after-fix.jpg, image.png, listsnapshots-p-s.jpg,
> snapshot-listsnapshot-.jpg, snapshot-p-s.jpg
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> we make snapshot through "nodetool snapshot -t snapshotname " , when
> snapshotname contains special characters like "/", the make snapshot process
> successfully , but the result
> can be different ,when we check the data file directory or use "nodetool
> listsnapshots".
> here is some case :
> 1. nodetool snapshot -t "p/s"
> the listsnapshot resturns snapshot p for all table but actually the snapshot
> name is "p/s";
> also the data directory is like the format :
> datapath/snapshots/p/s/snapshot-datafile-link
> !snapshot-p-s.jpg!
> !listsnapshots-p-s.jpg!
> 2. nodetool snapshot -t "/"
> the listsnapshot resturns "there is not snapshot"; but the make snapshot
> process return successfully and the data directory is like the format :
> datapath/snapshots/snapshot-datafile-link
> !snapshot-listsnapshot-.jpg!
> the Attachements are the result under our environment.
> so for me , we suggest that the snapshot name should not contains special
> character. just throw exception and told the user not to use special
> character.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-33) Optionally support multiple Cassandra instances in Sidecar
[ https://issues.apache.org/jira/browse/CASSANDRASC-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-33: Authors: Saranya Krishnakumar Test and Documentation Plan: Unit tests Status: Patch Available (was: Open) > Optionally support multiple Cassandra instances in Sidecar > -- > > Key: CASSANDRASC-33 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-33 > Project: Sidecar for Apache Cassandra > Issue Type: New Feature > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > Currently Sidecar supports only one Cassandra instance, we want to optionally > support multiple Cassandra instances -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-33) Optionally support multiple Cassandra instances in Sidecar
[ https://issues.apache.org/jira/browse/CASSANDRASC-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-33: Change Category: Operability Complexity: Normal Component/s: Rest API (was: Configuration) Reviewers: Dinesh Joshi, Yifan Cai Status: Open (was: Triage Needed) [https://github.com/apache/cassandra-sidecar/pull/25.] Tested with unit tests > Optionally support multiple Cassandra instances in Sidecar > -- > > Key: CASSANDRASC-33 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-33 > Project: Sidecar for Apache Cassandra > Issue Type: New Feature > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > Currently Sidecar supports only one Cassandra instance, we want to optionally > support multiple Cassandra instances -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-15297) nodetool can not create snapshot with snapshot name that have special character
[ https://issues.apache.org/jira/browse/CASSANDRA-15297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar reassigned CASSANDRA-15297: Assignee: Saranya Krishnakumar (was: maxwellguo) > nodetool can not create snapshot with snapshot name that have special > character > --- > > Key: CASSANDRA-15297 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15297 > Project: Cassandra > Issue Type: Bug > Components: Tool/nodetool >Reporter: maxwellguo >Assignee: Saranya Krishnakumar >Priority: Normal > Labels: pull-request-available > Fix For: 4.x > > Attachments: after-fix.jpg, image.png, listsnapshots-p-s.jpg, > snapshot-listsnapshot-.jpg, snapshot-p-s.jpg > > Time Spent: 0.5h > Remaining Estimate: 0h > > we make snapshot through "nodetool snapshot -t snapshotname " , when > snapshotname contains special characters like "/", the make snapshot process > successfully , but the result > can be different ,when we check the data file directory or use "nodetool > listsnapshots". > here is some case : > 1. nodetool snapshot -t "p/s" > the listsnapshot resturns snapshot p for all table but actually the snapshot > name is "p/s"; > also the data directory is like the format : > datapath/snapshots/p/s/snapshot-datafile-link > !snapshot-p-s.jpg! > !listsnapshots-p-s.jpg! > 2. nodetool snapshot -t "/" > the listsnapshot resturns "there is not snapshot"; but the make snapshot > process return successfully and the data directory is like the format : > datapath/snapshots/snapshot-datafile-link > !snapshot-listsnapshot-.jpg! > the Attachements are the result under our environment. > so for me , we suggest that the snapshot name should not contains special > character. just throw exception and told the user not to use special > character. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
