[jira] [Assigned] (CASSANDRA-19625) Integrate Cassandra Analytics with SonarQube
[ https://issues.apache.org/jira/browse/CASSANDRA-19625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn reassigned CASSANDRA-19625: Assignee: Francisco Guerrero (was: Yuriy Semchyshyn) > Integrate Cassandra Analytics with SonarQube > > > Key: CASSANDRA-19625 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19625 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Yuriy Semchyshyn >Assignee: Francisco Guerrero >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > Introduce the initial Gradle configuration for integration of Cassandra > Analytics with SonarCube for code analysis -- 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] (CASSANDRASC-128) Integrate Cassandra Sidecar with SonarQube
[ https://issues.apache.org/jira/browse/CASSANDRASC-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn reassigned CASSANDRASC-128: Assignee: Francisco Guerrero (was: Yuriy Semchyshyn) > Integrate Cassandra Sidecar with SonarQube > -- > > Key: CASSANDRASC-128 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-128 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Yuriy Semchyshyn >Assignee: Francisco Guerrero >Priority: Normal > Labels: pull-request-available > > Introduce the initial Gradle configuration for integration of Cassandra > Sidecar with SonarCube for code analysis -- 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-19625) Integrate Cassandra Analytics with SonarQube
[ https://issues.apache.org/jira/browse/CASSANDRA-19625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn updated CASSANDRA-19625: - Source Control Link: https://github.com/apache/cassandra-analytics/pull/57 > Integrate Cassandra Analytics with SonarQube > > > Key: CASSANDRA-19625 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19625 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Yuriy Semchyshyn >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > Introduce the initial Gradle configuration for integration of Cassandra > Analytics with SonarCube for code analysis -- 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-128) Integrate Cassandra Sidecar with SonarQube
[ https://issues.apache.org/jira/browse/CASSANDRASC-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn updated CASSANDRASC-128: - Source Control Link: https://github.com/apache/cassandra-sidecar/pull/119 > Integrate Cassandra Sidecar with SonarQube > -- > > Key: CASSANDRASC-128 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-128 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Yuriy Semchyshyn >Priority: Normal > Labels: pull-request-available > > Introduce the initial Gradle configuration for integration of Cassandra > Sidecar with SonarCube for code analysis -- 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-19625) Integrate Cassandra Analytics with SonarQube
Yuriy Semchyshyn created CASSANDRA-19625: Summary: Integrate Cassandra Analytics with SonarQube Key: CASSANDRA-19625 URL: https://issues.apache.org/jira/browse/CASSANDRA-19625 Project: Cassandra Issue Type: Improvement Components: Analytics Library Reporter: Yuriy Semchyshyn Introduce the initial Gradle configuration for integration of Cassandra Analytics with SonarCube for code analysis -- 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-128) Integrate Cassandra Sidecar with SonarQube
Yuriy Semchyshyn created CASSANDRASC-128: Summary: Integrate Cassandra Sidecar with SonarQube Key: CASSANDRASC-128 URL: https://issues.apache.org/jira/browse/CASSANDRASC-128 Project: Sidecar for Apache Cassandra Issue Type: Improvement Components: Configuration Reporter: Yuriy Semchyshyn Introduce the initial Gradle configuration for integration of Cassandra Sidecar with SonarCube for code analysis -- 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-19377) Startup Validation Failures when Checking Sidecar Connectivity (Analytics)
[jira] [Updated] (CASSANDRA-19377) Startup Validation Failures when Checking Sidecar Connectivity (Analytics)
[ https://issues.apache.org/jira/browse/CASSANDRA-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn updated CASSANDRA-19377: - Change Category: Operability Complexity: Normal Status: Open (was: Triage Needed) This is a follow-up issue to https://issues.apache.org/jira/browse/CASSANDRASC-86 that has already been committed. The reviewed patch is here: https://github.com/apache/cassandra-analytics/pull/22. The successful build is here: https://app.circleci.com/pipelines/github/5/cassandra-analytics/49/workflows/8ac5b581-e015-4c7f-b1ed-1b5bd9f4976c. > Startup Validation Failures when Checking Sidecar Connectivity (Analytics) > -- > > Key: CASSANDRA-19377 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19377 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Yuriy Semchyshyn >Priority: Normal > > We have experienced repeated startup validation failures caused by Sidecar > health checks for some jobs with a large number of Spark executors. > It is worth increasing the overall timeout for Sidecar health checks from > current 30 seconds to 5 minutes and making it configurable. -- 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-19377) Startup Validation Failures when Checking Sidecar Connectivity (Analytics)
[ https://issues.apache.org/jira/browse/CASSANDRA-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn updated CASSANDRA-19377: - Authors: Yuriy Semchyshyn Test and Documentation Plan: https://app.circleci.com/pipelines/github/5/cassandra-analytics/49/workflows/8ac5b581-e015-4c7f-b1ed-1b5bd9f4976c Status: Patch Available (was: Open) > Startup Validation Failures when Checking Sidecar Connectivity (Analytics) > -- > > Key: CASSANDRA-19377 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19377 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Yuriy Semchyshyn >Priority: Normal > > We have experienced repeated startup validation failures caused by Sidecar > health checks for some jobs with a large number of Spark executors. > It is worth increasing the overall timeout for Sidecar health checks from > current 30 seconds to 5 minutes and making it configurable. -- 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-19377) Startup Validation Failures when Checking Sidecar Connectivity (Analytics)
Yuriy Semchyshyn created CASSANDRA-19377: Summary: Startup Validation Failures when Checking Sidecar Connectivity (Analytics) Key: CASSANDRA-19377 URL: https://issues.apache.org/jira/browse/CASSANDRA-19377 Project: Cassandra Issue Type: Improvement Components: Analytics Library Reporter: Yuriy Semchyshyn We have experienced repeated startup validation failures caused by Sidecar health checks for some jobs with a large number of Spark executors. It is worth increasing the overall timeout for Sidecar health checks from current 30 seconds to 5 minutes and making it configurable. -- 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-102) Startup Validation Failures when Checking Sidecar Connectivity (Analytics)
[ https://issues.apache.org/jira/browse/CASSANDRASC-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn updated CASSANDRASC-102: - Source Control Link: https://github.com/apache/cassandra-analytics/pull/22 > Startup Validation Failures when Checking Sidecar Connectivity (Analytics) > -- > > Key: CASSANDRASC-102 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-102 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Yuriy Semchyshyn >Priority: Normal > > We have experienced repeated startup validation failures caused by Sidecar > health checks for some jobs with a large number of Spark executors. > It is worth increasing the overall timeout for Sidecar health checks from > current 30 seconds to 5 minutes and making it configurable. -- 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-102) Startup Validation Failures when Checking Sidecar Connectivity (Analytics)
[ https://issues.apache.org/jira/browse/CASSANDRASC-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17815412#comment-17815412 ] Yuriy Semchyshyn commented on CASSANDRASC-102: -- This is a follow-up issue to https://issues.apache.org/jira/browse/CASSANDRASC-86 that has already been committed. The reviewed patch is here: https://github.com/apache/cassandra-analytics/pull/22. The successful build is here: https://app.circleci.com/pipelines/github/5/cassandra-analytics/49/workflows/8ac5b581-e015-4c7f-b1ed-1b5bd9f4976c. > Startup Validation Failures when Checking Sidecar Connectivity (Analytics) > -- > > Key: CASSANDRASC-102 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-102 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Yuriy Semchyshyn >Priority: Normal > > We have experienced repeated startup validation failures caused by Sidecar > health checks for some jobs with a large number of Spark executors. > It is worth increasing the overall timeout for Sidecar health checks from > current 30 seconds to 5 minutes and making it configurable. -- 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-102) Startup Validation Failures when Checking Sidecar Connectivity (Analytics)
[ https://issues.apache.org/jira/browse/CASSANDRASC-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn updated CASSANDRASC-102: - Authors: Yuriy Semchyshyn Test and Documentation Plan: https://app.circleci.com/pipelines/github/5/cassandra-analytics/49/workflows/8ac5b581-e015-4c7f-b1ed-1b5bd9f4976c Status: Patch Available (was: Open) > Startup Validation Failures when Checking Sidecar Connectivity (Analytics) > -- > > Key: CASSANDRASC-102 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-102 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Yuriy Semchyshyn >Priority: Normal > > We have experienced repeated startup validation failures caused by Sidecar > health checks for some jobs with a large number of Spark executors. > It is worth increasing the overall timeout for Sidecar health checks from > current 30 seconds to 5 minutes and making it configurable. -- 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-102) Startup Validation Failures when Checking Sidecar Connectivity (Analytics)
[ https://issues.apache.org/jira/browse/CASSANDRASC-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn updated CASSANDRASC-102: - Change Category: Operability Complexity: Normal Status: Open (was: Triage Needed) > Startup Validation Failures when Checking Sidecar Connectivity (Analytics) > -- > > Key: CASSANDRASC-102 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-102 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Yuriy Semchyshyn >Priority: Normal > > We have experienced repeated startup validation failures caused by Sidecar > health checks for some jobs with a large number of Spark executors. > It is worth increasing the overall timeout for Sidecar health checks from > current 30 seconds to 5 minutes and making it configurable. -- 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-102) Startup Validation Failures when Checking Sidecar Connectivity (Analytics)
Yuriy Semchyshyn created CASSANDRASC-102: Summary: Startup Validation Failures when Checking Sidecar Connectivity (Analytics) Key: CASSANDRASC-102 URL: https://issues.apache.org/jira/browse/CASSANDRASC-102 Project: Sidecar for Apache Cassandra Issue Type: Improvement Components: Configuration Reporter: Yuriy Semchyshyn We have experienced repeated startup validation failures caused by Sidecar health checks for some jobs with a large number of Spark executors. It is worth increasing the overall timeout for Sidecar health checks from current 30 seconds to 5 minutes and making it configurable. -- 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-86) Startup Validation Failures when Checking Sidecar Connectivity
[ https://issues.apache.org/jira/browse/CASSANDRASC-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17811450#comment-17811450 ] Yuriy Semchyshyn commented on CASSANDRASC-86: - Links to successful CircleCI runs for both PRs: * https://app.circleci.com/pipelines/github/5/cassandra-sidecar/44/workflows/205bdbf9-67c6-4c05-9f7e-1503d3f6b2b0 * https://app.circleci.com/pipelines/github/5/cassandra-analytics/49/workflows/8ac5b581-e015-4c7f-b1ed-1b5bd9f4976c > Startup Validation Failures when Checking Sidecar Connectivity > -- > > Key: CASSANDRASC-86 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-86 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Yuriy Semchyshyn >Assignee: Yuriy Semchyshyn >Priority: Normal > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > We have experienced repeated startup validation failures caused by Sidecar > health checks for some jobs with a large number of Spark executors. > These failures are likely caused by the thundering herd problem, and have > been so far worked around by disabling startup validations altogether. > In order to prevent them going forward, a random delay needs to be added > between retries of health checks in Sidecar client. > It is also worth increasing the overall timeout for Sidecar health checks > from current 30 seconds to 60 seconds. -- 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-86) Startup Validation Failures when Checking Sidecar Connectivity
[ https://issues.apache.org/jira/browse/CASSANDRASC-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn updated CASSANDRASC-86: Authors: Yuriy Semchyshyn Test and Documentation Plan: N/A Status: Patch Available (was: Open) > Startup Validation Failures when Checking Sidecar Connectivity > -- > > Key: CASSANDRASC-86 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-86 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Yuriy Semchyshyn >Priority: Normal > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > We have experienced repeated startup validation failures caused by Sidecar > health checks for some jobs with a large number of Spark executors. > These failures are likely caused by the thundering herd problem, and have > been so far worked around by disabling startup validations altogether. > In order to prevent them going forward, a random delay needs to be added > between retries of health checks in Sidecar client. > It is also worth increasing the overall timeout for Sidecar health checks > from current 30 seconds to 60 seconds. -- 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-86) Startup Validation Failures when Checking Sidecar Connectivity
[ https://issues.apache.org/jira/browse/CASSANDRASC-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn updated CASSANDRASC-86: Change Category: Semantic Complexity: Normal Component/s: Configuration Status: Open (was: Triage Needed) > Startup Validation Failures when Checking Sidecar Connectivity > -- > > Key: CASSANDRASC-86 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-86 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Yuriy Semchyshyn >Priority: Normal > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > We have experienced repeated startup validation failures caused by Sidecar > health checks for some jobs with a large number of Spark executors. > These failures are likely caused by the thundering herd problem, and have > been so far worked around by disabling startup validations altogether. > In order to prevent them going forward, a random delay needs to be added > between retries of health checks in Sidecar client. > It is also worth increasing the overall timeout for Sidecar health checks > from current 30 seconds to 60 seconds. -- 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-86) Startup Validation Failures when Checking Sidecar Connectivity
[ https://issues.apache.org/jira/browse/CASSANDRASC-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17791382#comment-17791382 ] Yuriy Semchyshyn commented on CASSANDRASC-86: - PRs: * https://github.com/apache/cassandra-sidecar/pull/81 * https://github.com/apache/cassandra-analytics/pull/22 > Startup Validation Failures when Checking Sidecar Connectivity > -- > > Key: CASSANDRASC-86 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-86 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement >Reporter: Yuriy Semchyshyn >Priority: Normal > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > We have experienced repeated startup validation failures caused by Sidecar > health checks for some jobs with a large number of Spark executors. > These failures are likely caused by the thundering herd problem, and have > been so far worked around by disabling startup validations altogether. > In order to prevent them going forward, a random delay needs to be added > between retries of health checks in Sidecar client. > It is also worth increasing the overall timeout for Sidecar health checks > from current 30 seconds to 60 seconds. -- 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-86) Startup Validation Failures when Checking Sidecar Connectivity
Yuriy Semchyshyn created CASSANDRASC-86: --- Summary: Startup Validation Failures when Checking Sidecar Connectivity Key: CASSANDRASC-86 URL: https://issues.apache.org/jira/browse/CASSANDRASC-86 Project: Sidecar for Apache Cassandra Issue Type: Improvement Reporter: Yuriy Semchyshyn We have experienced repeated startup validation failures caused by Sidecar health checks for some jobs with a large number of Spark executors. These failures are likely caused by the thundering herd problem, and have been so far worked around by disabling startup validations altogether. In order to prevent them going forward, a random delay needs to be added between retries of health checks in Sidecar client. It is also worth increasing the overall timeout for Sidecar health checks from current 30 seconds to 60 seconds. -- 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-18916) Start-Up Validation Should Log a Single Report
[ https://issues.apache.org/jira/browse/CASSANDRA-18916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17773822#comment-17773822 ] Yuriy Semchyshyn commented on CASSANDRA-18916: -- GitHub PR: https://github.com/apache/cassandra-analytics/pull/16 CircleCI Run: https://app.circleci.com/pipelines/github/5/cassandra-analytics/41 > Start-Up Validation Should Log a Single Report > -- > > Key: CASSANDRA-18916 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18916 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Yuriy Semchyshyn >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > In order to improve readability of the log, start-up validation should > produce a complete report and emit it as a single event upon completion -- 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-18916) Start-Up Validation Should Log a Single Report
[ https://issues.apache.org/jira/browse/CASSANDRA-18916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn updated CASSANDRA-18916: - Change Category: Operability Complexity: Low Hanging Fruit Status: Open (was: Triage Needed) > Start-Up Validation Should Log a Single Report > -- > > Key: CASSANDRA-18916 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18916 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Yuriy Semchyshyn >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > In order to improve readability of the log, start-up validation should > produce a complete report and emit it as a single event upon completion -- 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-18916) Start-Up Validation Should Log a Single Report
[ https://issues.apache.org/jira/browse/CASSANDRA-18916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn updated CASSANDRA-18916: - Authors: Yuriy Semchyshyn Test and Documentation Plan: https://github.com/apache/cassandra-analytics/pull/16 Status: Patch Available (was: Open) > Start-Up Validation Should Log a Single Report > -- > > Key: CASSANDRA-18916 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18916 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Yuriy Semchyshyn >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > In order to improve readability of the log, start-up validation should > produce a complete report and emit it as a single event upon completion -- 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-18916) Start-Up Validation Should Log a Single Report
Yuriy Semchyshyn created CASSANDRA-18916: Summary: Start-Up Validation Should Log a Single Report Key: CASSANDRA-18916 URL: https://issues.apache.org/jira/browse/CASSANDRA-18916 Project: Cassandra Issue Type: Improvement Components: Analytics Library Reporter: Yuriy Semchyshyn In order to improve readability of the log, start-up validation should produce a complete report and emit it as a single event upon completion -- 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-18810) Cassandra Analytics Start-Up Validation
[ https://issues.apache.org/jira/browse/CASSANDRA-18810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn updated CASSANDRA-18810: - Test and Documentation Plan: https://github.com/apache/cassandra-analytics/pull/15 Status: Patch Available (was: Open) > Cassandra Analytics Start-Up Validation > --- > > Key: CASSANDRA-18810 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18810 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Yuriy Semchyshyn >Assignee: Yuriy Semchyshyn >Priority: Normal > Time Spent: 6.5h > Remaining Estimate: 0h > > Cassandra Analytics should perform a start-up validation of network > connectivity to Cassandra and Cassandra Sidecar, as well as of authentication > materials -- 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-18810) Cassandra Analytics Start-Up Validation
[ https://issues.apache.org/jira/browse/CASSANDRA-18810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17766918#comment-17766918 ] Yuriy Semchyshyn commented on CASSANDRA-18810: -- Builds and tests are green at https://app.circleci.com/pipelines/github/5/cassandra-analytics/31/workflows/2482ddeb-8758-414e-a63d-58dc363301c2 > Cassandra Analytics Start-Up Validation > --- > > Key: CASSANDRA-18810 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18810 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Yuriy Semchyshyn >Assignee: Yuriy Semchyshyn >Priority: Normal > Time Spent: 3h 20m > Remaining Estimate: 0h > > Cassandra Analytics should perform a start-up validation of network > connectivity to Cassandra and Cassandra Sidecar, as well as of authentication > materials -- 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-18810) Cassandra Analytics Start-Up Validation
[ https://issues.apache.org/jira/browse/CASSANDRA-18810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17760621#comment-17760621 ] Yuriy Semchyshyn commented on CASSANDRA-18810: -- Pull request is at https://github.com/apache/cassandra-analytics/pull/15 > Cassandra Analytics Start-Up Validation > --- > > Key: CASSANDRA-18810 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18810 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Yuriy Semchyshyn >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > Cassandra Analytics should perform a start-up validation of network > connectivity to Cassandra and Cassandra Sidecar, as well as of authentication > materials -- 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-18810) Cassandra Analytics Start-Up Validation
Yuriy Semchyshyn created CASSANDRA-18810: Summary: Cassandra Analytics Start-Up Validation Key: CASSANDRA-18810 URL: https://issues.apache.org/jira/browse/CASSANDRA-18810 Project: Cassandra Issue Type: Improvement Components: Analytics Library Reporter: Yuriy Semchyshyn Cassandra Analytics should perform a start-up validation of network connectivity to Cassandra and Cassandra Sidecar, as well as of authentication materials -- 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-70) Add Client Methods for Obtaining Sidecar and Cassandra Health
[ https://issues.apache.org/jira/browse/CASSANDRASC-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17759728#comment-17759728 ] Yuriy Semchyshyn commented on CASSANDRASC-70: - New CI Link: https://app.circleci.com/pipelines/github/5/cassandra-sidecar/32/workflows/2f1678b9-0493-44e6-8568-b87f0954b616 > Add Client Methods for Obtaining Sidecar and Cassandra Health > - > > Key: CASSANDRASC-70 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-70 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Yuriy Semchyshyn >Priority: Normal > Labels: pull-request-available > > Methods for obtaining Sidecar and Cassandra health need to be added to the > client. > Both of these methods will be used for start-up validation by 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] (CASSANDRASC-70) Add Client Methods for Obtaining Sidecar and Cassandra Health
[ https://issues.apache.org/jira/browse/CASSANDRASC-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17758235#comment-17758235 ] Yuriy Semchyshyn commented on CASSANDRASC-70: - CI Link: https://app.circleci.com/pipelines/github/5/cassandra-sidecar/22/workflows/9b48eab2-8f05-4280-96e9-4771307e9cac Java 8 succeeded, but Java 11 failed for reasons that seem to be unrelated to this change. > Add Client Methods for Obtaining Sidecar and Cassandra Health > - > > Key: CASSANDRASC-70 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-70 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Yuriy Semchyshyn >Priority: Normal > Labels: pull-request-available > > Methods for obtaining Sidecar and Cassandra health need to be added to the > client. > Both of these methods will be used for start-up validation by 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] (CASSANDRASC-70) Add Client Methods for Obtaining Sidecar and Cassandra Health
[ https://issues.apache.org/jira/browse/CASSANDRASC-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17757556#comment-17757556 ] Yuriy Semchyshyn commented on CASSANDRASC-70: - Pull Request: https://github.com/apache/cassandra-sidecar/pull/66 > Add Client Methods for Obtaining Sidecar and Cassandra Health > - > > Key: CASSANDRASC-70 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-70 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement >Reporter: Yuriy Semchyshyn >Priority: Normal > Labels: pull-request-available > > Methods for obtaining Sidecar and Cassandra health need to be added to the > client. > Both of these methods will be used for start-up validation by 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] [Created] (CASSANDRASC-70) Add Client Methods for Obtaining Sidecar and Cassandra Health
Yuriy Semchyshyn created CASSANDRASC-70: --- Summary: Add Client Methods for Obtaining Sidecar and Cassandra Health Key: CASSANDRASC-70 URL: https://issues.apache.org/jira/browse/CASSANDRASC-70 Project: Sidecar for Apache Cassandra Issue Type: Improvement Reporter: Yuriy Semchyshyn Methods for obtaining Sidecar and Cassandra health need to be added to the client. Both of these methods will be used for start-up validation by 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-18684) [Analytics] Minor Refactoring to Improve Code Reusability
[ https://issues.apache.org/jira/browse/CASSANDRA-18684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747080#comment-17747080 ] Yuriy Semchyshyn commented on CASSANDRA-18684: -- PR: https://github.com/apache/cassandra-analytics/pull/12 CI: https://app.circleci.com/pipelines/github/5/cassandra-analytics > [Analytics] Minor Refactoring to Improve Code Reusability > - > > Key: CASSANDRA-18684 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18684 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Yuriy Semchyshyn >Priority: Normal > Labels: Refactoring, refactor, refactoring > > A very minor refactoring is needed in the `CassandraClusterInfo` class to > enable reuse of the code block handling retrieval of all `NodeSettings`. -- 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-18684) [Analytics] Minor Refactoring to Improve Code Reusability
[ https://issues.apache.org/jira/browse/CASSANDRA-18684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn updated CASSANDRA-18684: - Test and Documentation Plan: https://app.circleci.com/pipelines/github/5/cassandra-analytics (was: https://github.com/apache/cassandra-analytics/pull/12) > [Analytics] Minor Refactoring to Improve Code Reusability > - > > Key: CASSANDRA-18684 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18684 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Yuriy Semchyshyn >Priority: Normal > Labels: Refactoring, refactor, refactoring > > A very minor refactoring is needed in the `CassandraClusterInfo` class to > enable reuse of the code block handling retrieval of all `NodeSettings`. -- 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-18684) [Analytics] Minor Refactoring to Improve Code Reusability
[ https://issues.apache.org/jira/browse/CASSANDRA-18684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn updated CASSANDRA-18684: - Authors: Yuriy Semchyshyn Test and Documentation Plan: https://github.com/apache/cassandra-analytics/pull/12 Status: Patch Available (was: Open) > [Analytics] Minor Refactoring to Improve Code Reusability > - > > Key: CASSANDRA-18684 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18684 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Yuriy Semchyshyn >Priority: Normal > Labels: Refactoring, refactor, refactoring > > A very minor refactoring is needed in the `CassandraClusterInfo` class to > enable reuse of the code block handling retrieval of all `NodeSettings`. -- 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-18684) [Analytics] Minor Refactoring to Improve Code Reusability
[ https://issues.apache.org/jira/browse/CASSANDRA-18684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn updated CASSANDRA-18684: - Status: Open (was: Triage Needed) > [Analytics] Minor Refactoring to Improve Code Reusability > - > > Key: CASSANDRA-18684 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18684 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Yuriy Semchyshyn >Priority: Normal > Labels: Refactoring, refactor, refactoring > > A very minor refactoring is needed in the `CassandraClusterInfo` class to > enable reuse of the code block handling retrieval of all `NodeSettings`. -- 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-18684) [Analytics] Minor Refactoring to Improve Code Reusability
[ https://issues.apache.org/jira/browse/CASSANDRA-18684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn updated CASSANDRA-18684: - Change Category: Code Clarity Complexity: Low Hanging Fruit Source Control Link: https://github.com/apache/cassandra-analytics/pull/12 Labels: Refactoring refactor refactoring (was: ) > [Analytics] Minor Refactoring to Improve Code Reusability > - > > Key: CASSANDRA-18684 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18684 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Yuriy Semchyshyn >Priority: Normal > Labels: Refactoring, refactor, refactoring > > A very minor refactoring is needed in the `CassandraClusterInfo` class to > enable reuse of the code block handling retrieval of all `NodeSettings`. -- 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-18684) [Analytics] Minor Refactoring to Improve Code Reusability
Yuriy Semchyshyn created CASSANDRA-18684: Summary: [Analytics] Minor Refactoring to Improve Code Reusability Key: CASSANDRA-18684 URL: https://issues.apache.org/jira/browse/CASSANDRA-18684 Project: Cassandra Issue Type: Improvement Components: Analytics Library Reporter: Yuriy Semchyshyn A very minor refactoring is needed in the `CassandraClusterInfo` class to enable reuse of the code block handling retrieval of all `NodeSettings`. -- 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-18633) [Analytics] Add Caching of Node Settings to Improve Efficiency
[ https://issues.apache.org/jira/browse/CASSANDRA-18633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn updated CASSANDRA-18633: - Source Control Link: https://github.com/apache/cassandra-analytics/pull/9 > [Analytics] Add Caching of Node Settings to Improve Efficiency > -- > > Key: CASSANDRA-18633 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18633 > Project: Cassandra > Issue Type: Improvement > Components: Analytics Library >Reporter: Yuriy Semchyshyn >Priority: Normal > > Currently, `CassandraClusterInfo` does not reuse results of a call to > `allNodeSettingsBlocking` from `Sidecar`. > We should improve efficiency by caching these results in order to prevent > multiple expensive cluster-wide calls. -- 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-18633) [Analytics] Add Caching of Node Settings to Improve Efficiency
Yuriy Semchyshyn created CASSANDRA-18633: Summary: [Analytics] Add Caching of Node Settings to Improve Efficiency Key: CASSANDRA-18633 URL: https://issues.apache.org/jira/browse/CASSANDRA-18633 Project: Cassandra Issue Type: Improvement Components: Analytics Library Reporter: Yuriy Semchyshyn Currently, `CassandraClusterInfo` does not reuse results of a call to `allNodeSettingsBlocking` from `Sidecar`. We should improve efficiency by caching these results in order to prevent multiple expensive cluster-wide calls. -- 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-52) Sidecar Should Return Own Version in Node Settings
[ https://issues.apache.org/jira/browse/CASSANDRASC-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17729516#comment-17729516 ] Yuriy Semchyshyn commented on CASSANDRASC-52: - Thank you for taking a look, Dinesh. Just pushed another commit addressing your comment. > Sidecar Should Return Own Version in Node Settings > -- > > Key: CASSANDRASC-52 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-52 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Yuriy Semchyshyn >Assignee: Yuriy Semchyshyn >Priority: Normal > Labels: pull-request-available > > As of now, Sidecar's node settings endpoint returns Cassandra version and > partitioner only. > Sidecar should add its own build version into the node settings object for > reporting purposes. -- 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-52) Sidecar Should Return Own Version in Node Settings
[ https://issues.apache.org/jira/browse/CASSANDRASC-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn updated CASSANDRASC-52: Source Control Link: https://github.com/apache/cassandra-sidecar/pull/47 > Sidecar Should Return Own Version in Node Settings > -- > > Key: CASSANDRASC-52 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-52 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement >Reporter: Yuriy Semchyshyn >Assignee: Dinesh Joshi >Priority: Normal > > As of now, Sidecar's node settings endpoint returns Cassandra version and > partitioner only. > Sidecar should add its own build version into the node settings object for > reporting purposes. -- 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-52) Sidecar Should Return Own Version in Node Settings
Yuriy Semchyshyn created CASSANDRASC-52: --- Summary: Sidecar Should Return Own Version in Node Settings Key: CASSANDRASC-52 URL: https://issues.apache.org/jira/browse/CASSANDRASC-52 Project: Sidecar for Apache Cassandra Issue Type: Improvement Reporter: Yuriy Semchyshyn Assignee: Dinesh Joshi As of now, Sidecar's node settings endpoint returns Cassandra version and partitioner only. Sidecar should add its own build version into the node settings object for reporting purposes. -- 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-18373) Node Draining Should Abort All Current SSTables Imports
[ https://issues.apache.org/jira/browse/CASSANDRA-18373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17708911#comment-17708911 ] Yuriy Semchyshyn commented on CASSANDRA-18373: -- Thanks for the review, Dinesh! Addressed your comments in a separate commit. > Node Draining Should Abort All Current SSTables Imports > --- > > Key: CASSANDRA-18373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18373 > Project: Cassandra > Issue Type: Improvement > Components: Local/Startup and Shutdown >Reporter: Yuriy Semchyshyn >Assignee: Yuriy Semchyshyn >Priority: Normal > Time Spent: 1h 20m > Remaining Estimate: 0h > > SS tables imports that will end up being ignored due to the node draining > should fail instead of succeeding. > Each active SS tables import should periodically check for the node status > and see whether or not it is `DRAINING`. > In case the node starts draining the import should abort immediately by > throwing an `InterruptedException`. -- 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-18373) Node Draining Should Abort All Current SSTables Imports
[ https://issues.apache.org/jira/browse/CASSANDRA-18373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn updated CASSANDRA-18373: - Status: Needs Committer (was: Patch Available) > Node Draining Should Abort All Current SSTables Imports > --- > > Key: CASSANDRA-18373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18373 > Project: Cassandra > Issue Type: Improvement > Components: Local/Startup and Shutdown >Reporter: Yuriy Semchyshyn >Assignee: Yuriy Semchyshyn >Priority: Normal > Time Spent: 50m > Remaining Estimate: 0h > > SS tables imports that will end up being ignored due to the node draining > should fail instead of succeeding. > Each active SS tables import should periodically check for the node status > and see whether or not it is `DRAINING`. > In case the node starts draining the import should abort immediately by > throwing an `InterruptedException`. -- 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-18373) Node Draining Should Abort All Current SSTables Imports
[ https://issues.apache.org/jira/browse/CASSANDRA-18373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17708160#comment-17708160 ] Yuriy Semchyshyn commented on CASSANDRA-18373: -- Thanks for the discussion, Yifan! I addressed your comments in a separate commit. Also, updated Jira and PR descriptions accordingly. Please take another look. > Node Draining Should Abort All Current SSTables Imports > --- > > Key: CASSANDRA-18373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18373 > Project: Cassandra > Issue Type: Improvement > Components: Local/Startup and Shutdown >Reporter: Yuriy Semchyshyn >Assignee: Yuriy Semchyshyn >Priority: Normal > Time Spent: 50m > Remaining Estimate: 0h > > SS tables imports that will end up being ignored due to the node draining > should fail instead of succeeding. > Each active SS tables import should periodically check for the node status > and see whether or not it is `DRAINING`. > In case the node starts draining the import should abort immediately by > throwing an `InterruptedException`. -- 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-18373) Node Draining Should Abort All Current SSTables Imports
[ https://issues.apache.org/jira/browse/CASSANDRA-18373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn updated CASSANDRA-18373: - Description: SS tables imports that will end up being ignored due to the node draining should fail instead of succeeding. Each active SS tables import should periodically check for the node status and see whether or not it is `DRAINING`. In case the node starts draining the import should abort immediately by throwing an `InterruptedException`. was: SS tables imports that have no chance of succeeding due to the node being drained should fail fast. In case there are any SS tables imports currently active, a draining node should notify all of them upon flushing its column family stores. Each notified SS tables import should abort as soon as possible by throwing an `InterruptedException`. > Node Draining Should Abort All Current SSTables Imports > --- > > Key: CASSANDRA-18373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18373 > Project: Cassandra > Issue Type: Improvement > Components: Local/Startup and Shutdown >Reporter: Yuriy Semchyshyn >Assignee: Yuriy Semchyshyn >Priority: Normal > Time Spent: 50m > Remaining Estimate: 0h > > SS tables imports that will end up being ignored due to the node draining > should fail instead of succeeding. > Each active SS tables import should periodically check for the node status > and see whether or not it is `DRAINING`. > In case the node starts draining the import should abort immediately by > throwing an `InterruptedException`. -- 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-18373) Node Draining Should Abort All Current SSTables Imports
[ https://issues.apache.org/jira/browse/CASSANDRA-18373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn updated CASSANDRA-18373: - Test and Documentation Plan: https://github.com/apache/cassandra/pull/2251 Status: Patch Available (was: Open) > Node Draining Should Abort All Current SSTables Imports > --- > > Key: CASSANDRA-18373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18373 > Project: Cassandra > Issue Type: Improvement > Components: Local/Startup and Shutdown >Reporter: Yuriy Semchyshyn >Assignee: Yuriy Semchyshyn >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > SS tables imports that have no chance of succeeding due to the node being > drained should fail fast. > In case there are any SS tables imports currently active, a draining node > should notify all of them upon flushing its column family stores. > Each notified SS tables import should abort as soon as possible by throwing > an `InterruptedException`. -- 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-18373) Node Draining Should Abort All Current SSTables Imports
[ https://issues.apache.org/jira/browse/CASSANDRA-18373 ] Yuriy Semchyshyn deleted comment on CASSANDRA-18373: -- was (Author: JIRAUSER299574): Pull request for review: https://github.com/apache/cassandra/pull/2251 > Node Draining Should Abort All Current SSTables Imports > --- > > Key: CASSANDRA-18373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18373 > Project: Cassandra > Issue Type: Improvement > Components: Local/Startup and Shutdown >Reporter: Yuriy Semchyshyn >Assignee: Yuriy Semchyshyn >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > SS tables imports that have no chance of succeeding due to the node being > drained should fail fast. > In case there are any SS tables imports currently active, a draining node > should notify all of them upon flushing its column family stores. > Each notified SS tables import should abort as soon as possible by throwing > an `InterruptedException`. -- 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-18373) Node Draining Should Abort All Current SSTables Imports
[ https://issues.apache.org/jira/browse/CASSANDRA-18373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Semchyshyn updated CASSANDRA-18373: - Change Category: Semantic Complexity: Low Hanging Fruit Status: Open (was: Triage Needed) > Node Draining Should Abort All Current SSTables Imports > --- > > Key: CASSANDRA-18373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18373 > Project: Cassandra > Issue Type: Improvement > Components: Local/Startup and Shutdown >Reporter: Yuriy Semchyshyn >Assignee: Yuriy Semchyshyn >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > SS tables imports that have no chance of succeeding due to the node being > drained should fail fast. > In case there are any SS tables imports currently active, a draining node > should notify all of them upon flushing its column family stores. > Each notified SS tables import should abort as soon as possible by throwing > an `InterruptedException`. -- 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-18373) Node Draining Should Abort All Current SSTables Imports
[ https://issues.apache.org/jira/browse/CASSANDRA-18373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17706152#comment-17706152 ] Yuriy Semchyshyn commented on CASSANDRA-18373: -- Pull request for review: https://github.com/apache/cassandra/pull/2251 > Node Draining Should Abort All Current SSTables Imports > --- > > Key: CASSANDRA-18373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18373 > Project: Cassandra > Issue Type: Improvement > Components: Local/Startup and Shutdown >Reporter: Yuriy Semchyshyn >Assignee: Yuriy Semchyshyn >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > SS tables imports that have no chance of succeeding due to the node being > drained should fail fast. > In case there are any SS tables imports currently active, a draining node > should notify all of them upon flushing its column family stores. > Each notified SS tables import should abort as soon as possible by throwing > an `InterruptedException`. -- 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-18373) Node Draining Should Abort All Current SSTables Imports
Yuriy Semchyshyn created CASSANDRA-18373: Summary: Node Draining Should Abort All Current SSTables Imports Key: CASSANDRA-18373 URL: https://issues.apache.org/jira/browse/CASSANDRA-18373 Project: Cassandra Issue Type: Improvement Components: Local/Startup and Shutdown Reporter: Yuriy Semchyshyn Assignee: Yuriy Semchyshyn SS tables imports that have no chance of succeeding due to the node being drained should fail fast. In case there are any SS tables imports currently active, a draining node should notify all of them upon flushing its column family stores. Each notified SS tables import should abort as soon as possible by throwing an `InterruptedException`. -- 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
