[jira] [Comment Edited] (CASSANDRA-19480) [Analytics] Report task level job stats from analytics
[ https://issues.apache.org/jira/browse/CASSANDRA-19480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841006#comment-17841006 ] Arjun Ashok edited comment on CASSANDRA-19480 at 4/26/24 1:33 AM: -- PR: [https://github.com/apache/cassandra-analytics/pull/51] CI: [https://app.circleci.com/pipelines/github/arjunashok/cassandra-analytics/94/workflows/02190c2f-e40f-402c-bce2-facd2fd829f8] was (Author: JIRAUSER301082): PR: [https://github.com/apache/cassandra-analytics/pull/55] CI: https://app.circleci.com/pipelines/github/arjunashok/cassandra-analytics?branch=CASSANDRA-19480-2 > [Analytics] Report task level job stats from analytics > -- > > Key: CASSANDRA-19480 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19480 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > > This is an extension of > https://issues.apache.org/jira/browse/CASSANDRA-19418. to instrument spark > task level metrics such as max task retries and task execution time stats > (max, median, p90 across tasks within the job) from the analytics library. > -- 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-19480) [Analytics] Report task level job stats from analytics
[ https://issues.apache.org/jira/browse/CASSANDRA-19480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841006#comment-17841006 ] Arjun Ashok edited comment on CASSANDRA-19480 at 4/25/24 11:41 PM: --- PR: [https://github.com/apache/cassandra-analytics/pull/55] CI: https://app.circleci.com/pipelines/github/arjunashok/cassandra-analytics?branch=CASSANDRA-19480-2 was (Author: JIRAUSER301082): PR: https://github.com/apache/cassandra-analytics/pull/55 > [Analytics] Report task level job stats from analytics > -- > > Key: CASSANDRA-19480 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19480 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > > This is an extension of > https://issues.apache.org/jira/browse/CASSANDRA-19418. to instrument spark > task level metrics such as max task retries and task execution time stats > (max, median, p90 across tasks within the job) from the analytics library. > -- 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-19480) [Analytics] Report task level job stats from analytics
[ https://issues.apache.org/jira/browse/CASSANDRA-19480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841006#comment-17841006 ] Arjun Ashok commented on CASSANDRA-19480: - PR: https://github.com/apache/cassandra-analytics/pull/55 > [Analytics] Report task level job stats from analytics > -- > > Key: CASSANDRA-19480 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19480 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > > This is an extension of > https://issues.apache.org/jira/browse/CASSANDRA-19418. to instrument spark > task level metrics such as max task retries and task execution time stats > (max, median, p90 across tasks within the job) from the analytics library. > -- 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-19480) [Analytics] Report task level job stats from analytics
[ https://issues.apache.org/jira/browse/CASSANDRA-19480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok updated CASSANDRA-19480: Change Category: Operability Complexity: Normal Status: Open (was: Triage Needed) > [Analytics] Report task level job stats from analytics > -- > > Key: CASSANDRA-19480 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19480 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > > This is an extension of > https://issues.apache.org/jira/browse/CASSANDRA-19418. to instrument spark > task level metrics such as max task retries and task execution time stats > (max, median, p90 across tasks within the job) from the analytics library. > -- 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] [Assigned] (CASSANDRA-19480) [Analytics] Report task level job stats from analytics
[ https://issues.apache.org/jira/browse/CASSANDRA-19480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok reassigned CASSANDRA-19480: --- Assignee: Arjun Ashok > [Analytics] Report task level job stats from analytics > -- > > Key: CASSANDRA-19480 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19480 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > > This is an extension of > https://issues.apache.org/jira/browse/CASSANDRA-19418. to instrument spark > task level metrics such as max task retries and task execution time stats > (max, median, p90 across tasks within the job) from the analytics library. > -- 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-19418) [Analytics] Report additional bulk analytics job stats for instrumentation
[ https://issues.apache.org/jira/browse/CASSANDRA-19418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829663#comment-17829663 ] Arjun Ashok edited comment on CASSANDRA-19418 at 3/21/24 9:34 PM: -- CI is green: https://app.circleci.com/pipelines/github/arjunashok/cassandra-analytics/78/workflows/4cf445d1-1a4c-430a-a498-54341f754996 was (Author: JIRAUSER301082): CI is green: https://app.circleci.com/pipelines/github/arjunashok/cassandra-analytics/77/workflows/f87b3605-f5b2-4f50-a039-b55822b43e2c > [Analytics] Report additional bulk analytics job stats for instrumentation > -- > > Key: CASSANDRA-19418 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19418 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Time Spent: 3h > Remaining Estimate: 0h > > Currently, the Cassandra bulk analytics library supports a "dialHome" API to > publish some initial job metadata, which in its current form, is redirected > to a log. The intention behind this is to allow custom implementations that > can utilize these summarized stats for instrumentation or reporting of client > behavior. > This task is meant to enhance this API to allow for additional job metadata > to be published both at the Spark executor level and at the task levels to > gather stats such as "success/failure", "number of rows written/read", > "failure reason" etc. -- 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-19418) [Analytics] Report additional bulk analytics job stats for instrumentation
[ https://issues.apache.org/jira/browse/CASSANDRA-19418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok updated CASSANDRA-19418: Test and Documentation Plan: Validated unit/integration tests and on a test cluster. CI is green Status: Patch Available (was: Open) > [Analytics] Report additional bulk analytics job stats for instrumentation > -- > > Key: CASSANDRA-19418 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19418 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Time Spent: 3h > Remaining Estimate: 0h > > Currently, the Cassandra bulk analytics library supports a "dialHome" API to > publish some initial job metadata, which in its current form, is redirected > to a log. The intention behind this is to allow custom implementations that > can utilize these summarized stats for instrumentation or reporting of client > behavior. > This task is meant to enhance this API to allow for additional job metadata > to be published both at the Spark executor level and at the task levels to > gather stats such as "success/failure", "number of rows written/read", > "failure reason" etc. -- 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-19418) [Analytics] Report additional bulk analytics job stats for instrumentation
[ https://issues.apache.org/jira/browse/CASSANDRA-19418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829663#comment-17829663 ] Arjun Ashok edited comment on CASSANDRA-19418 at 3/21/24 7:07 PM: -- CI is green: https://app.circleci.com/pipelines/github/arjunashok/cassandra-analytics/77/workflows/f87b3605-f5b2-4f50-a039-b55822b43e2c was (Author: JIRAUSER301082): CI: [https://app.circleci.com/pipelines/github/arjunashok/cassandra-analytics/76/workflows/662c438a-7541-4a53-a9e9-08b8d472e6df|https://app.circleci.com/pipelines/github/arjunashok/cassandra-analytics/77/workflows/fc6fd747-80ea-425e-bb2c-3998647f7a42] > [Analytics] Report additional bulk analytics job stats for instrumentation > -- > > Key: CASSANDRA-19418 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19418 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Time Spent: 3h > Remaining Estimate: 0h > > Currently, the Cassandra bulk analytics library supports a "dialHome" API to > publish some initial job metadata, which in its current form, is redirected > to a log. The intention behind this is to allow custom implementations that > can utilize these summarized stats for instrumentation or reporting of client > behavior. > This task is meant to enhance this API to allow for additional job metadata > to be published both at the Spark executor level and at the task levels to > gather stats such as "success/failure", "number of rows written/read", > "failure reason" etc. -- 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-19418) [Analytics] Report additional bulk analytics job stats for instrumentation
[ https://issues.apache.org/jira/browse/CASSANDRA-19418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829663#comment-17829663 ] Arjun Ashok edited comment on CASSANDRA-19418 at 3/21/24 6:25 PM: -- CI: [https://app.circleci.com/pipelines/github/arjunashok/cassandra-analytics/76/workflows/662c438a-7541-4a53-a9e9-08b8d472e6df|https://app.circleci.com/pipelines/github/arjunashok/cassandra-analytics/77/workflows/fc6fd747-80ea-425e-bb2c-3998647f7a42] was (Author: JIRAUSER301082): CI: https://app.circleci.com/pipelines/github/arjunashok/cassandra-analytics/76/workflows/662c438a-7541-4a53-a9e9-08b8d472e6df > [Analytics] Report additional bulk analytics job stats for instrumentation > -- > > Key: CASSANDRA-19418 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19418 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Time Spent: 3h > Remaining Estimate: 0h > > Currently, the Cassandra bulk analytics library supports a "dialHome" API to > publish some initial job metadata, which in its current form, is redirected > to a log. The intention behind this is to allow custom implementations that > can utilize these summarized stats for instrumentation or reporting of client > behavior. > This task is meant to enhance this API to allow for additional job metadata > to be published both at the Spark executor level and at the task levels to > gather stats such as "success/failure", "number of rows written/read", > "failure reason" etc. -- 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-19418) [Analytics] Report additional bulk analytics job stats for instrumentation
[ https://issues.apache.org/jira/browse/CASSANDRA-19418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok updated CASSANDRA-19418: Complexity: Normal Status: Open (was: Triage Needed) > [Analytics] Report additional bulk analytics job stats for instrumentation > -- > > Key: CASSANDRA-19418 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19418 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Time Spent: 3h > Remaining Estimate: 0h > > Currently, the Cassandra bulk analytics library supports a "dialHome" API to > publish some initial job metadata, which in its current form, is redirected > to a log. The intention behind this is to allow custom implementations that > can utilize these summarized stats for instrumentation or reporting of client > behavior. > This task is meant to enhance this API to allow for additional job metadata > to be published both at the Spark executor level and at the task levels to > gather stats such as "success/failure", "number of rows written/read", > "failure reason" etc. -- 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-19418) [Analytics] Report additional bulk analytics job stats for instrumentation
[ https://issues.apache.org/jira/browse/CASSANDRA-19418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829663#comment-17829663 ] Arjun Ashok commented on CASSANDRA-19418: - CI: https://app.circleci.com/pipelines/github/arjunashok/cassandra-analytics/76/workflows/662c438a-7541-4a53-a9e9-08b8d472e6df > [Analytics] Report additional bulk analytics job stats for instrumentation > -- > > Key: CASSANDRA-19418 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19418 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Time Spent: 3h > Remaining Estimate: 0h > > Currently, the Cassandra bulk analytics library supports a "dialHome" API to > publish some initial job metadata, which in its current form, is redirected > to a log. The intention behind this is to allow custom implementations that > can utilize these summarized stats for instrumentation or reporting of client > behavior. > This task is meant to enhance this API to allow for additional job metadata > to be published both at the Spark executor level and at the task levels to > gather stats such as "success/failure", "number of rows written/read", > "failure reason" etc. -- 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-19480) [Analytics] Report task level job stats from analytics
Arjun Ashok created CASSANDRA-19480: --- Summary: [Analytics] Report task level job stats from analytics Key: CASSANDRA-19480 URL: https://issues.apache.org/jira/browse/CASSANDRA-19480 Project: Cassandra Issue Type: Task Components: Analytics Library Reporter: Arjun Ashok This is an extension of https://issues.apache.org/jira/browse/CASSANDRA-19418. to instrument spark task level metrics such as max task retries and task execution time stats (max, median, p90 across tasks within the job) from the analytics library. -- 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] [Assigned] (CASSANDRA-19418) [Analytics] Report additional bulk analytics job stats for instrumentation
[ https://issues.apache.org/jira/browse/CASSANDRA-19418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok reassigned CASSANDRA-19418: --- Assignee: Arjun Ashok > [Analytics] Report additional bulk analytics job stats for instrumentation > -- > > Key: CASSANDRA-19418 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19418 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > > Currently, the Cassandra bulk analytics library supports a "dialHome" API to > publish some initial job metadata, which in its current form, is redirected > to a log. The intention behind this is to allow custom implementations that > can utilize these summarized stats for instrumentation or reporting of client > behavior. > This task is meant to enhance this API to allow for additional job metadata > to be published both at the Spark executor level and at the task levels to > gather stats such as "success/failure", "number of rows written/read", > "failure reason" etc. -- 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-19418) [Analytics] Report additional bulk analytics job stats for instrumentation
[ https://issues.apache.org/jira/browse/CASSANDRA-19418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok updated CASSANDRA-19418: Component/s: Analytics Library > [Analytics] Report additional bulk analytics job stats for instrumentation > -- > > Key: CASSANDRA-19418 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19418 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Arjun Ashok >Priority: Normal > > Currently, the Cassandra bulk analytics library supports a "dialHome" API to > publish some initial job metadata, which in its current form, is redirected > to a log. The intention behind this is to allow custom implementations that > can utilize these summarized stats for instrumentation or reporting of client > behavior. > This task is meant to enhance this API to allow for additional job metadata > to be published both at the Spark executor level and at the task levels to > gather stats such as "success/failure", "number of rows written/read", > "failure reason" etc. -- 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-19418) [Analytics] Report additional bulk analytics job stats for instrumentation
[ https://issues.apache.org/jira/browse/CASSANDRA-19418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok updated CASSANDRA-19418: Change Category: Operability > [Analytics] Report additional bulk analytics job stats for instrumentation > -- > > Key: CASSANDRA-19418 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19418 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Arjun Ashok >Priority: Normal > > Currently, the Cassandra bulk analytics library supports a "dialHome" API to > publish some initial job metadata, which in its current form, is redirected > to a log. The intention behind this is to allow custom implementations that > can utilize these summarized stats for instrumentation or reporting of client > behavior. > This task is meant to enhance this API to allow for additional job metadata > to be published both at the Spark executor level and at the task levels to > gather stats such as "success/failure", "number of rows written/read", > "failure reason" etc. -- 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-19418) [Analytics] Report additional bulk analytics job stats for instrumentation
Arjun Ashok created CASSANDRA-19418: --- Summary: [Analytics] Report additional bulk analytics job stats for instrumentation Key: CASSANDRA-19418 URL: https://issues.apache.org/jira/browse/CASSANDRA-19418 Project: Cassandra Issue Type: Task Reporter: Arjun Ashok Currently, the Cassandra bulk analytics library supports a "dialHome" API to publish some initial job metadata, which in its current form, is redirected to a log. The intention behind this is to allow custom implementations that can utilize these summarized stats for instrumentation or reporting of client behavior. This task is meant to enhance this API to allow for additional job metadata to be published both at the Spark executor level and at the task levels to gather stats such as "success/failure", "number of rows written/read", "failure reason" etc. -- 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-19331) [Analytics] Improve logging for bulk writes and on task failures
[ https://issues.apache.org/jira/browse/CASSANDRA-19331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812494#comment-17812494 ] Arjun Ashok commented on CASSANDRA-19331: - Link to green CI: https://app.circleci.com/pipelines/github/arjunashok/cassandra-analytics/64/workflows/b64b0f6e-a202-468a-8d1c-37b135a798f1 > [Analytics] Improve logging for bulk writes and on task failures > > > Key: CASSANDRA-19331 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19331 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Time Spent: 1.5h > Remaining Estimate: 0h > > Builds on top of the resiliency changes to add additional logging around > token-range metadata fetched from C* during bulk-writes, and also > specifically for case when the spark task fails when the cluster is resized. -- 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-19331) [Analytics] Improve logging for bulk writes and on task failures
[ https://issues.apache.org/jira/browse/CASSANDRA-19331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok updated CASSANDRA-19331: Test and Documentation Plan: Validated unit/integration tests Status: Patch Available (was: In Progress) > [Analytics] Improve logging for bulk writes and on task failures > > > Key: CASSANDRA-19331 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19331 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Time Spent: 1.5h > Remaining Estimate: 0h > > Builds on top of the resiliency changes to add additional logging around > token-range metadata fetched from C* during bulk-writes, and also > specifically for case when the spark task fails when the cluster is resized. -- 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-19331) [Analytics] Improve logging for bulk writes and on task failures
[ https://issues.apache.org/jira/browse/CASSANDRA-19331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811369#comment-17811369 ] Arjun Ashok commented on CASSANDRA-19331: - PR: https://github.com/apache/cassandra-analytics/pull/35 CI: https://app.circleci.com/pipelines/github/arjunashok/cassandra-analytics?branch=CASSANDRA-19331 > [Analytics] Improve logging for bulk writes and on task failures > > > Key: CASSANDRA-19331 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19331 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > Builds on top of the resiliency changes to add additional logging around > token-range metadata fetched from C* during bulk-writes, and also > specifically for case when the spark task fails when the cluster is resized. -- 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-19331) [Analytics] Improve logging for bulk writes and on task failures
[ https://issues.apache.org/jira/browse/CASSANDRA-19331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok updated CASSANDRA-19331: Change Category: Operability Complexity: Low Hanging Fruit Component/s: Analytics Library Status: Open (was: Triage Needed) > [Analytics] Improve logging for bulk writes and on task failures > > > Key: CASSANDRA-19331 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19331 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > > Builds on top of the resiliency changes to add additional logging around > token-range metadata fetched from C* during bulk-writes, and also > specifically for case when the spark task fails when the cluster is resized. -- 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] [Assigned] (CASSANDRA-19331) [Analytics] Improve logging for bulk writes and on task failures
[ https://issues.apache.org/jira/browse/CASSANDRA-19331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok reassigned CASSANDRA-19331: --- Assignee: Arjun Ashok > [Analytics] Improve logging for bulk writes and on task failures > > > Key: CASSANDRA-19331 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19331 > Project: Cassandra > Issue Type: Task >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > > Builds on top of the resiliency changes to add additional logging around > token-range metadata fetched from C* during bulk-writes, and also > specifically for case when the spark task fails when the cluster is resized. -- 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-19331) [Analytics] Improve logging for bulk writes and on task failures
Arjun Ashok created CASSANDRA-19331: --- Summary: [Analytics] Improve logging for bulk writes and on task failures Key: CASSANDRA-19331 URL: https://issues.apache.org/jira/browse/CASSANDRA-19331 Project: Cassandra Issue Type: Task Reporter: Arjun Ashok Builds on top of the resiliency changes to add additional logging around token-range metadata fetched from C* during bulk-writes, and also specifically for case when the spark task fails when the cluster is resized. -- 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-19272) [Analytics] Add integration tests using in-jvm-dtest to cover blocklisted instances
[ https://issues.apache.org/jira/browse/CASSANDRA-19272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17807892#comment-17807892 ] Arjun Ashok edited comment on CASSANDRA-19272 at 1/17/24 9:05 PM: -- PR: [https://github.com/apache/cassandra-analytics/pull/32] CI: [https://app.circleci.com/pipelines/github/arjunashok/cassandra-analytics/57/workflows/bb0e357f-1866-44e4-91a1-f627afb07d56] was (Author: JIRAUSER301082): PR: https://github.com/apache/cassandra-analytics/pull/32 CI: [https://app.circleci.com/pipelines/github/arjunashok/cassandra-analytics/57/workflows/bb0e357f-1866-44e4-91a1-f627afb07d56] > [Analytics] Add integration tests using in-jvm-dtest to cover blocklisted > instances > --- > > Key: CASSANDRA-19272 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19272 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > > Scope: > - Add default mechanism to load blocklist from configuration > - Relevant in-jvm-dtest based integration tests to validate the CL > validations for different CL combinations -- 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-19272) [Analytics] Add integration tests using in-jvm-dtest to cover blocklisted instances
[ https://issues.apache.org/jira/browse/CASSANDRA-19272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17807892#comment-17807892 ] Arjun Ashok edited comment on CASSANDRA-19272 at 1/17/24 9:05 PM: -- PR: https://github.com/apache/cassandra-analytics/pull/32 CI: [https://app.circleci.com/pipelines/github/arjunashok/cassandra-analytics/57/workflows/bb0e357f-1866-44e4-91a1-f627afb07d56] was (Author: JIRAUSER301082): CI: https://app.circleci.com/pipelines/github/arjunashok/cassandra-analytics/57/workflows/bb0e357f-1866-44e4-91a1-f627afb07d56 > [Analytics] Add integration tests using in-jvm-dtest to cover blocklisted > instances > --- > > Key: CASSANDRA-19272 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19272 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > > Scope: > - Add default mechanism to load blocklist from configuration > - Relevant in-jvm-dtest based integration tests to validate the CL > validations for different CL combinations -- 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] (CASSANDRA-19257) [Analytics] Fix bulk writer consistency level validations for blocked instances
[ https://issues.apache.org/jira/browse/CASSANDRA-19257 ] Arjun Ashok deleted comment on CASSANDRA-19257: - was (Author: JIRAUSER301082): CI: https://app.circleci.com/pipelines/github/arjunashok/cassandra-analytics/57/workflows/bb0e357f-1866-44e4-91a1-f627afb07d56 > [Analytics] Fix bulk writer consistency level validations for blocked > instances > --- > > Key: CASSANDRA-19257 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19257 > Project: Cassandra > Issue Type: Bug > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Fix For: NA > > Time Spent: 1h 10m > Remaining Estimate: 0h > > The analytics library bulk writer spark job performs consistency level > validations around write operations. > Currently, these validations incorrectly double count the number of blocked > instances for these validations resulting in valid scenarios failing CL > checks. -- 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-19272) [Analytics] Add integration tests using in-jvm-dtest to cover blocklisted instances
[ https://issues.apache.org/jira/browse/CASSANDRA-19272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok updated CASSANDRA-19272: Test and Documentation Plan: Added integration tests for CL validations with blocked instances Status: Patch Available (was: In Progress) > [Analytics] Add integration tests using in-jvm-dtest to cover blocklisted > instances > --- > > Key: CASSANDRA-19272 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19272 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > > Scope: > - Add default mechanism to load blocklist from configuration > - Relevant in-jvm-dtest based integration tests to validate the CL > validations for different CL combinations -- 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-19272) [Analytics] Add integration tests using in-jvm-dtest to cover blocklisted instances
[ https://issues.apache.org/jira/browse/CASSANDRA-19272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok updated CASSANDRA-19272: Change Category: Quality Assurance Complexity: Low Hanging Fruit Status: Open (was: Triage Needed) > [Analytics] Add integration tests using in-jvm-dtest to cover blocklisted > instances > --- > > Key: CASSANDRA-19272 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19272 > Project: Cassandra > Issue Type: Task > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > > Scope: > - Add default mechanism to load blocklist from configuration > - Relevant in-jvm-dtest based integration tests to validate the CL > validations for different CL combinations -- 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-19272) [Analytics] Add integration tests using in-jvm-dtest to cover blocklisted instances
Arjun Ashok created CASSANDRA-19272: --- Summary: [Analytics] Add integration tests using in-jvm-dtest to cover blocklisted instances Key: CASSANDRA-19272 URL: https://issues.apache.org/jira/browse/CASSANDRA-19272 Project: Cassandra Issue Type: Task Components: Analytics Library Reporter: Arjun Ashok Scope: - Add default mechanism to load blocklist from configuration - Relevant in-jvm-dtest based integration tests to validate the CL validations for different CL combinations -- 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-19257) [Analytics] Fix bulk writer consistency level validations for blocked instances
[ https://issues.apache.org/jira/browse/CASSANDRA-19257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805314#comment-17805314 ] Arjun Ashok commented on CASSANDRA-19257: - CI: https://app.circleci.com/pipelines/github/arjunashok/cassandra-analytics/53/workflows/a1ff2f41-7f21-465c-90c8-eb8a6f799dd5 > [Analytics] Fix bulk writer consistency level validations for blocked > instances > --- > > Key: CASSANDRA-19257 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19257 > Project: Cassandra > Issue Type: Bug > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Time Spent: 50m > Remaining Estimate: 0h > > The analytics library bulk writer spark job performs consistency level > validations around write operations. > Currently, these validations incorrectly double count the number of blocked > instances for these validations resulting in valid scenarios failing CL > checks. -- 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-19257) [Analytics] Fix bulk writer consistency level validations for blocked instances
[ https://issues.apache.org/jira/browse/CASSANDRA-19257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok updated CASSANDRA-19257: Test and Documentation Plan: Added unit test to validate fix and no uploads to blocked instances. Status: Patch Available (was: In Progress) > [Analytics] Fix bulk writer consistency level validations for blocked > instances > --- > > Key: CASSANDRA-19257 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19257 > Project: Cassandra > Issue Type: Bug > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Time Spent: 50m > Remaining Estimate: 0h > > The analytics library bulk writer spark job performs consistency level > validations around write operations. > Currently, these validations incorrectly double count the number of blocked > instances for these validations resulting in valid scenarios failing CL > checks. -- 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-19257) [Analytics] Fix bulk writer consistency level validations for blocked instances
[ https://issues.apache.org/jira/browse/CASSANDRA-19257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok updated CASSANDRA-19257: Bug Category: Parent values: Correctness(12982) Complexity: Low Hanging Fruit Discovered By: Adhoc Test Severity: Normal Assignee: Arjun Ashok Status: Open (was: Triage Needed) > [Analytics] Fix bulk writer consistency level validations for blocked > instances > --- > > Key: CASSANDRA-19257 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19257 > Project: Cassandra > Issue Type: Bug > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > > The analytics library bulk writer spark job performs consistency level > validations around write operations. > Currently, these validations incorrectly double count the number of blocked > instances for these validations resulting in valid scenarios failing CL > checks. -- 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-19257) [Analytics] Fix bulk writer consistency level validations for blocked instances
Arjun Ashok created CASSANDRA-19257: --- Summary: [Analytics] Fix bulk writer consistency level validations for blocked instances Key: CASSANDRA-19257 URL: https://issues.apache.org/jira/browse/CASSANDRA-19257 Project: Cassandra Issue Type: Bug Components: Analytics Library Reporter: Arjun Ashok The analytics library bulk writer spark job performs consistency level validations around write operations. Currently, these validations incorrectly double count the number of blocked instances for these validations resulting in valid scenarios failing CL checks. -- 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-90) Fix Sidecar TokenRangeReplicas endpoint to unwrap the token-range by partitioner's range for a single node clusters
[ https://issues.apache.org/jira/browse/CASSANDRASC-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok updated CASSANDRASC-90: --- Description: The sidecar token-range-replicas endpoint returns an empty range for the write replicas for single node clusters, due to a bug that fails to unwrap such ranges returned from Cassandra around the partitioner's token boundary. CI: https://app.circleci.com/pipelines/github/arjunashok/cassandra-sidecar/73/workflows/c95e7468-7c7b-4f52-8e23-054c583fcc7f was:The sidecar token-range-replicas endpoint returns an empty range for the write replicas for single node clusters, due to a bug that fails to unwrap such ranges returned from Cassandra around the partitioner's token boundary. > Fix Sidecar TokenRangeReplicas endpoint to unwrap the token-range by > partitioner's range for a single node clusters > --- > > Key: CASSANDRASC-90 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-90 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Labels: pull-request-available > > The sidecar token-range-replicas endpoint returns an empty range for the > write replicas for single node clusters, due to a bug that fails to unwrap > such ranges returned from Cassandra around the partitioner's token boundary. > > CI: > https://app.circleci.com/pipelines/github/arjunashok/cassandra-sidecar/73/workflows/c95e7468-7c7b-4f52-8e23-054c583fcc7f -- 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-90) Fix Sidecar TokenRangeReplicas endpoint to unwrap the token-range by partitioner's range for a single node clusters
[ https://issues.apache.org/jira/browse/CASSANDRASC-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok updated CASSANDRASC-90: --- Authors: Arjun Ashok Test and Documentation Plan: Added relevant unit tests to validate fix. Status: Patch Available (was: In Progress) > Fix Sidecar TokenRangeReplicas endpoint to unwrap the token-range by > partitioner's range for a single node clusters > --- > > Key: CASSANDRASC-90 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-90 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Labels: pull-request-available > > The sidecar token-range-replicas endpoint returns an empty range for the > write replicas for single node clusters, due to a bug that fails to unwrap > such ranges returned from Cassandra around the partitioner's token boundary. -- 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-90) Fix Sidecar TokenRangeReplicas endpoint to unwrap the token-range by partitioner's range for a single node clusters
[ https://issues.apache.org/jira/browse/CASSANDRASC-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok updated CASSANDRASC-90: --- Bug Category: Parent values: Correctness(12982) Complexity: Normal Discovered By: DTest Reviewers: Francisco Guerrero Severity: Normal Status: Open (was: Triage Needed) > Fix Sidecar TokenRangeReplicas endpoint to unwrap the token-range by > partitioner's range for a single node clusters > --- > > Key: CASSANDRASC-90 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-90 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Labels: pull-request-available > > The sidecar token-range-replicas endpoint returns an empty range for the > write replicas for single node clusters, due to a bug that fails to unwrap > such ranges returned from Cassandra around the partitioner's token boundary. -- 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-90) Fix Sidecar TokenRangeReplicas endpoint to unwrap the token-range by partitioner's range for a single node clusters
Arjun Ashok created CASSANDRASC-90: -- Summary: Fix Sidecar TokenRangeReplicas endpoint to unwrap the token-range by partitioner's range for a single node clusters Key: CASSANDRASC-90 URL: https://issues.apache.org/jira/browse/CASSANDRASC-90 Project: Sidecar for Apache Cassandra Issue Type: Bug Components: Rest API Reporter: Arjun Ashok Assignee: Arjun Ashok The sidecar token-range-replicas endpoint returns an empty range for the write replicas for single node clusters, due to a bug that fails to unwrap such ranges returned from Cassandra around the partitioner's token boundary. -- 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-78) Fix token-ranges endpoint to handle gossip-info responses without 'status'
[
https://issues.apache.org/jira/browse/CASSANDRASC-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17778823#comment-17778823
]
Arjun Ashok commented on CASSANDRASC-78:
CI:
https://app.circleci.com/pipelines/github/arjunashok/cassandra-sidecar/66/workflows/8ea22382-9f51-4535-bf40-c1bf49ae7f78
> Fix token-ranges endpoint to handle gossip-info responses without 'status'
> --
>
> Key: CASSANDRASC-78
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-78
> Project: Sidecar for Apache Cassandra
> Issue Type: Bug
> Components: Rest API
>Reporter: Arjun Ashok
>Assignee: Arjun Ashok
>Priority: Normal
> Labels: pull-request-available
>
> This is a fix to look for the host status in ‘Status’ and ‘StatusWithPort’
> attributes in GossipInfo response to determine the ‘state’ of the node.
> Currently, we only check for ‘status’ which can be missing from gossipInfo in
> some cases, which will result in a replacement node status to be reported as
> `Joining` instead of `Replacing`.
> eg.
> {code:java}
> Found gossipInfoEntry={generation=1697736379,
> schema=6d6abc83-a600-35a4-8bbe-fe5edca6a63b, rack=rack1, heartbeat=119,
> releaseVersion=4.1.4-SNAPSHOT, hostId=--4000-8000-0006,
> nativeAddressAndPort=127.0.0.6:9042, load=76459.0,
> internalAddressAndPort=127.0.0.6:7012, sstableVersions=big-nb,
> tokens=, dc=datacenter1, netVersion=12,
> statusWithPort=BOOT_REPLACE,127.0.0.5:7012}{code}
--
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-78) Fix token-ranges endpoint to handle gossip-info responses without 'status'
[
https://issues.apache.org/jira/browse/CASSANDRASC-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arjun Ashok updated CASSANDRASC-78:
---
Authors: Arjun Ashok
Test and Documentation Plan: Validated fix in unit tests and in-jvm-dtests
Status: Patch Available (was: In Progress)
> Fix token-ranges endpoint to handle gossip-info responses without 'status'
> --
>
> Key: CASSANDRASC-78
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-78
> Project: Sidecar for Apache Cassandra
> Issue Type: Bug
> Components: Rest API
>Reporter: Arjun Ashok
>Assignee: Arjun Ashok
>Priority: Normal
> Labels: pull-request-available
>
> This is a fix to look for the host status in ‘Status’ and ‘StatusWithPort’
> attributes in GossipInfo response to determine the ‘state’ of the node.
> Currently, we only check for ‘status’ which can be missing from gossipInfo in
> some cases, which will result in a replacement node status to be reported as
> `Joining` instead of `Replacing`.
> eg.
> {code:java}
> Found gossipInfoEntry={generation=1697736379,
> schema=6d6abc83-a600-35a4-8bbe-fe5edca6a63b, rack=rack1, heartbeat=119,
> releaseVersion=4.1.4-SNAPSHOT, hostId=--4000-8000-0006,
> nativeAddressAndPort=127.0.0.6:9042, load=76459.0,
> internalAddressAndPort=127.0.0.6:7012, sstableVersions=big-nb,
> tokens=, dc=datacenter1, netVersion=12,
> statusWithPort=BOOT_REPLACE,127.0.0.5:7012}{code}
--
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-78) Fix token-ranges endpoint to handle gossip-info responses without 'status'
[
https://issues.apache.org/jira/browse/CASSANDRASC-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arjun Ashok updated CASSANDRASC-78:
---
Bug Category: Parent values: Correctness(12982)
Complexity: Normal
Discovered By: Unit Test
Severity: Normal
Status: Open (was: Triage Needed)
> Fix token-ranges endpoint to handle gossip-info responses without 'status'
> --
>
> Key: CASSANDRASC-78
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-78
> Project: Sidecar for Apache Cassandra
> Issue Type: Bug
> Components: Rest API
>Reporter: Arjun Ashok
>Assignee: Arjun Ashok
>Priority: Normal
>
> This is a fix to look for the host status in ‘Status’ and ‘StatusWithPort’
> attributes in GossipInfo response to determine the ‘state’ of the node.
> Currently, we only check for ‘status’ which can be missing from gossipInfo in
> some cases, which will result in a replacement node status to be reported as
> `Joining` instead of `Replacing`.
> eg.
> {code:java}
> Found gossipInfoEntry={generation=1697736379,
> schema=6d6abc83-a600-35a4-8bbe-fe5edca6a63b, rack=rack1, heartbeat=119,
> releaseVersion=4.1.4-SNAPSHOT, hostId=--4000-8000-0006,
> nativeAddressAndPort=127.0.0.6:9042, load=76459.0,
> internalAddressAndPort=127.0.0.6:7012, sstableVersions=big-nb,
> tokens=, dc=datacenter1, netVersion=12,
> statusWithPort=BOOT_REPLACE,127.0.0.5:7012}{code}
--
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-78) Fix token-ranges endpoint to handle gossip-info responses without 'status'
[
https://issues.apache.org/jira/browse/CASSANDRASC-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arjun Ashok updated CASSANDRASC-78:
---
Summary: Fix token-ranges endpoint to handle gossip-info responses without
'status' (was: Fix token-ranges endpoint to o handle gossip-info responses
without 'status')
> Fix token-ranges endpoint to handle gossip-info responses without 'status'
> --
>
> Key: CASSANDRASC-78
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-78
> Project: Sidecar for Apache Cassandra
> Issue Type: Bug
> Components: Rest API
>Reporter: Arjun Ashok
>Assignee: Arjun Ashok
>Priority: Normal
>
> This is a fix to look for the host status in ‘Status’ and ‘StatusWithPort’
> attributes in GossipInfo response to determine the ‘state’ of the node.
> Currently, we only check for ‘status’ which can be missing from gossipInfo in
> some cases, which will result in a replacement node status to be reported as
> `Joining` instead of `Replacing`.
> eg.
> {code:java}
> Found gossipInfoEntry={generation=1697736379,
> schema=6d6abc83-a600-35a4-8bbe-fe5edca6a63b, rack=rack1, heartbeat=119,
> releaseVersion=4.1.4-SNAPSHOT, hostId=--4000-8000-0006,
> nativeAddressAndPort=127.0.0.6:9042, load=76459.0,
> internalAddressAndPort=127.0.0.6:7012, sstableVersions=big-nb,
> tokens=, dc=datacenter1, netVersion=12,
> statusWithPort=BOOT_REPLACE,127.0.0.5:7012}{code}
--
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-78) Fix token-ranges endpoint to o handle gossip-info responses without 'status'
[
https://issues.apache.org/jira/browse/CASSANDRASC-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arjun Ashok updated CASSANDRASC-78:
---
Description:
This is a fix to look for the host status in ‘Status’ and ‘StatusWithPort’
attributes in GossipInfo response to determine the ‘state’ of the node.
Currently, we only check for ‘status’ which can be missing from gossipInfo in
some cases, which will result in a replacement node status to be reported as
`Joining` instead of `Replacing`.
eg.
{code:java}
Found gossipInfoEntry={generation=1697736379,
schema=6d6abc83-a600-35a4-8bbe-fe5edca6a63b, rack=rack1, heartbeat=119,
releaseVersion=4.1.4-SNAPSHOT, hostId=--4000-8000-0006,
nativeAddressAndPort=127.0.0.6:9042, load=76459.0,
internalAddressAndPort=127.0.0.6:7012, sstableVersions=big-nb, tokens=,
dc=datacenter1, netVersion=12, statusWithPort=BOOT_REPLACE,127.0.0.5:7012}{code}
was:
This is a fix to look for the host status in ‘Status’ and ‘StatusWithPort’
attributes in GossipInfo response to determine the ‘state’ of the node.
Currently, we only check for ‘status’ which can be missing from gossipInfo in
some cases, which will result in a replacement node status to be reported as
`Joining` instead of `Replacing`.
eg.
```
Found gossipInfoEntry=\{generation=1697736379,
schema=6d6abc83-a600-35a4-8bbe-fe5edca6a63b, rack=rack1, heartbeat=119,
releaseVersion=4.1.4-SNAPSHOT, hostId=--4000-8000-0006,
nativeAddressAndPort=127.0.0.6:9042, load=76459.0,
internalAddressAndPort=127.0.0.6:7012, sstableVersions=big-nb, tokens=,
dc=datacenter1, netVersion=12, statusWithPort=BOOT_REPLACE,127.0.0.5:7012}
```
> Fix token-ranges endpoint to o handle gossip-info responses without 'status'
>
>
> Key: CASSANDRASC-78
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-78
> Project: Sidecar for Apache Cassandra
> Issue Type: Bug
> Components: Rest API
>Reporter: Arjun Ashok
>Assignee: Arjun Ashok
>Priority: Normal
>
> This is a fix to look for the host status in ‘Status’ and ‘StatusWithPort’
> attributes in GossipInfo response to determine the ‘state’ of the node.
> Currently, we only check for ‘status’ which can be missing from gossipInfo in
> some cases, which will result in a replacement node status to be reported as
> `Joining` instead of `Replacing`.
> eg.
> {code:java}
> Found gossipInfoEntry={generation=1697736379,
> schema=6d6abc83-a600-35a4-8bbe-fe5edca6a63b, rack=rack1, heartbeat=119,
> releaseVersion=4.1.4-SNAPSHOT, hostId=--4000-8000-0006,
> nativeAddressAndPort=127.0.0.6:9042, load=76459.0,
> internalAddressAndPort=127.0.0.6:7012, sstableVersions=big-nb,
> tokens=, dc=datacenter1, netVersion=12,
> statusWithPort=BOOT_REPLACE,127.0.0.5:7012}{code}
--
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-78) Fix token-ranges endpoint to o handle gossip-info responses without 'status'
Arjun Ashok created CASSANDRASC-78:
--
Summary: Fix token-ranges endpoint to o handle gossip-info
responses without 'status'
Key: CASSANDRASC-78
URL: https://issues.apache.org/jira/browse/CASSANDRASC-78
Project: Sidecar for Apache Cassandra
Issue Type: Bug
Components: Rest API
Reporter: Arjun Ashok
Assignee: Arjun Ashok
This is a fix to look for the host status in ‘Status’ and ‘StatusWithPort’
attributes in GossipInfo response to determine the ‘state’ of the node.
Currently, we only check for ‘status’ which can be missing from gossipInfo in
some cases, which will result in a replacement node status to be reported as
`Joining` instead of `Replacing`.
eg.
```
Found gossipInfoEntry=\{generation=1697736379,
schema=6d6abc83-a600-35a4-8bbe-fe5edca6a63b, rack=rack1, heartbeat=119,
releaseVersion=4.1.4-SNAPSHOT, hostId=--4000-8000-0006,
nativeAddressAndPort=127.0.0.6:9042, load=76459.0,
internalAddressAndPort=127.0.0.6:7012, sstableVersions=big-nb, tokens=,
dc=datacenter1, netVersion=12, statusWithPort=BOOT_REPLACE,127.0.0.5:7012}
```
--
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-18852) [Analytics] Make bulk writer resilient to cluster resize events
[ https://issues.apache.org/jira/browse/CASSANDRA-18852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok updated CASSANDRA-18852: Change Category: Semantic Complexity: Normal Status: Open (was: Triage Needed) > [Analytics] Make bulk writer resilient to cluster resize events > --- > > Key: CASSANDRA-18852 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18852 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > > Currently, the analytics bulk writer fails-fast if there are any ongoing > cluster resizing events such as expansion, shrink, host-replacement or node > movements. > This effort is make the bulk writer resilient to these events by having the > writes account for the transient nodes and their corresponding pending token > ranges. > Related: https://issues.apache.org/jira/browse/CASSANDRASC-60 -- 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-73) Update token-ranges endpoint to return additional instance metadata
[ https://issues.apache.org/jira/browse/CASSANDRASC-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok updated CASSANDRASC-73: --- Authors: Arjun Ashok Test and Documentation Plan: Validated changes via unit/integration tests which were updated accordingly. Status: Patch Available (was: Open) > Update token-ranges endpoint to return additional instance metadata > --- > > Key: CASSANDRASC-73 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-73 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Labels: pull-request-available > > Sidecar `token-range-replicas` endpoint to return the following additional > metadata for each instance: > * State. eg Normal, Joining, Leaving > * Status. eg. Up, Down > * Address: Replica host and port > * Name: Node name resolved from the above IP address -- 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-73) Update token-ranges endpoint to return additional instance metadata
[ https://issues.apache.org/jira/browse/CASSANDRASC-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok updated CASSANDRASC-73: --- Change Category: Semantic Complexity: Normal Component/s: Rest API Status: Open (was: Triage Needed) > Update token-ranges endpoint to return additional instance metadata > --- > > Key: CASSANDRASC-73 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-73 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Labels: pull-request-available > > Sidecar `token-range-replicas` endpoint to return the following additional > metadata for each instance: > * State. eg Normal, Joining, Leaving > * Status. eg. Up, Down > * Address: Replica host and port > * Name: Node name resolved from the above IP address -- 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-73) Update token-ranges endpoint to return additional instance metadata
[ https://issues.apache.org/jira/browse/CASSANDRASC-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766609#comment-17766609 ] Arjun Ashok commented on CASSANDRASC-73: PR: [https://github.com/apache/cassandra-sidecar/pull/69] CI: https://app.circleci.com/pipelines/github/arjunashok/cassandra-sidecar?branch=CASSANDRASC-73 > Update token-ranges endpoint to return additional instance metadata > --- > > Key: CASSANDRASC-73 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-73 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > > Sidecar `token-range-replicas` endpoint to return the following additional > metadata for each instance: > * State. eg Normal, Joining, Leaving > * Status. eg. Up, Down > * Address: Replica host and port > * Name: Node name resolved from the above IP address -- 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-73) Update token-ranges endpoint to return additional instance metadata
Arjun Ashok created CASSANDRASC-73: -- Summary: Update token-ranges endpoint to return additional instance metadata Key: CASSANDRASC-73 URL: https://issues.apache.org/jira/browse/CASSANDRASC-73 Project: Sidecar for Apache Cassandra Issue Type: Improvement Reporter: Arjun Ashok Assignee: Arjun Ashok Sidecar `token-range-replicas` endpoint to return the following additional metadata for each instance: * State. eg Normal, Joining, Leaving * Status. eg. Up, Down * Address: Replica host and port * Name: Node name resolved from the above IP address -- 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-18852) [Analytics] Make bulk writer resilient to cluster resize events
[ https://issues.apache.org/jira/browse/CASSANDRA-18852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok updated CASSANDRA-18852: Description: Currently, the analytics bulk writer fails-fast if there are any ongoing cluster resizing events such as expansion, shrink, host-replacement or node movements. This effort is make the bulk writer resilient to these events by having the writes account for the transient nodes and their corresponding pending token ranges. Related: https://issues.apache.org/jira/browse/CASSANDRASC-60 was: Currently, the analytics bulk writer fails-fast if there are any ongoing cluster resizing events such as expansion, shrink, host-replacement or node movements. This effort is make the bulk writer resilient to these events by having the writes account for the transient nodes and their corresponding pending token ranges. > [Analytics] Make bulk writer resilient to cluster resize events > --- > > Key: CASSANDRA-18852 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18852 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > > Currently, the analytics bulk writer fails-fast if there are any ongoing > cluster resizing events such as expansion, shrink, host-replacement or node > movements. > This effort is make the bulk writer resilient to these events by having the > writes account for the transient nodes and their corresponding pending token > ranges. > Related: https://issues.apache.org/jira/browse/CASSANDRASC-60 -- 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-18852) [Analytics] Make bulk writer resilient to cluster resize events
Arjun Ashok created CASSANDRA-18852: --- Summary: [Analytics] Make bulk writer resilient to cluster resize events Key: CASSANDRA-18852 URL: https://issues.apache.org/jira/browse/CASSANDRA-18852 Project: Cassandra Issue Type: Improvement Components: Analytics Library Reporter: Arjun Ashok Assignee: Arjun Ashok Currently, the analytics bulk writer fails-fast if there are any ongoing cluster resizing events such as expansion, shrink, host-replacement or node movements. This effort is make the bulk writer resilient to these events by having the writes account for the transient nodes and their corresponding pending token ranges. -- 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-60) Sidecar API to expose cluster topology information
[ https://issues.apache.org/jira/browse/CASSANDRASC-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok updated CASSANDRASC-60: --- Test and Documentation Plan: Added in-jvm-dtest based integration tests to validate API against Cassandra clusters and simulating different resizing scenarios. Status: Patch Available (was: In Progress) PR: https://github.com/apache/cassandra-sidecar/pull/58 CI: https://app.circleci.com/pipelines/github/arjunashok/cassandra-sidecar?branch=CASSANDRASC-60 > Sidecar API to expose cluster topology information > -- > > Key: CASSANDRASC-60 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-60 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Labels: pull-request-available > > This API will expose token ranges and the corresponding read and write > replicas. The write replica-set token ranges will include natural and pending > ranges, so clients can have a complete view of the cluster as nodes are > joining or leaving. -- 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-60) Sidecar API to expose cluster topology information
[ https://issues.apache.org/jira/browse/CASSANDRASC-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok updated CASSANDRASC-60: --- Change Category: Semantic Complexity: Normal Status: Open (was: Triage Needed) > Sidecar API to expose cluster topology information > -- > > Key: CASSANDRASC-60 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-60 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > > This API will expose token ranges and the corresponding read and write > replicas. The write replica-set token ranges will include natural and pending > ranges, so clients can have a complete view of the cluster as nodes are > joining or leaving. -- 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-60) Sidecar API to expose cluster topology information
Arjun Ashok created CASSANDRASC-60: -- Summary: Sidecar API to expose cluster topology information Key: CASSANDRASC-60 URL: https://issues.apache.org/jira/browse/CASSANDRASC-60 Project: Sidecar for Apache Cassandra Issue Type: Improvement Components: Rest API Reporter: Arjun Ashok Assignee: Arjun Ashok This API will expose token ranges and the corresponding read and write replicas. The write replica-set token ranges will include natural and pending ranges, so clients can have a complete view of the cluster as nodes are joining or leaving. -- 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
