[jira] [Commented] (CASSANDRA-17606) Fix dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD.test_rolling_upgrade_with_interno
[
https://issues.apache.org/jira/browse/CASSANDRA-17606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536435#comment-17536435
]
Berenguer Blasi commented on CASSANDRA-17606:
-
Waiting for schema agreement is the right thing regardless as Brandon says +1.
In fact someday we should add a mandatory flag when issuing a command given how
many flaky tests we've hit on these grounds. LGTM +1, let's merge it imo as
being part of the upgrade matrix this should be a noisy test and we'll kill a
few flakies with one stone :-)
> Fix
> dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD.test_rolling_upgrade_with_internode_ssl
> -
>
> Key: CASSANDRA-17606
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17606
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.x, 4.1-beta
>
>
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1126/testReport/dtest-upgrade.upgrade_tests.upgrade_through_versions_test/TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD/test_rolling_upgrade_with_internode_ssl/]
> Failed twice on trunk.
> h3.
> {code:java}
> Error Message
> test teardown failure
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [WARN [MessagingService-Incoming-/127.0.0.2] 2022-05-03 21:37:48,446
> IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from
> socket; closing org.apache.cassandra.db.UnknownColumnFamilyException: Got
> slice command for nonexistent table system_auth.roles. If the table was just
> created, this is likely due to the schema not being fully propagated. Please
> wait for schema agreement on table creation. at
> org.apache.cassandra.db.SliceFromReadCommandSerializer.deserialize(SliceFromReadCommand.java:184)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:158)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:132)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.MessageIn.read(MessageIn.java:99)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:200)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:177)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91)
> ~[apache-cassandra-2.2.19.jar:2.2.19], WARN
> [MessagingService-Incoming-/127.0.0.2] 2022-05-03 21:37:48,446
> IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from
> socket; closing org.apache.cassandra.db.UnknownColumnFamilyException: Got
> slice command for nonexistent table system_auth.roles. If the table was just
> created, this is likely due to the schema not being fully propagated. Please
> wait for schema agreement on table creation. at
> org.apache.cassandra.db.SliceFromReadCommandSerializer.deserialize(SliceFromReadCommand.java:184)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:158)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:132)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.MessageIn.read(MessageIn.java:99)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:200)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:177)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91)
> ~[apache-cassandra-2.2.19.jar:2.2.19]]
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17606) Fix dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD.test_rolling_upgrade_with_internode
[
https://issues.apache.org/jira/browse/CASSANDRA-17606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Berenguer Blasi updated CASSANDRA-17606:
Reviewers: Berenguer Blasi, Ekaterina Dimitrova (was: Ekaterina Dimitrova)
> Fix
> dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD.test_rolling_upgrade_with_internode_ssl
> -
>
> Key: CASSANDRA-17606
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17606
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.x, 4.1-beta
>
>
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1126/testReport/dtest-upgrade.upgrade_tests.upgrade_through_versions_test/TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD/test_rolling_upgrade_with_internode_ssl/]
> Failed twice on trunk.
> h3.
> {code:java}
> Error Message
> test teardown failure
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [WARN [MessagingService-Incoming-/127.0.0.2] 2022-05-03 21:37:48,446
> IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from
> socket; closing org.apache.cassandra.db.UnknownColumnFamilyException: Got
> slice command for nonexistent table system_auth.roles. If the table was just
> created, this is likely due to the schema not being fully propagated. Please
> wait for schema agreement on table creation. at
> org.apache.cassandra.db.SliceFromReadCommandSerializer.deserialize(SliceFromReadCommand.java:184)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:158)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:132)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.MessageIn.read(MessageIn.java:99)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:200)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:177)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91)
> ~[apache-cassandra-2.2.19.jar:2.2.19], WARN
> [MessagingService-Incoming-/127.0.0.2] 2022-05-03 21:37:48,446
> IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from
> socket; closing org.apache.cassandra.db.UnknownColumnFamilyException: Got
> slice command for nonexistent table system_auth.roles. If the table was just
> created, this is likely due to the schema not being fully propagated. Please
> wait for schema agreement on table creation. at
> org.apache.cassandra.db.SliceFromReadCommandSerializer.deserialize(SliceFromReadCommand.java:184)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:158)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:132)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.MessageIn.read(MessageIn.java:99)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:200)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:177)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91)
> ~[apache-cassandra-2.2.19.jar:2.2.19]]
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17615) Flaky org.apache.cassandra.cql3.KeywordTest
[
https://issues.apache.org/jira/browse/CASSANDRA-17615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536433#comment-17536433
]
Berenguer Blasi commented on CASSANDRA-17615:
-
To me it reads like an ant timeout, so a test timeout.
> Flaky org.apache.cassandra.cql3.KeywordTest
> ---
>
> Key: CASSANDRA-17615
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17615
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x, 4.1-beta
>
>
> The tests in this class fail very often with:
> h3.
> {code:java}
> Error Message
> Timeout occurred. Please note the time in the report does not reflect the
> time until the timeout.
> Stacktrace
> junit.framework.AssertionFailedError: Timeout occurred. Please note the time
> in the report does not reflect the time until the timeout. at
> java.util.Vector.forEach(Vector.java:1277) at
> java.util.Vector.forEach(Vector.java:1277) at
> java.util.Vector.forEach(Vector.java:1277) at
> org.apache.cassandra.anttasks.TestHelper.execute(TestHelper.java:53) at
> java.util.Vector.forEach(Vector.java:1277)
> {code}
>
> I don't think I've seen them failing in CircleCI, but I see different tests
> from the class in Jenkins timing out.
> Example:
> [https://jenkins-cm4.apache.org/job/Cassandra-4.1/5/testReport/junit/org.apache.cassandra.cql3/KeywordTest/test_keyword_MODIFY_isReserved_true_/]
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-10709) Synchronize TOC and digest
[ https://issues.apache.org/jira/browse/CASSANDRA-10709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536430#comment-17536430 ] Berenguer Blasi commented on CASSANDRA-10709: - Yep that was it. LGTM +1 > Synchronize TOC and digest > -- > > Key: CASSANDRA-10709 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10709 > Project: Cassandra > Issue Type: Bug >Reporter: Stefania Alborghetti >Assignee: Maciej Sokol >Priority: Low > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1-beta > > > The TOC and DIGEST components are not synchronized at the moment (the file is > not fsynch-ed to disk after it is written). This could cause inconsistencies > in case of power failures. At the moment these component sstable files are > only used by standalone tools but we should fix them nonetheless. > Refer to the discussion on CASSANDRA-10534 for more details. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17624) WEBSITE - Fix vanity image on 4.1 Guardrails blog post
[
https://issues.apache.org/jira/browse/CASSANDRA-17624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536399#comment-17536399
]
Erick Ramirez commented on CASSANDRA-17624:
---
I've completed final verification in staging and [published to
production|https://github.com/apache/cassandra-website#merging-asf-staging-to-asf-site]:
{noformat}
$ git branch
* trunk
$ git fetch origin
$ git checkout asf-site
Branch 'asf-site' set up to track remote branch 'asf-site' from 'origin'.
Switched to a new branch 'asf-site'
$ git branch
* asf-site
trunk
$ git reset --hard origin/asf-staging
HEAD is now at 354c902d generate docs for 8ba417dc
$ git push -f origin asf-site
Username for 'https://github.com': erickramirezau
Password for 'https://erickramire...@github.com':
Total 0 (delta 0), reused 0 (delta 0)
To https://github.com/apache/cassandra-website.git
+ f00461fb...354c902d asf-site -> asf-site (forced update){noformat}
The change is now live in production –
[https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html].
> WEBSITE - Fix vanity image on 4.1 Guardrails blog post
> --
>
> Key: CASSANDRA-17624
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17624
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Erick Ramirez
>Assignee: Erick Ramirez
>Priority: Normal
> Fix For: 4.1-rc
>
> Attachments:
> apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg,
> c17624-01-image_replaced.png, c17624-02-blog-post.png
>
>
> The image attached to the [Apache Cassandra 4.1 Features: Guardrails
> Framework|https://cassandra.staged.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html]
> blog post (CASSANDRA-17621) is too large for the page.
> It needs to be replaced with the attached image supplied by [~Calico]:
> !apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg|width=300!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-site updated (f00461fb -> 354c902d)
This is an automated email from the ASF dual-hosted git repository. erickramirezau pushed a change to branch asf-site in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard f00461fb generate docs for a5fdecab add 8ba417dc WEBSITE - Fixed vanity image on 4.1 Guardrails blog post add 354c902d generate docs for 8ba417dc This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (f00461fb) \ N -- N -- N refs/heads/asf-site (354c902d) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. No new revisions were added by this update. Summary of changes: ...tures-guardrails-framework-unsplash-jj-ying.jpg | Bin 136965 -> 186333 bytes content/search-index.js| 2 +- ...tures-guardrails-framework-unsplash-jj-ying.jpg | Bin 136965 -> 186333 bytes site-ui/build/ui-bundle.zip| Bin 4740078 -> 4740078 bytes 4 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17624) WEBSITE - Fix vanity image on 4.1 Guardrails blog post
[ https://issues.apache.org/jira/browse/CASSANDRA-17624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536398#comment-17536398 ] Erick Ramirez commented on CASSANDRA-17624: --- The updated post is now in staging – https://cassandra.staged.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html > WEBSITE - Fix vanity image on 4.1 Guardrails blog post > -- > > Key: CASSANDRA-17624 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17624 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Fix For: 4.1-rc > > Attachments: > apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg, > c17624-01-image_replaced.png, c17624-02-blog-post.png > > > The image attached to the [Apache Cassandra 4.1 Features: Guardrails > Framework|https://cassandra.staged.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html] > blog post (CASSANDRA-17621) is too large for the page. > It needs to be replaced with the attached image supplied by [~Calico]: > !apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg|width=300! -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (f00461fb -> 354c902d)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git omit f00461fb generate docs for a5fdecab add 8ba417dc WEBSITE - Fixed vanity image on 4.1 Guardrails blog post new 354c902d generate docs for 8ba417dc This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (f00461fb) \ N -- N -- N refs/heads/asf-staging (354c902d) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: ...tures-guardrails-framework-unsplash-jj-ying.jpg | Bin 136965 -> 186333 bytes content/search-index.js| 2 +- ...tures-guardrails-framework-unsplash-jj-ying.jpg | Bin 136965 -> 186333 bytes site-ui/build/ui-bundle.zip| Bin 4740078 -> 4740078 bytes 4 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17624) WEBSITE - Fix vanity image on 4.1 Guardrails blog post
[
https://issues.apache.org/jira/browse/CASSANDRA-17624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536396#comment-17536396
]
Erick Ramirez commented on CASSANDRA-17624:
---
||Branch||PR||Commit||Build||
|{{trunk}}|[#129|https://github.com/apache/cassandra-website/pull/129]|[8ba417d
|https://github.com/apache/cassandra-website/commit/8ba417dc013fd880621945b4b0bf3912b9cfad10]|[#240|https://ci-cassandra.apache.org/job/cassandra-website/240/]|
> WEBSITE - Fix vanity image on 4.1 Guardrails blog post
> --
>
> Key: CASSANDRA-17624
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17624
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Erick Ramirez
>Assignee: Erick Ramirez
>Priority: Normal
> Fix For: 4.1-rc
>
> Attachments:
> apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg,
> c17624-01-image_replaced.png, c17624-02-blog-post.png
>
>
> The image attached to the [Apache Cassandra 4.1 Features: Guardrails
> Framework|https://cassandra.staged.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html]
> blog post (CASSANDRA-17621) is too large for the page.
> It needs to be replaced with the attached image supplied by [~Calico]:
> !apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg|width=300!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17624) WEBSITE - Fix vanity image on 4.1 Guardrails blog post
[
https://issues.apache.org/jira/browse/CASSANDRA-17624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-17624:
--
Source Control Link:
https://github.com/apache/cassandra-website/commit/8ba417dc013fd880621945b4b0bf3912b9cfad10
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed:
||Branch||PR||Commit||
|{{trunk}}|[#129|https://github.com/apache/cassandra-website/pull/129]|[8ba417d
|https://github.com/apache/cassandra-website/commit/8ba417dc013fd880621945b4b0bf3912b9cfad10]|
> WEBSITE - Fix vanity image on 4.1 Guardrails blog post
> --
>
> Key: CASSANDRA-17624
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17624
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Erick Ramirez
>Assignee: Erick Ramirez
>Priority: Normal
> Fix For: 4.1-rc
>
> Attachments:
> apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg,
> c17624-01-image_replaced.png, c17624-02-blog-post.png
>
>
> The image attached to the [Apache Cassandra 4.1 Features: Guardrails
> Framework|https://cassandra.staged.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html]
> blog post (CASSANDRA-17621) is too large for the page.
> It needs to be replaced with the attached image supplied by [~Calico]:
> !apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg|width=300!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17624) WEBSITE - Fix vanity image on 4.1 Guardrails blog post
[ https://issues.apache.org/jira/browse/CASSANDRA-17624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17624: -- Status: Ready to Commit (was: Review In Progress) Image replaced: !c17624-01-image_replaced.png|width=400! !c17624-02-blog-post.png|width=400! > WEBSITE - Fix vanity image on 4.1 Guardrails blog post > -- > > Key: CASSANDRA-17624 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17624 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Fix For: 4.1-rc > > Attachments: > apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg, > c17624-01-image_replaced.png, c17624-02-blog-post.png > > > The image attached to the [Apache Cassandra 4.1 Features: Guardrails > Framework|https://cassandra.staged.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html] > blog post (CASSANDRA-17621) is too large for the page. > It needs to be replaced with the attached image supplied by [~Calico]: > !apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg|width=300! -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch trunk updated: WEBSITE - Fixed vanity image on 4.1 Guardrails blog post
This is an automated email from the ASF dual-hosted git repository. erickramirezau pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra-website.git The following commit(s) were added to refs/heads/trunk by this push: new 8ba417dc WEBSITE - Fixed vanity image on 4.1 Guardrails blog post 8ba417dc is described below commit 8ba417dc013fd880621945b4b0bf3912b9cfad10 Author: Erick Ramirez AuthorDate: Fri May 13 01:01:24 2022 + WEBSITE - Fixed vanity image on 4.1 Guardrails blog post patch by Erick Ramirez; reviewed by Chris Thornett, Erick Ramirez for CASSANDRA-17624 --- ...tures-guardrails-framework-unsplash-jj-ying.jpg | Bin 136965 -> 186333 bytes 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/site-content/source/modules/ROOT/images/blog/apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg b/site-content/source/modules/ROOT/images/blog/apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg index dc9c187f..01016c62 100644 Binary files a/site-content/source/modules/ROOT/images/blog/apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg and b/site-content/source/modules/ROOT/images/blog/apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg differ - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17624) WEBSITE - Fix vanity image on 4.1 Guardrails blog post
[ https://issues.apache.org/jira/browse/CASSANDRA-17624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17624: -- Attachment: c17624-02-blog-post.png > WEBSITE - Fix vanity image on 4.1 Guardrails blog post > -- > > Key: CASSANDRA-17624 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17624 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Fix For: 4.1-rc > > Attachments: > apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg, > c17624-01-image_replaced.png, c17624-02-blog-post.png > > > The image attached to the [Apache Cassandra 4.1 Features: Guardrails > Framework|https://cassandra.staged.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html] > blog post (CASSANDRA-17621) is too large for the page. > It needs to be replaced with the attached image supplied by [~Calico]: > !apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg|width=300! -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17624) WEBSITE - Fix vanity image on 4.1 Guardrails blog post
[ https://issues.apache.org/jira/browse/CASSANDRA-17624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17624: -- Attachment: c17624-01-image_replaced.png > WEBSITE - Fix vanity image on 4.1 Guardrails blog post > -- > > Key: CASSANDRA-17624 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17624 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Fix For: 4.1-rc > > Attachments: > apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg, > c17624-01-image_replaced.png > > > The image attached to the [Apache Cassandra 4.1 Features: Guardrails > Framework|https://cassandra.staged.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html] > blog post (CASSANDRA-17621) is too large for the page. > It needs to be replaced with the attached image supplied by [~Calico]: > !apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg|width=300! -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17624) WEBSITE - Fix vanity image on 4.1 Guardrails blog post
[ https://issues.apache.org/jira/browse/CASSANDRA-17624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17624: -- Status: Review In Progress (was: Patch Available) > WEBSITE - Fix vanity image on 4.1 Guardrails blog post > -- > > Key: CASSANDRA-17624 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17624 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Fix For: 4.1-rc > > Attachments: > apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg > > > The image attached to the [Apache Cassandra 4.1 Features: Guardrails > Framework|https://cassandra.staged.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html] > blog post (CASSANDRA-17621) is too large for the page. > It needs to be replaced with the attached image supplied by [~Calico]: > !apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg|width=300! -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17621) WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework"
[
https://issues.apache.org/jira/browse/CASSANDRA-17621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536079#comment-17536079
]
Erick Ramirez edited comment on CASSANDRA-17621 at 5/13/22 1:08 AM:
||Branch||PR||Commit||Build||
|{{trunk}}|[#128|https://github.com/apache/cassandra-website/pull/128]|[a5fdeca
|https://github.com/apache/cassandra-website/commit/a5fdecabfb800cb6638086739171bbe0faebd20e]|[#239|https://ci-cassandra.apache.org/job/cassandra-website/239/]|
was (Author: JIRAUSER285101):
||Branch||PR||Commit||Build||
|{{trunk}}|[#128|https://github.com/apache/cassandra-website/pull/127]|[a5fdeca
|https://github.com/apache/cassandra-website/commit/a5fdecabfb800cb6638086739171bbe0faebd20e]|[#239|https://ci-cassandra.apache.org/job/cassandra-website/239/]|
> WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework"
> -
>
> Key: CASSANDRA-17621
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17621
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Andres de la Peña
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.1-rc
>
> Attachments: c17621-01-blog-index.png, c17621-02-blog-post.png
>
>
> This ticket is to capture the work associated with publishing the May 2022
> blog "Apache Cassandra 4.1 Features: Guardrails Framework"
> If this blog cannot be published by the *May 12, 2022 publish date*, please
> contact me, suggest changes, or correct the date when possible in the pull
> request for the appropriate time that the blog will go live (on both the
> blog.adoc and the blog post's file).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17624) WEBSITE - Fix vanity image on 4.1 Guardrails blog post
[ https://issues.apache.org/jira/browse/CASSANDRA-17624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17624: -- Reviewers: Chris Thornett, Erick Ramirez (was: Erick Ramirez) > WEBSITE - Fix vanity image on 4.1 Guardrails blog post > -- > > Key: CASSANDRA-17624 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17624 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Fix For: 4.1-rc > > Attachments: > apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg > > > The image attached to the [Apache Cassandra 4.1 Features: Guardrails > Framework|https://cassandra.staged.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html] > blog post (CASSANDRA-17621) is too large for the page. > It needs to be replaced with the attached image supplied by [~Calico]: > !apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg|width=300! -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17624) WEBSITE - Fix vanity image on 4.1 Guardrails blog post
[
https://issues.apache.org/jira/browse/CASSANDRA-17624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-17624:
--
Test and Documentation Plan: Replace image with a smaller, cropped version.
Status: Patch Available (was: In Progress)
Patch:
||Branch||PR||
|{{trunk}}|[#129|https://github.com/apache/cassandra-website/pull/129]|
> WEBSITE - Fix vanity image on 4.1 Guardrails blog post
> --
>
> Key: CASSANDRA-17624
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17624
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Erick Ramirez
>Assignee: Erick Ramirez
>Priority: Normal
> Fix For: 4.1-rc
>
> Attachments:
> apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg
>
>
> The image attached to the [Apache Cassandra 4.1 Features: Guardrails
> Framework|https://cassandra.staged.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html]
> blog post (CASSANDRA-17621) is too large for the page.
> It needs to be replaced with the attached image supplied by [~Calico]:
> !apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg|width=300!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17621) WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework"
[
https://issues.apache.org/jira/browse/CASSANDRA-17621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536077#comment-17536077
]
Erick Ramirez edited comment on CASSANDRA-17621 at 5/13/22 1:07 AM:
Committed:
||Branch||PR||Commit||
|{{trunk}}|[#128|https://github.com/apache/cassandra-website/pull/128]|[a5fdeca
|https://github.com/apache/cassandra-website/commit/a5fdecabfb800cb6638086739171bbe0faebd20e]|
was (Author: JIRAUSER285101):
Committed:
||Branch||PR||Commit||
|{{trunk}}|[#128|https://github.com/apache/cassandra-website/pull/127]|[a5fdeca
|https://github.com/apache/cassandra-website/commit/a5fdecabfb800cb6638086739171bbe0faebd20e]|
> WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework"
> -
>
> Key: CASSANDRA-17621
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17621
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Andres de la Peña
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.1-rc
>
> Attachments: c17621-01-blog-index.png, c17621-02-blog-post.png
>
>
> This ticket is to capture the work associated with publishing the May 2022
> blog "Apache Cassandra 4.1 Features: Guardrails Framework"
> If this blog cannot be published by the *May 12, 2022 publish date*, please
> contact me, suggest changes, or correct the date when possible in the pull
> request for the appropriate time that the blog will go live (on both the
> blog.adoc and the blog post's file).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17624) WEBSITE - Fix vanity image on 4.1 Guardrails blog post
[ https://issues.apache.org/jira/browse/CASSANDRA-17624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17624: -- Description: The image attached to the [Apache Cassandra 4.1 Features: Guardrails Framework|https://cassandra.staged.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html] blog post (CASSANDRA-17621) is too large for the page. It needs to be replaced with the attached image supplied by [~Calico]: !apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg|width=300! was: The image attached to the [Apache Cassandra 4.1 Features: Guardrails Framework|https://cassandra.staged.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html] blog post is too large for the page. It needs to be replaced with the attached image supplied by [~Calico]: !apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg|width=300! > WEBSITE - Fix vanity image on 4.1 Guardrails blog post > -- > > Key: CASSANDRA-17624 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17624 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Fix For: 4.1-rc > > Attachments: > apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg > > > The image attached to the [Apache Cassandra 4.1 Features: Guardrails > Framework|https://cassandra.staged.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html] > blog post (CASSANDRA-17621) is too large for the page. > It needs to be replaced with the attached image supplied by [~Calico]: > !apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg|width=300! -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17513) Adding support for TLS client authentication for internode communication
[ https://issues.apache.org/jira/browse/CASSANDRA-17513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yifan Cai updated CASSANDRA-17513: -- Change Category: Operability > Adding support for TLS client authentication for internode communication > > > Key: CASSANDRA-17513 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17513 > Project: Cassandra > Issue Type: Improvement > Components: Feature/Encryption, Local/Config >Reporter: Jyothsna Konisa >Assignee: Jyothsna Konisa >Priority: Normal > Time Spent: 4.5h > Remaining Estimate: 0h > > Same keystore is being set for both Inbound and outbound connections but we > should use a keystore with server certificate for Inbound connections and a > keystore with client certificates for outbound connections. So we should add > a new property in Cassandra.yaml to pass outbound keystore and use it in > SSLContextFactory for creating outbound SSL context. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17513) Adding support for TLS client authentication for internode communication
[ https://issues.apache.org/jira/browse/CASSANDRA-17513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yifan Cai updated CASSANDRA-17513: -- Workflow: Copy of Cassandra Default Workflow (was: Copy of Cassandra Bug Workflow) Issue Type: Improvement (was: Bug) > Adding support for TLS client authentication for internode communication > > > Key: CASSANDRA-17513 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17513 > Project: Cassandra > Issue Type: Improvement > Components: Feature/Encryption, Local/Config >Reporter: Jyothsna Konisa >Assignee: Jyothsna Konisa >Priority: Normal > Time Spent: 4.5h > Remaining Estimate: 0h > > Same keystore is being set for both Inbound and outbound connections but we > should use a keystore with server certificate for Inbound connections and a > keystore with client certificates for outbound connections. So we should add > a new property in Cassandra.yaml to pass outbound keystore and use it in > SSLContextFactory for creating outbound SSL context. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17624) WEBSITE - Fix vanity image on 4.1 Guardrails blog post
[ https://issues.apache.org/jira/browse/CASSANDRA-17624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17624: -- Change Category: Semantic Complexity: Normal Component/s: Documentation/Blog Fix Version/s: 4.1-rc Reviewers: Erick Ramirez Status: Open (was: Triage Needed) > WEBSITE - Fix vanity image on 4.1 Guardrails blog post > -- > > Key: CASSANDRA-17624 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17624 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Fix For: 4.1-rc > > Attachments: > apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg > > > The image attached to the [Apache Cassandra 4.1 Features: Guardrails > Framework|https://cassandra.staged.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html] > blog post is too large for the page. > It needs to be replaced with the attached image supplied by [~Calico]: > !apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg|width=300! -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17549) jvm-dtest unhandled exceptions failing the test no longer work
[ https://issues.apache.org/jira/browse/CASSANDRA-17549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536387#comment-17536387 ] David Capwell commented on CASSANDRA-17549: --- Starting commit CI Results (pending): ||Branch||Source||Circle CI||Jenkins|| |cassandra-4.1|[branch|https://github.com/dcapwell/cassandra/tree/commit_remote_branch/CASSANDRA-17549-cassandra-4.1-6D2B7DB9-6A18-49E4-928D-A269DD2942FD]|[build|https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-17549-cassandra-4.1-6D2B7DB9-6A18-49E4-928D-A269DD2942FD]|[build|unknown]| |trunk|[branch|https://github.com/dcapwell/cassandra/tree/commit_remote_branch/CASSANDRA-17549-trunk-6D2B7DB9-6A18-49E4-928D-A269DD2942FD]|[build|https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-17549-trunk-6D2B7DB9-6A18-49E4-928D-A269DD2942FD]|[build|unknown]| > jvm-dtest unhandled exceptions failing the test no longer work > -- > > Key: CASSANDRA-17549 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17549 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 4.1-beta > > > Seems that ([CASSANDRA-16925] CEP-10 Phase 1: Mockable Task Execution) > refactored and avoided using AbstractCluster.uncaughtException, this means > that the logic to detect unexpected exceptions to fail tests no longer works. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17624) WEBSITE - Fix vanity image on 4.1 Guardrails blog post
Erick Ramirez created CASSANDRA-17624: - Summary: WEBSITE - Fix vanity image on 4.1 Guardrails blog post Key: CASSANDRA-17624 URL: https://issues.apache.org/jira/browse/CASSANDRA-17624 Project: Cassandra Issue Type: Task Reporter: Erick Ramirez Assignee: Erick Ramirez Attachments: apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg The image attached to the [Apache Cassandra 4.1 Features: Guardrails Framework|https://cassandra.staged.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html] blog post is too large for the page. It needs to be replaced with the attached image supplied by [~Calico]: !apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg|width=300! -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17513) Adding support for TLS client authentication for internode communication
[ https://issues.apache.org/jira/browse/CASSANDRA-17513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536374#comment-17536374 ] Yifan Cai edited comment on CASSANDRA-17513 at 5/12/22 11:37 PM: - For posterity, PR: [https://github.com/apache/cassandra/pull/1535] CI: [https://app.circleci.com/pipelines/github/yifan-c/cassandra?branch=r%2Fpr1535=all] was (Author: yifanc): For posterity, the PR is [https://github.com/apache/cassandra/pull/1535] > Adding support for TLS client authentication for internode communication > > > Key: CASSANDRA-17513 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17513 > Project: Cassandra > Issue Type: Bug > Components: Feature/Encryption, Local/Config >Reporter: Jyothsna Konisa >Assignee: Jyothsna Konisa >Priority: Normal > Time Spent: 4.5h > Remaining Estimate: 0h > > Same keystore is being set for both Inbound and outbound connections but we > should use a keystore with server certificate for Inbound connections and a > keystore with client certificates for outbound connections. So we should add > a new property in Cassandra.yaml to pass outbound keystore and use it in > SSLContextFactory for creating outbound SSL context. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17513) Adding support for TLS client authentication for internode communication
[ https://issues.apache.org/jira/browse/CASSANDRA-17513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yifan Cai updated CASSANDRA-17513: -- Reviewers: Bernardo Botella, Francisco Guerrero, Maulin Vasavada, Yifan Cai, Yifan Cai Status: Review In Progress (was: Patch Available) Adding the folks who have left review comments as reviewers. > Adding support for TLS client authentication for internode communication > > > Key: CASSANDRA-17513 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17513 > Project: Cassandra > Issue Type: Bug > Components: Feature/Encryption, Local/Config >Reporter: Jyothsna Konisa >Assignee: Jyothsna Konisa >Priority: Normal > Time Spent: 4.5h > Remaining Estimate: 0h > > Same keystore is being set for both Inbound and outbound connections but we > should use a keystore with server certificate for Inbound connections and a > keystore with client certificates for outbound connections. So we should add > a new property in Cassandra.yaml to pass outbound keystore and use it in > SSLContextFactory for creating outbound SSL context. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17513) Adding support for TLS client authentication for internode communication
[ https://issues.apache.org/jira/browse/CASSANDRA-17513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yifan Cai updated CASSANDRA-17513: -- Reviewers: Bernardo Botella, Francisco Guerrero, Maulin Vasavada, Yifan Cai (was: Bernardo Botella, Francisco Guerrero, Maulin Vasavada, Yifan Cai, Yifan Cai) > Adding support for TLS client authentication for internode communication > > > Key: CASSANDRA-17513 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17513 > Project: Cassandra > Issue Type: Bug > Components: Feature/Encryption, Local/Config >Reporter: Jyothsna Konisa >Assignee: Jyothsna Konisa >Priority: Normal > Time Spent: 4.5h > Remaining Estimate: 0h > > Same keystore is being set for both Inbound and outbound connections but we > should use a keystore with server certificate for Inbound connections and a > keystore with client certificates for outbound connections. So we should add > a new property in Cassandra.yaml to pass outbound keystore and use it in > SSLContextFactory for creating outbound SSL context. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17513) Adding support for TLS client authentication for internode communication
[ https://issues.apache.org/jira/browse/CASSANDRA-17513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yifan Cai updated CASSANDRA-17513: -- Test and Documentation Plan: unit test Status: Patch Available (was: Open) For posterity, the PR is [https://github.com/apache/cassandra/pull/1535] > Adding support for TLS client authentication for internode communication > > > Key: CASSANDRA-17513 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17513 > Project: Cassandra > Issue Type: Bug > Components: Feature/Encryption, Local/Config >Reporter: Jyothsna Konisa >Assignee: Jyothsna Konisa >Priority: Normal > Time Spent: 4.5h > Remaining Estimate: 0h > > Same keystore is being set for both Inbound and outbound connections but we > should use a keystore with server certificate for Inbound connections and a > keystore with client certificates for outbound connections. So we should add > a new property in Cassandra.yaml to pass outbound keystore and use it in > SSLContextFactory for creating outbound SSL context. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17513) Adding support for TLS client authentication for internode communication
[ https://issues.apache.org/jira/browse/CASSANDRA-17513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yifan Cai updated CASSANDRA-17513: -- Bug Category: Parent values: Code(13163)Level 1 values: Bug - Unclear Impact(13164) Complexity: Normal Component/s: Feature/Encryption Local/Config Discovered By: User Report Severity: Low Status: Open (was: Triage Needed) Opening the issue. Somehow it was categorized as "Bug", which should really be an "Improvement" instead, IMO. Jira won't allow to change the type. I am filling the required fields at my best effort :] > Adding support for TLS client authentication for internode communication > > > Key: CASSANDRA-17513 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17513 > Project: Cassandra > Issue Type: Bug > Components: Feature/Encryption, Local/Config >Reporter: Jyothsna Konisa >Assignee: Jyothsna Konisa >Priority: Normal > Time Spent: 4.5h > Remaining Estimate: 0h > > Same keystore is being set for both Inbound and outbound connections but we > should use a keystore with server certificate for Inbound connections and a > keystore with client certificates for outbound connections. So we should add > a new property in Cassandra.yaml to pass outbound keystore and use it in > SSLContextFactory for creating outbound SSL context. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17606) Fix dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD.test_rolling_upgrade_with_in
[
https://issues.apache.org/jira/browse/CASSANDRA-17606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536367#comment-17536367
]
Ekaterina Dimitrova edited comment on CASSANDRA-17606 at 5/12/22 11:02 PM:
---
Yup, that's what I meant, at most.
I am not against, just wondering whether it makes sense to make it more clear.
Also, it seems 10 was considered reasonable.
Let's see
was (Author: e.dimitrova):
Yup, that's what I meant.
I am not against, just wondering whether it makes sense to make it more clear.
Also, it seems 10 was considered reasonable.
Let's see
> Fix
> dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD.test_rolling_upgrade_with_internode_ssl
> -
>
> Key: CASSANDRA-17606
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17606
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.x, 4.1-beta
>
>
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1126/testReport/dtest-upgrade.upgrade_tests.upgrade_through_versions_test/TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD/test_rolling_upgrade_with_internode_ssl/]
> Failed twice on trunk.
> h3.
> {code:java}
> Error Message
> test teardown failure
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [WARN [MessagingService-Incoming-/127.0.0.2] 2022-05-03 21:37:48,446
> IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from
> socket; closing org.apache.cassandra.db.UnknownColumnFamilyException: Got
> slice command for nonexistent table system_auth.roles. If the table was just
> created, this is likely due to the schema not being fully propagated. Please
> wait for schema agreement on table creation. at
> org.apache.cassandra.db.SliceFromReadCommandSerializer.deserialize(SliceFromReadCommand.java:184)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:158)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:132)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.MessageIn.read(MessageIn.java:99)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:200)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:177)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91)
> ~[apache-cassandra-2.2.19.jar:2.2.19], WARN
> [MessagingService-Incoming-/127.0.0.2] 2022-05-03 21:37:48,446
> IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from
> socket; closing org.apache.cassandra.db.UnknownColumnFamilyException: Got
> slice command for nonexistent table system_auth.roles. If the table was just
> created, this is likely due to the schema not being fully propagated. Please
> wait for schema agreement on table creation. at
> org.apache.cassandra.db.SliceFromReadCommandSerializer.deserialize(SliceFromReadCommand.java:184)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:158)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:132)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.MessageIn.read(MessageIn.java:99)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:200)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:177)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91)
> ~[apache-cassandra-2.2.19.jar:2.2.19]]
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17606) Fix dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD.test_rolling_upgrade_with_interno
[
https://issues.apache.org/jira/browse/CASSANDRA-17606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536367#comment-17536367
]
Ekaterina Dimitrova commented on CASSANDRA-17606:
-
Yup, that's what I meant.
I am not against, just wondering whether it makes sense to make it more clear.
Also, it seems 10 was considered reasonable.
Let's see
> Fix
> dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD.test_rolling_upgrade_with_internode_ssl
> -
>
> Key: CASSANDRA-17606
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17606
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.x, 4.1-beta
>
>
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1126/testReport/dtest-upgrade.upgrade_tests.upgrade_through_versions_test/TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD/test_rolling_upgrade_with_internode_ssl/]
> Failed twice on trunk.
> h3.
> {code:java}
> Error Message
> test teardown failure
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [WARN [MessagingService-Incoming-/127.0.0.2] 2022-05-03 21:37:48,446
> IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from
> socket; closing org.apache.cassandra.db.UnknownColumnFamilyException: Got
> slice command for nonexistent table system_auth.roles. If the table was just
> created, this is likely due to the schema not being fully propagated. Please
> wait for schema agreement on table creation. at
> org.apache.cassandra.db.SliceFromReadCommandSerializer.deserialize(SliceFromReadCommand.java:184)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:158)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:132)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.MessageIn.read(MessageIn.java:99)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:200)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:177)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91)
> ~[apache-cassandra-2.2.19.jar:2.2.19], WARN
> [MessagingService-Incoming-/127.0.0.2] 2022-05-03 21:37:48,446
> IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from
> socket; closing org.apache.cassandra.db.UnknownColumnFamilyException: Got
> slice command for nonexistent table system_auth.roles. If the table was just
> created, this is likely due to the schema not being fully propagated. Please
> wait for schema agreement on table creation. at
> org.apache.cassandra.db.SliceFromReadCommandSerializer.deserialize(SliceFromReadCommand.java:184)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:158)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:132)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.MessageIn.read(MessageIn.java:99)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:200)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:177)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91)
> ~[apache-cassandra-2.2.19.jar:2.2.19]]
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17606) Fix dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD.test_rolling_upgrade_with_interno
[
https://issues.apache.org/jira/browse/CASSANDRA-17606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536366#comment-17536366
]
Brandon Williams commented on CASSANDRA-17606:
--
Yes, it's at most 15s since it's not blindly sleeping. As for removing the
blind sleep, let's try it:
[jenkins|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1706/] and
[circle|https://app.circleci.com/pipelines/github/driftx/cassandra/483/workflows/8a852510-8a8e-4c67-9613-159d6c7659d2/jobs/5563]
are queued up.
> Fix
> dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD.test_rolling_upgrade_with_internode_ssl
> -
>
> Key: CASSANDRA-17606
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17606
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.x, 4.1-beta
>
>
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1126/testReport/dtest-upgrade.upgrade_tests.upgrade_through_versions_test/TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD/test_rolling_upgrade_with_internode_ssl/]
> Failed twice on trunk.
> h3.
> {code:java}
> Error Message
> test teardown failure
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [WARN [MessagingService-Incoming-/127.0.0.2] 2022-05-03 21:37:48,446
> IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from
> socket; closing org.apache.cassandra.db.UnknownColumnFamilyException: Got
> slice command for nonexistent table system_auth.roles. If the table was just
> created, this is likely due to the schema not being fully propagated. Please
> wait for schema agreement on table creation. at
> org.apache.cassandra.db.SliceFromReadCommandSerializer.deserialize(SliceFromReadCommand.java:184)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:158)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:132)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.MessageIn.read(MessageIn.java:99)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:200)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:177)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91)
> ~[apache-cassandra-2.2.19.jar:2.2.19], WARN
> [MessagingService-Incoming-/127.0.0.2] 2022-05-03 21:37:48,446
> IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from
> socket; closing org.apache.cassandra.db.UnknownColumnFamilyException: Got
> slice command for nonexistent table system_auth.roles. If the table was just
> created, this is likely due to the schema not being fully propagated. Please
> wait for schema agreement on table creation. at
> org.apache.cassandra.db.SliceFromReadCommandSerializer.deserialize(SliceFromReadCommand.java:184)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:158)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:132)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.MessageIn.read(MessageIn.java:99)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:200)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:177)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91)
> ~[apache-cassandra-2.2.19.jar:2.2.19]]
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17549) jvm-dtest unhandled exceptions failing the test no longer work
[ https://issues.apache.org/jira/browse/CASSANDRA-17549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536363#comment-17536363 ] David Capwell commented on CASSANDRA-17549: --- Starting commit CI Results (pending): ||Branch||Source||Circle CI||Jenkins|| |cassandra-4.1|[branch|https://github.com/dcapwell/cassandra/tree/commit_remote_branch/CASSANDRA-17549-cassandra-4.1-CAB4FE23-1E00-4674-BD35-8E15B84CAFB4]|[build|https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-17549-cassandra-4.1-CAB4FE23-1E00-4674-BD35-8E15B84CAFB4]|[build|unknown]| |trunk|[branch|https://github.com/dcapwell/cassandra/tree/commit_remote_branch/CASSANDRA-17549-trunk-CAB4FE23-1E00-4674-BD35-8E15B84CAFB4]|[build|https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-17549-trunk-CAB4FE23-1E00-4674-BD35-8E15B84CAFB4]|[build|unknown]| > jvm-dtest unhandled exceptions failing the test no longer work > -- > > Key: CASSANDRA-17549 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17549 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 4.1-beta > > > Seems that ([CASSANDRA-16925] CEP-10 Phase 1: Mockable Task Execution) > refactored and avoided using AbstractCluster.uncaughtException, this means > that the logic to detect unexpected exceptions to fail tests no longer works. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] (CASSANDRA-17594) Fix flaky python-tests due to connection getting closed
[ https://issues.apache.org/jira/browse/CASSANDRA-17594 ]
David Capwell deleted comment on CASSANDRA-17594:
---
was (Author: dcapwell):
Starting commit
CI Results (pending):
||Branch||Source||Circle CI||Jenkins||
|cassandra-4.1|[branch|https://github.com/dcapwell/cassandra/tree/commit_remote_branch/CASSANDRA-17549-cassandra-4.1-CAB4FE23-1E00-4674-BD35-8E15B84CAFB4]|[build|https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-17549-cassandra-4.1-CAB4FE23-1E00-4674-BD35-8E15B84CAFB4]|[build|unknown]|
|trunk|[branch|https://github.com/dcapwell/cassandra/tree/commit_remote_branch/CASSANDRA-17549-trunk-CAB4FE23-1E00-4674-BD35-8E15B84CAFB4]|[build|https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-17549-trunk-CAB4FE23-1E00-4674-BD35-8E15B84CAFB4]|[build|unknown]|
> Fix flaky python-tests due to connection getting closed
> ---
>
> Key: CASSANDRA-17594
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17594
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: NA
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> We log unknown exceptions at the networking level, which includes case where
> the remote side closes the connection (such as the cases caused by shutting
> down), depending on how quickly the instances shutdown, this could cause
> python-dtest to fail for random tests with a message such as
> {code}
> Unexpected error found in node logs (see stdout for full details). Errors:
> [WARN [epollEventLoopGroup-5-9] 2022-05-03T16:47:03,800
> ExceptionHandlers.java:134 - Unknown exception in client networking
> io.netty.channel.unix.Errors$NativeIoException: writeAddress(..) failed:
> Connection reset by peer, WARN [epollEventLoopGroup-5-9]
> 2022-05-03T16:47:03,800 ExceptionHandlers.java:134 - Unknown exception in
> client networking
> io.netty.channel.unix.Errors$NativeIoException: writeAddress(..) failed:
> Connection reset by peer]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17606) Fix dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD.test_rolling_upgrade_with_in
[
https://issues.apache.org/jira/browse/CASSANDRA-17606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536360#comment-17536360
]
Ekaterina Dimitrova edited comment on CASSANDRA-17606 at 5/12/22 10:37 PM:
---
So this new call raises the wait time from 5 to 15s? Looking at
max_schema_agreement_wait and considering the sleep is still there.
Wondering whether we want to remove then the sleep?
was (Author: e.dimitrova):
So this new call raises it from 5 to 15? Looking at max_schema_agreement_wait
and considering the sleep is still there.
Wondering whether we want to remove then the sleep?
> Fix
> dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD.test_rolling_upgrade_with_internode_ssl
> -
>
> Key: CASSANDRA-17606
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17606
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.x, 4.1-beta
>
>
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1126/testReport/dtest-upgrade.upgrade_tests.upgrade_through_versions_test/TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD/test_rolling_upgrade_with_internode_ssl/]
> Failed twice on trunk.
> h3.
> {code:java}
> Error Message
> test teardown failure
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [WARN [MessagingService-Incoming-/127.0.0.2] 2022-05-03 21:37:48,446
> IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from
> socket; closing org.apache.cassandra.db.UnknownColumnFamilyException: Got
> slice command for nonexistent table system_auth.roles. If the table was just
> created, this is likely due to the schema not being fully propagated. Please
> wait for schema agreement on table creation. at
> org.apache.cassandra.db.SliceFromReadCommandSerializer.deserialize(SliceFromReadCommand.java:184)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:158)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:132)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.MessageIn.read(MessageIn.java:99)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:200)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:177)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91)
> ~[apache-cassandra-2.2.19.jar:2.2.19], WARN
> [MessagingService-Incoming-/127.0.0.2] 2022-05-03 21:37:48,446
> IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from
> socket; closing org.apache.cassandra.db.UnknownColumnFamilyException: Got
> slice command for nonexistent table system_auth.roles. If the table was just
> created, this is likely due to the schema not being fully propagated. Please
> wait for schema agreement on table creation. at
> org.apache.cassandra.db.SliceFromReadCommandSerializer.deserialize(SliceFromReadCommand.java:184)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:158)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:132)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.MessageIn.read(MessageIn.java:99)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:200)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:177)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91)
> ~[apache-cassandra-2.2.19.jar:2.2.19]]
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17606) Fix dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD.test_rolling_upgrade_with_internode
[
https://issues.apache.org/jira/browse/CASSANDRA-17606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17606:
Reviewers: Ekaterina Dimitrova, Ekaterina Dimitrova
Ekaterina Dimitrova, Ekaterina Dimitrova (was: Ekaterina
Dimitrova)
Status: Review In Progress (was: Patch Available)
> Fix
> dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD.test_rolling_upgrade_with_internode_ssl
> -
>
> Key: CASSANDRA-17606
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17606
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.x, 4.1-beta
>
>
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1126/testReport/dtest-upgrade.upgrade_tests.upgrade_through_versions_test/TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD/test_rolling_upgrade_with_internode_ssl/]
> Failed twice on trunk.
> h3.
> {code:java}
> Error Message
> test teardown failure
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [WARN [MessagingService-Incoming-/127.0.0.2] 2022-05-03 21:37:48,446
> IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from
> socket; closing org.apache.cassandra.db.UnknownColumnFamilyException: Got
> slice command for nonexistent table system_auth.roles. If the table was just
> created, this is likely due to the schema not being fully propagated. Please
> wait for schema agreement on table creation. at
> org.apache.cassandra.db.SliceFromReadCommandSerializer.deserialize(SliceFromReadCommand.java:184)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:158)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:132)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.MessageIn.read(MessageIn.java:99)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:200)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:177)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91)
> ~[apache-cassandra-2.2.19.jar:2.2.19], WARN
> [MessagingService-Incoming-/127.0.0.2] 2022-05-03 21:37:48,446
> IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from
> socket; closing org.apache.cassandra.db.UnknownColumnFamilyException: Got
> slice command for nonexistent table system_auth.roles. If the table was just
> created, this is likely due to the schema not being fully propagated. Please
> wait for schema agreement on table creation. at
> org.apache.cassandra.db.SliceFromReadCommandSerializer.deserialize(SliceFromReadCommand.java:184)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:158)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:132)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.MessageIn.read(MessageIn.java:99)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:200)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:177)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91)
> ~[apache-cassandra-2.2.19.jar:2.2.19]]
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17606) Fix dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD.test_rolling_upgrade_with_interno
[
https://issues.apache.org/jira/browse/CASSANDRA-17606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536360#comment-17536360
]
Ekaterina Dimitrova commented on CASSANDRA-17606:
-
So this new call raises it from 5 to 15? Looking at max_schema_agreement_wait
and considering the sleep is still there.
Wondering whether we want to remove then the sleep?
> Fix
> dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD.test_rolling_upgrade_with_internode_ssl
> -
>
> Key: CASSANDRA-17606
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17606
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.x, 4.1-beta
>
>
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1126/testReport/dtest-upgrade.upgrade_tests.upgrade_through_versions_test/TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD/test_rolling_upgrade_with_internode_ssl/]
> Failed twice on trunk.
> h3.
> {code:java}
> Error Message
> test teardown failure
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [WARN [MessagingService-Incoming-/127.0.0.2] 2022-05-03 21:37:48,446
> IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from
> socket; closing org.apache.cassandra.db.UnknownColumnFamilyException: Got
> slice command for nonexistent table system_auth.roles. If the table was just
> created, this is likely due to the schema not being fully propagated. Please
> wait for schema agreement on table creation. at
> org.apache.cassandra.db.SliceFromReadCommandSerializer.deserialize(SliceFromReadCommand.java:184)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:158)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:132)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.MessageIn.read(MessageIn.java:99)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:200)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:177)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91)
> ~[apache-cassandra-2.2.19.jar:2.2.19], WARN
> [MessagingService-Incoming-/127.0.0.2] 2022-05-03 21:37:48,446
> IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from
> socket; closing org.apache.cassandra.db.UnknownColumnFamilyException: Got
> slice command for nonexistent table system_auth.roles. If the table was just
> created, this is likely due to the schema not being fully propagated. Please
> wait for schema agreement on table creation. at
> org.apache.cassandra.db.SliceFromReadCommandSerializer.deserialize(SliceFromReadCommand.java:184)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:158)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:132)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.MessageIn.read(MessageIn.java:99)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:200)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:177)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91)
> ~[apache-cassandra-2.2.19.jar:2.2.19]]
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17594) Fix flaky python-tests due to connection getting closed
[
https://issues.apache.org/jira/browse/CASSANDRA-17594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536361#comment-17536361
]
David Capwell commented on CASSANDRA-17594:
---
Starting commit
CI Results (pending):
||Branch||Source||Circle CI||Jenkins||
|cassandra-4.1|[branch|https://github.com/dcapwell/cassandra/tree/commit_remote_branch/CASSANDRA-17549-cassandra-4.1-CAB4FE23-1E00-4674-BD35-8E15B84CAFB4]|[build|https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-17549-cassandra-4.1-CAB4FE23-1E00-4674-BD35-8E15B84CAFB4]|[build|unknown]|
|trunk|[branch|https://github.com/dcapwell/cassandra/tree/commit_remote_branch/CASSANDRA-17549-trunk-CAB4FE23-1E00-4674-BD35-8E15B84CAFB4]|[build|https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-17549-trunk-CAB4FE23-1E00-4674-BD35-8E15B84CAFB4]|[build|unknown]|
> Fix flaky python-tests due to connection getting closed
> ---
>
> Key: CASSANDRA-17594
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17594
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: NA
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> We log unknown exceptions at the networking level, which includes case where
> the remote side closes the connection (such as the cases caused by shutting
> down), depending on how quickly the instances shutdown, this could cause
> python-dtest to fail for random tests with a message such as
> {code}
> Unexpected error found in node logs (see stdout for full details). Errors:
> [WARN [epollEventLoopGroup-5-9] 2022-05-03T16:47:03,800
> ExceptionHandlers.java:134 - Unknown exception in client networking
> io.netty.channel.unix.Errors$NativeIoException: writeAddress(..) failed:
> Connection reset by peer, WARN [epollEventLoopGroup-5-9]
> 2022-05-03T16:47:03,800 ExceptionHandlers.java:134 - Unknown exception in
> client networking
> io.netty.channel.unix.Errors$NativeIoException: writeAddress(..) failed:
> Connection reset by peer]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17606) Fix dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD.test_rolling_upgrade_with_internode
[
https://issues.apache.org/jira/browse/CASSANDRA-17606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-17606:
-
Test and Documentation Plan: run CI
Status: Patch Available (was: Open)
> Fix
> dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD.test_rolling_upgrade_with_internode_ssl
> -
>
> Key: CASSANDRA-17606
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17606
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.x, 4.1-beta
>
>
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1126/testReport/dtest-upgrade.upgrade_tests.upgrade_through_versions_test/TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD/test_rolling_upgrade_with_internode_ssl/]
> Failed twice on trunk.
> h3.
> {code:java}
> Error Message
> test teardown failure
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [WARN [MessagingService-Incoming-/127.0.0.2] 2022-05-03 21:37:48,446
> IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from
> socket; closing org.apache.cassandra.db.UnknownColumnFamilyException: Got
> slice command for nonexistent table system_auth.roles. If the table was just
> created, this is likely due to the schema not being fully propagated. Please
> wait for schema agreement on table creation. at
> org.apache.cassandra.db.SliceFromReadCommandSerializer.deserialize(SliceFromReadCommand.java:184)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:158)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:132)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.MessageIn.read(MessageIn.java:99)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:200)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:177)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91)
> ~[apache-cassandra-2.2.19.jar:2.2.19], WARN
> [MessagingService-Incoming-/127.0.0.2] 2022-05-03 21:37:48,446
> IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from
> socket; closing org.apache.cassandra.db.UnknownColumnFamilyException: Got
> slice command for nonexistent table system_auth.roles. If the table was just
> created, this is likely due to the schema not being fully propagated. Please
> wait for schema agreement on table creation. at
> org.apache.cassandra.db.SliceFromReadCommandSerializer.deserialize(SliceFromReadCommand.java:184)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:158)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:132)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.MessageIn.read(MessageIn.java:99)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:200)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:177)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91)
> ~[apache-cassandra-2.2.19.jar:2.2.19]]
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17606) Fix dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD.test_rolling_upgrade_with_interno
[
https://issues.apache.org/jira/browse/CASSANDRA-17606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536358#comment-17536358
]
Brandon Williams commented on CASSANDRA-17606:
--
I've got a
[branch|https://github.com/driftx/cassandra-dtest/tree/CASSANDRA-17606] that
adds a wait for schema agreement at the end of both schema creation calls, and
it has a run in
[jenkins|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1705/] and 100
in
[circle|https://app.circleci.com/pipelines/github/driftx/cassandra/482/workflows/67c88777-35b9-4931-ac5a-93d6c321aa1a/jobs/5561]
passed. While we don't yet have a way to multiplex a test in Jenkins, in
practice I was able to reproduce this before the patch and am unable after, so
I don't think this was _just_ an environmental thing. Regardless, waiting for
schema agreement is the correct thing to do and perhaps what
[this|https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_through_versions_test.py#L388]
is trying to accomplish.
> Fix
> dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD.test_rolling_upgrade_with_internode_ssl
> -
>
> Key: CASSANDRA-17606
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17606
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.x, 4.1-beta
>
>
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1126/testReport/dtest-upgrade.upgrade_tests.upgrade_through_versions_test/TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD/test_rolling_upgrade_with_internode_ssl/]
> Failed twice on trunk.
> h3.
> {code:java}
> Error Message
> test teardown failure
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [WARN [MessagingService-Incoming-/127.0.0.2] 2022-05-03 21:37:48,446
> IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from
> socket; closing org.apache.cassandra.db.UnknownColumnFamilyException: Got
> slice command for nonexistent table system_auth.roles. If the table was just
> created, this is likely due to the schema not being fully propagated. Please
> wait for schema agreement on table creation. at
> org.apache.cassandra.db.SliceFromReadCommandSerializer.deserialize(SliceFromReadCommand.java:184)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:158)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:132)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.MessageIn.read(MessageIn.java:99)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:200)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:177)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91)
> ~[apache-cassandra-2.2.19.jar:2.2.19], WARN
> [MessagingService-Incoming-/127.0.0.2] 2022-05-03 21:37:48,446
> IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from
> socket; closing org.apache.cassandra.db.UnknownColumnFamilyException: Got
> slice command for nonexistent table system_auth.roles. If the table was just
> created, this is likely due to the schema not being fully propagated. Please
> wait for schema agreement on table creation. at
> org.apache.cassandra.db.SliceFromReadCommandSerializer.deserialize(SliceFromReadCommand.java:184)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:158)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:132)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.MessageIn.read(MessageIn.java:99)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:200)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:177)
> ~[apache-cassandra-2.2.19.jar:2.2.19] at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91)
> ~[apache-cassandra-2.2.19.jar:2.2.19]]
> {code}
>
--
This message was sent by Atlassian Jira
[jira] [Updated] (CASSANDRA-17623) Frozen maps may be serialized unsorted, causing inability to query later
[
https://issues.apache.org/jira/browse/CASSANDRA-17623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Rohrer updated CASSANDRA-17623:
Authors: Doug Rohrer, Francisco Guerrero, Yifan Cai
(was: Doug Rohrer)
Test and Documentation Plan:
Unit tests at multiple levels added to test.
Github PR at https://github.com/apache/cassandra/pull/1621
Status: Patch Available (was: Open)
> Frozen maps may be serialized unsorted, causing inability to query later
>
>
> Key: CASSANDRA-17623
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17623
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Semantics
>Reporter: Doug Rohrer
>Assignee: Doug Rohrer
>Priority: Normal
>
> CASSANDRA-7859 introduced the ability to use frozen collections as parts of
> primary keys. This +requires+ all frozen maps to be persisted with their
> entries sorted by the map keys. If the map is +not+ sorted correctly, it
> becomes impossible to project all of the map values out of the map using the
> map projection/selection syntax. For example, the select below would fail if
> the map was not sorted correctly and the higher-valued key was persisted
> first:
> {code:sql}
> CREATE TABLE test.test (k text, c frozen>, PRIMARY KEY (k,
> c));
> INSERT INTO test.test (k, c) VALUES ('key', {'z':'second_value',
> 'a':'first_value'});
> SELECT k, c['a'] from test.test where k='key' -- c['a'] would return NULL here
> {code}
> Additionally, if you attempted to select just that row by using the complete
> map value in a WHERE clause, which is also supported, it would return no rows
> unless the map provided by the query processor just happened to be sorted the
> same way as the persisted value.
> However, there is a bug in Maps.java where we don't actually use a SortedMap
> in {{Maps.Value#fromSerialized}}, which manifests if a client sends an
> unsorted map as a bound parameter to a query on insert or select. In either
> case, the map may not be sorted correctly, leading to either invalid data
> being persisted to disk (in the INSERT case) or the query not being able to
> be executed/returning 0 rows even though a row _should_ exist (SELECT).
> This bug affects any usage of parameterized queries (tested with the DataStax
> driver, and was originally discovered when using the CQLSSTableWriter code to
> write data locally).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17623) Frozen maps may be serialized unsorted, causing inability to query later
[
https://issues.apache.org/jira/browse/CASSANDRA-17623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Rohrer updated CASSANDRA-17623:
Bug Category: Parent values: Correctness(12982)Level 1 values: Recoverable
Corruption / Loss(12986)
Complexity: Challenging
Component/s: CQL/Semantics
Discovered By: User Report
Severity: Normal
Status: Open (was: Triage Needed)
> Frozen maps may be serialized unsorted, causing inability to query later
>
>
> Key: CASSANDRA-17623
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17623
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Semantics
>Reporter: Doug Rohrer
>Assignee: Doug Rohrer
>Priority: Normal
>
> CASSANDRA-7859 introduced the ability to use frozen collections as parts of
> primary keys. This +requires+ all frozen maps to be persisted with their
> entries sorted by the map keys. If the map is +not+ sorted correctly, it
> becomes impossible to project all of the map values out of the map using the
> map projection/selection syntax. For example, the select below would fail if
> the map was not sorted correctly and the higher-valued key was persisted
> first:
> {code:sql}
> CREATE TABLE test.test (k text, c frozen>, PRIMARY KEY (k,
> c));
> INSERT INTO test.test (k, c) VALUES ('key', {'z':'second_value',
> 'a':'first_value'});
> SELECT k, c['a'] from test.test where k='key' -- c['a'] would return NULL here
> {code}
> Additionally, if you attempted to select just that row by using the complete
> map value in a WHERE clause, which is also supported, it would return no rows
> unless the map provided by the query processor just happened to be sorted the
> same way as the persisted value.
> However, there is a bug in Maps.java where we don't actually use a SortedMap
> in {{Maps.Value#fromSerialized}}, which manifests if a client sends an
> unsorted map as a bound parameter to a query on insert or select. In either
> case, the map may not be sorted correctly, leading to either invalid data
> being persisted to disk (in the INSERT case) or the query not being able to
> be executed/returning 0 rows even though a row _should_ exist (SELECT).
> This bug affects any usage of parameterized queries (tested with the DataStax
> driver, and was originally discovered when using the CQLSSTableWriter code to
> write data locally).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17619) Expired snapshots of dropped tables are not removed after node restart
[
https://issues.apache.org/jira/browse/CASSANDRA-17619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536348#comment-17536348
]
Paulo Motta commented on CASSANDRA-17619:
-
Previous CI did not complete due to OOM.
Resubmitted new CI on rebased patch:
|[CASSANDRA-17619-4.1-rebased|https://github.com/pauloricardomg/cassandra/tree/CASSANDRA-17619-4.1-rebased]|[4.1
CI|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1704/]|
> Expired snapshots of dropped tables are not removed after node restart
> --
>
> Key: CASSANDRA-17619
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17619
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Snapshots
>Reporter: Paulo Motta
>Assignee: Paulo Motta
>Priority: Normal
> Fix For: 4.1-beta
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Expired TTL snapshots from a dropped table are only removed if the node is
> not restarted after the table is dropped.
> The reason for this is because {{SnapshotManager}} is using the old
> implementation of {{listsnapshots}} to load snapshots in memory during node
> startup, before CASSANDRA-16843 is fixed so it doesn't keep track of
> snapshots of dropped tables.
> We should make {{SnapshotManager}} use the new implementation to load
> snapshots of dropped tables in memory, what ensures they will be removed when
> expired.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17619) Expired snapshots of dropped tables are not removed after node restart
[
https://issues.apache.org/jira/browse/CASSANDRA-17619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paulo Motta updated CASSANDRA-17619:
Status: Patch Available (was: In Progress)
> Expired snapshots of dropped tables are not removed after node restart
> --
>
> Key: CASSANDRA-17619
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17619
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Snapshots
>Reporter: Paulo Motta
>Assignee: Paulo Motta
>Priority: Normal
> Fix For: 4.1-beta
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Expired TTL snapshots from a dropped table are only removed if the node is
> not restarted after the table is dropped.
> The reason for this is because {{SnapshotManager}} is using the old
> implementation of {{listsnapshots}} to load snapshots in memory during node
> startup, before CASSANDRA-16843 is fixed so it doesn't keep track of
> snapshots of dropped tables.
> We should make {{SnapshotManager}} use the new implementation to load
> snapshots of dropped tables in memory, what ensures they will be removed when
> expired.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17619) Expired snapshots of dropped tables are not removed after node restart
[
https://issues.apache.org/jira/browse/CASSANDRA-17619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paulo Motta updated CASSANDRA-17619:
Status: In Progress (was: Changes Suggested)
> Expired snapshots of dropped tables are not removed after node restart
> --
>
> Key: CASSANDRA-17619
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17619
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Snapshots
>Reporter: Paulo Motta
>Assignee: Paulo Motta
>Priority: Normal
> Fix For: 4.1-beta
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Expired TTL snapshots from a dropped table are only removed if the node is
> not restarted after the table is dropped.
> The reason for this is because {{SnapshotManager}} is using the old
> implementation of {{listsnapshots}} to load snapshots in memory during node
> startup, before CASSANDRA-16843 is fixed so it doesn't keep track of
> snapshots of dropped tables.
> We should make {{SnapshotManager}} use the new implementation to load
> snapshots of dropped tables in memory, what ensures they will be removed when
> expired.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17619) Expired snapshots of dropped tables are not removed after node restart
[
https://issues.apache.org/jira/browse/CASSANDRA-17619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536341#comment-17536341
]
Paulo Motta commented on CASSANDRA-17619:
-
Addressed review comments on github
[PR|https://github.com/apache/cassandra/pull/1615] and fixed two extra nits
found during testing:
* [fix
log|https://github.com/apache/cassandra/pull/1615/commits/333f813f6872b87f7e0f79f71a4f9688a9cc3193]
* [Add verbose log to
trace|https://github.com/apache/cassandra/pull/1615/commits/c2d7c679c3492b66d41f8c60ce29d38efdf1c88e]
This is what the output of nodetool listsnapshots looks like after doing the
following operations:
* global snapshot of all keyspaces
* drop keyspace ks2 with auto_snapshot_ttl unset
* drop keyspace ks1 with auto_snapshot_ttl=1 minute
* nodetool snapshots
{noformat}
grep -v "all_keyspaces_snapshot" snapshot.txt
Snapshot Details:
Snapshot name Keyspace name Column family name
True size Size on disk Creation timeExpiration time
dropped-1652386867075-my_table ks2my_table
5.81 KiB 5.81 KiB 2022-05-12T20:21:07.075Z
dropped-1652388565491-my_table ks my_table
5.83 KiB 5.83 KiB 2022-05-12T20:49:25.491Z 2022-05-12T20:50:25.491Z
dropped-1652388565604-my_table2 ks my_table2
5.83 KiB 5.83 KiB 2022-05-12T20:49:25.604Z 2022-05-12T20:50:25.604Z
dropped-1652386867016-my_table2 ks2my_table2
5.81 KiB 5.81 KiB 2022-05-12T20:21:07.016Z
Total TrueDiskSpaceUsed: 0 byte
pmottagomes@C02FD3GTMD6R Documents %
{noformat}
After this I restarted the node and verified the snapshot from ks1 was removed
after 1 minute:
{noformat}
Snapshot Details:
Snapshot name Keyspace name Column family name
True size Size on disk Creation timeExpiration time
dropped-1652386867075-my_table ks2my_table
5.81 KiB 5.81 KiB 2022-05-12T20:21:07.075Z
dropped-1652386867016-my_table2 ks2my_table2
5.81 KiB 5.81 KiB 2022-05-12T20:21:07.016Z
Total TrueDiskSpaceUsed: 0 bytes
{noformat}
This is the debug logs of the manual test above:
{noformat}
DEBUG [main] 2022-05-12 17:51:07,265 SnapshotManager.java:119 - Adding
snapshots:
system:peers:37f71aca-7dc2-383b-a706-72528af04d4f:all_keyspaces_snapshot,
system:transferred_ranges:6cad20f7-d4f5-3af2-b6e2-0da33c6c1f83:all_keyspaces_snapshot,
system_traces:sessions:c5e99f16-8677-3914-b17e-960613512345:all_keyspaces_snapshot,
system_schema:dropped_columns:5e7583b5-f3f4-3af1-9a39-b7e1d6f5f11f:all_keyspaces_snapshot,
system_auth:role_members:0ecdaa87-f8fb-3e60-88d1-74fb36fe5c0d:all_keyspaces_snapshot,
ks:my_table2:74a02c00-d230-11ec-b12d-d9d82874084f:dropped-1652388565604-my_table2,
system:repairs:a3d277d1-cfaf-36f5-a2a7-38d5eea9ad6a:all_keyspaces_snapshot,
ks2:my_table2:846d1fd0-d230-11ec-b12d-d9d82874084f:all_keyspaces_snapshot,
system:IndexInfo:9f5c6374-d485-3229-9a0a-5094af9ad1e3:all_keyspaces_snapshot,
system_schema:functions:96489b79-80be-3e14-a701-66a0b9159450:all_keyspaces_snapshot,
system:top_partitions:7e5a361c-317c-351f-b15f-ffd8afd3dd4b:all_keyspaces_snapshot,
system:peers_v2:c4325fbb-8e5e-3baf-bd07-0f9250ed818e:all_keyspaces_snapshot,
system_distributed:partition_denylist:d6123acc-8649-3496-9d4e-f3fe39a6018b:all_keyspaces_snapshot,
system_schema:views:9786ac1c-dd58-3201-a7cd-ad556410c985:all_keyspaces_snapshot,
system_auth:resource_role_permissons_index:5f2fbdad-91f1-3946-bd25-d5da3a5c35ec:all_keyspaces_snapshot,
system_schema:columns:24101c25-a2ae-3af7-87c1-b40ee1aca33f:all_keyspaces_snapshot,
system:transferred_ranges_v2:1ff78f1a-7df1-3a2a-a998-6f4932270af5:all_keyspaces_snapshot,
system:prepared_statements:18a9c257-6a0c-3841-ba71-8cd529849fef:all_keyspaces_snapshot,
system:local:7ad54392-bcdd-35a6-8417-4e047860b377:all_keyspaces_snapshot,
system_schema:types:5a8b1ca8-6602-3f77-a045-9273d308917a:all_keyspaces_snapshot,
ks2:my_table:8eada2d0-d230-11ec-b12d-d9d82874084f:dropped-1652386867075-my_table,
system:size_estimates:618f817b-005f-3678-b8a4-53f3930b8e86:all_keyspaces_snapshot,
ks2:my_table:8eada2d0-d230-11ec-b12d-d9d82874084f:all_keyspaces_snapshot,
system:peer_events:59dfeaea-8db2-3341-91ef-109974d81484:all_keyspaces_snapshot,
system_auth:roles:5bc52802-de25-35ed-aeab-188eecebb090:all_keyspaces_snapshot,
system_schema:indexes:0feb57ac-311f-382f-ba6d-9024d305702f:all_keyspaces_snapshot,
system_schema:keyspaces:abac5682-dea6-31c5-b535-b3d6cffd0fb6:all_keyspaces_snapshot,
system:table_estimates:176c39cd-b93d-33a5-a218-8eb06a56f66e:all_keyspaces_snapshot,
system_auth:network_permissions:d46780c2-2f1c-3db9-b4c1-b8d9fbc0cc23:all_keyspaces_snapshot,
[jira] [Assigned] (CASSANDRA-17623) Frozen maps may be serialized unsorted, causing inability to query later
[
https://issues.apache.org/jira/browse/CASSANDRA-17623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francisco Guerrero reassigned CASSANDRA-17623:
--
Assignee: Doug Rohrer
> Frozen maps may be serialized unsorted, causing inability to query later
>
>
> Key: CASSANDRA-17623
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17623
> Project: Cassandra
> Issue Type: Bug
>Reporter: Doug Rohrer
>Assignee: Doug Rohrer
>Priority: Normal
>
> CASSANDRA-7859 introduced the ability to use frozen collections as parts of
> primary keys. This +requires+ all frozen maps to be persisted with their
> entries sorted by the map keys. If the map is +not+ sorted correctly, it
> becomes impossible to project all of the map values out of the map using the
> map projection/selection syntax. For example, the select below would fail if
> the map was not sorted correctly and the higher-valued key was persisted
> first:
> {code:sql}
> CREATE TABLE test.test (k text, c frozen>, PRIMARY KEY (k,
> c));
> INSERT INTO test.test (k, c) VALUES ('key', {'z':'second_value',
> 'a':'first_value'});
> SELECT k, c['a'] from test.test where k='key' -- c['a'] would return NULL here
> {code}
> Additionally, if you attempted to select just that row by using the complete
> map value in a WHERE clause, which is also supported, it would return no rows
> unless the map provided by the query processor just happened to be sorted the
> same way as the persisted value.
> However, there is a bug in Maps.java where we don't actually use a SortedMap
> in {{Maps.Value#fromSerialized}}, which manifests if a client sends an
> unsorted map as a bound parameter to a query on insert or select. In either
> case, the map may not be sorted correctly, leading to either invalid data
> being persisted to disk (in the INSERT case) or the query not being able to
> be executed/returning 0 rows even though a row _should_ exist (SELECT).
> This bug affects any usage of parameterized queries (tested with the DataStax
> driver, and was originally discovered when using the CQLSSTableWriter code to
> write data locally).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17623) Frozen maps may be serialized unsorted, causing inability to query later
Doug Rohrer created CASSANDRA-17623:
---
Summary: Frozen maps may be serialized unsorted, causing inability
to query later
Key: CASSANDRA-17623
URL: https://issues.apache.org/jira/browse/CASSANDRA-17623
Project: Cassandra
Issue Type: Bug
Reporter: Doug Rohrer
CASSANDRA-7859 introduced the ability to use frozen collections as parts of
primary keys. This +requires+ all frozen maps to be persisted with their
entries sorted by the map keys. If the map is +not+ sorted correctly, it
becomes impossible to project all of the map values out of the map using the
map projection/selection syntax. For example, the select below would fail if
the map was not sorted correctly and the higher-valued key was persisted first:
{code:sql}
CREATE TABLE test.test (k text, c frozen>, PRIMARY KEY (k, c));
INSERT INTO test.test (k, c) VALUES ('key', {'z':'second_value',
'a':'first_value'});
SELECT k, c['a'] from test.test where k='key' -- c['a'] would return NULL here
{code}
Additionally, if you attempted to select just that row by using the complete
map value in a WHERE clause, which is also supported, it would return no rows
unless the map provided by the query processor just happened to be sorted the
same way as the persisted value.
However, there is a bug in Maps.java where we don't actually use a SortedMap in
{{Maps.Value#fromSerialized}}, which manifests if a client sends an unsorted
map as a bound parameter to a query on insert or select. In either case, the
map may not be sorted correctly, leading to either invalid data being persisted
to disk (in the INSERT case) or the query not being able to be
executed/returning 0 rows even though a row _should_ exist (SELECT).
This bug affects any usage of parameterized queries (tested with the DataStax
driver, and was originally discovered when using the CQLSSTableWriter code to
write data locally).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17483) WEBSITE - Homepage, Case Studies, and Blog edits and fixes
[ https://issues.apache.org/jira/browse/CASSANDRA-17483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diogenese Topper updated CASSANDRA-17483: - Test and Documentation Plan: Homepage * Formatting fix for Cassandra Users quotes Case Studies page * Add alt text for company logos * Add quotation marks to the Backblaze case study card * Fix "Read More" buttons on Backblaze, Kinetic Data, and Liquibase opening a new window *and* opening the case study page Blog * "Apache Cassandra 4.1 Features: Guardrails Framework" image replacement * "Inside Cassandra: An Interview with Project Contributor, Lorina Poland" image replacement was: Homepage * Formatting fix for Cassandra Users quotes Case Studies * Add alt text for company logos Summary: WEBSITE - Homepage, Case Studies, and Blog edits and fixes (was: WEBSITE - Homepage and Case Studies page edits) > WEBSITE - Homepage, Case Studies, and Blog edits and fixes > -- > > Key: CASSANDRA-17483 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17483 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Diogenese Topper >Priority: Normal > Fix For: NA > > > This ticket is to capture the work associated with updates to the Apache > Cassandra homepage, Case Studies page, and blog posts to address typos and > formatting issues. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17622) WEBSITE - Resources page update
[ https://issues.apache.org/jira/browse/CASSANDRA-17622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diogenese Topper updated CASSANDRA-17622: - Change Category: Semantic Complexity: Normal Impacts: Docs (was: None) Test and Documentation Plan: Update resources page with * > WEBSITE - Resources page update > --- > > Key: CASSANDRA-17622 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17622 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Diogenese Topper >Priority: Normal > > This ticket is to capture the work associated with updating the Apache > Cassandra Resources page with new resources and replacing outdated resources > with more recent and relevant ones. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17622) WEBSITE - Resources page update
Diogenese Topper created CASSANDRA-17622: Summary: WEBSITE - Resources page update Key: CASSANDRA-17622 URL: https://issues.apache.org/jira/browse/CASSANDRA-17622 Project: Cassandra Issue Type: Task Components: Documentation/Website Reporter: Diogenese Topper This ticket is to capture the work associated with updating the Apache Cassandra Resources page with new resources and replacing outdated resources with more recent and relevant ones. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17310) Test Failure: org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityV3XTest.testAvailability
[
https://issues.apache.org/jira/browse/CASSANDRA-17310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17310:
Fix Version/s: 4.1.x
4.1-beta
> Test Failure:
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityV3XTest.testAvailability
>
>
> Key: CASSANDRA-17310
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17310
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Josh McKenzie
>Priority: Normal
> Fix For: 4.1.x, 4.x, 4.1-beta
>
>
> https://ci-cassandra.apache.org/job/Cassandra-4.0/312/testReport/org.apache.cassandra.distributed.upgrade/MixedModeAvailabilityV3XTest/testAvailability/
> Failed 1 times in the last 5 runs. Flakiness: 25%, Stability: 80%
> Error Message
> Unexpected error while reading in case write-read consistency ONE-ALL with
> upgraded coordinator and 2 nodes down
> {code}
> Stacktrace
> junit.framework.AssertionFailedError: Unexpected error while reading in case
> write-read consistency ONE-ALL with upgraded coordinator and 2 nodes down
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase$Tester.test(MixedModeAvailabilityTestBase.java:142)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.lambda$testAvailability$2(MixedModeAvailabilityTestBase.java:91)
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:231)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailability(MixedModeAvailabilityTestBase.java:93)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailability(MixedModeAvailabilityTestBase.java:61)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailability(MixedModeAvailabilityTestBase.java:56)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityV3XTest.testAvailability(MixedModeAvailabilityV3XTest.java:33)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase$Tester.maybeFail(MixedModeAvailabilityTestBase.java:166)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase$Tester.test(MixedModeAvailabilityTestBase.java:134)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17291) Test Failure: unit test compression: testTokenGenerator_single_rack_or_single_rf
[
https://issues.apache.org/jira/browse/CASSANDRA-17291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17291:
Fix Version/s: 4.1.x
4.1-beta
> Test Failure: unit test compression:
> testTokenGenerator_single_rack_or_single_rf
>
>
> Key: CASSANDRA-17291
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17291
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 4.1.x, 4.x, 4.1-beta
>
>
> org.apache.cassandra.dht.tokenallocator.OfflineTokenAllocatorTest
> [https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/168/workflows/1d30a113-c14b-4cf4-a631-bedb9eb65762/jobs/1447]
> Looks like a pretty simple / straightforward timeout
> {code}
> junit.framework.AssertionFailedError: Timeout occurred. Please note the time
> in the report does not reflect the time until the timeout.
> at java.util.Vector.forEach(Vector.java:1277)
> at java.util.Vector.forEach(Vector.java:1277)
> at java.util.Vector.forEach(Vector.java:1277)
> at org.apache.cassandra.anttasks.TestHelper.execute(TestHelper.java:53)
> at java.util.Vector.forEach(Vector.java:1277)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17244) Fix org.apache.cassandra.distributed.test.trackwarnings.TombstoneCountWarningTest.failThresholdSinglePartition
[ https://issues.apache.org/jira/browse/CASSANDRA-17244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17244: Fix Version/s: 4.1.x 4.1-beta > Fix > org.apache.cassandra.distributed.test.trackwarnings.TombstoneCountWarningTest.failThresholdSinglePartition > -- > > Key: CASSANDRA-17244 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17244 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.1.x, 4.x, 4.1-beta > > > org.apache.cassandra.distributed.test.trackwarnings.TombstoneCountWarningTest.failThresholdSinglePartition > failed > [here|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1354/testReport/junit/org.apache.cassandra.distributed.test.trackwarnings/TombstoneCountWarningTest/failThresholdSinglePartition/] > I didn't find any other occurrences but seems to me legit failure. > CC [~dcapwell] as I think you were working on those and probably you will > make better assessment than me. :) -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17232) org.apache.cassandra.db.commitlog.GroupCommitLogTest tests failing on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17232:
Fix Version/s: 4.1.x
4.1-beta
> org.apache.cassandra.db.commitlog.GroupCommitLogTest tests failing on trunk
> ---
>
> Key: CASSANDRA-17232
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17232
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.1.x, 4.x, 4.1-beta
>
>
> I saw
> [here|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1344/testReport/junit/org.apache.cassandra.db.commitlog/GroupCommitLogTest/replayWithDiscard_3_/]
> and
> [here|https://ci-cassandra.apache.org/job/Cassandra-trunk/881/testReport/junit/org.apache.cassandra.db.commitlog/GroupCommitLogTest/replayWithDiscard_3__compression_3/]
> the same assertion failure:
>
> {code:java}
> org.apache.cassandra.db.commitlog.GroupCommitLogTest.replayWithDiscard[3]
> Error Message
> expected:<204> but was:<0>
> Stacktrace
> junit.framework.AssertionFailedError: expected:<204> but was:<0> at
> org.apache.cassandra.db.commitlog.CommitLogTest.replayWithDiscard(CommitLogTest.java:883)
> {code}
>
> Then I find that there are many other tests from GroupCommitLogTest failing
> with No such file found.
> Example:
> https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1344/
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17144) Fix test TestHintedHandoff#test_hintedhandoff_window
[
https://issues.apache.org/jira/browse/CASSANDRA-17144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17144:
Fix Version/s: 4.1.x
4.1-beta
> Fix test TestHintedHandoff#test_hintedhandoff_window
>
>
> Key: CASSANDRA-17144
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17144
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: David Capwell
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.1.x, 4.x, 4.1-beta
>
>
> This test fails from time to time (see butler
> https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/hintedhandoff_test/TestHintedHandoff/test_hintedhandoff_window)
> Example:
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/1101/workflows/7afb1c7e-8330-4ac6-963d-d7864282f2f3/jobs/7877
> {code}
> # Ensure second and third datasets are not present
> for x in range(100, 300):
> > query_c1c2(session, x, ConsistencyLevel.ONE,
> > tolerate_missing=True, must_be_missing=True)
> hintedhandoff_test.py:264:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> tools/data.py:44: in query_c1c2
> assertions.assert_length_equal(rows, 0)
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> object_with_length = [Row(c1='value1', c2='value2')], expected_length = 0
> def assert_length_equal(object_with_length, expected_length):
> """
> Assert an object has a specific length.
> @param object_with_length The object whose length will be checked
> @param expected_length The expected length of the object
>
> Examples:
> assert_length_equal(res, nb_counter)
> """
> assert len(object_with_length) == expected_length, \
> "Expected {} to have length {}, but instead is of length {}"\
> > .format(object_with_length, expected_length,
> > len(object_with_length))
> E AssertionError: Expected [Row(c1='value1', c2='value2')] to have
> length 0, but instead is of length 1
> tools/assertions.py:269: AssertionError
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16974) Fix org.apache.cassandra.distributed.test.UnableToParseClientMessageTest.badHeader[version=5/v5]
[
https://issues.apache.org/jira/browse/CASSANDRA-16974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-16974:
Fix Version/s: 4.1.x
4.1-beta
> Fix
> org.apache.cassandra.distributed.test.UnableToParseClientMessageTest.badHeader[version=5/v5]
>
>
> Key: CASSANDRA-16974
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16974
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.1.x, 4.x, 4.1-beta
>
>
> org.apache.cassandra.distributed.test.UnableToParseClientMessageTest.badHeader[version=5/v5
> is
> [failing|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1121/testReport/junit/org.apache.cassandra.distributed.test/UnableToParseClientMessageTest/badHeader_version_5_v5_/]
> on trunk
> {code:java}
> Error Message
> Expecting actual not to be empty
> Stacktrace
> junit.framework.AssertionFailedError:
> Expecting actual not to be empty
> at
> org.apache.cassandra.distributed.test.UnableToParseClientMessageTest.test(UnableToParseClientMessageTest.java:158)
> at
> org.apache.cassandra.distributed.test.UnableToParseClientMessageTest.badHeader(UnableToParseClientMessageTest.java:99)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16826) Fix flaky test consistent_bootstrap_test.py::TestBootstrapConsistency::test_consistent_reads_after_move
[
https://issues.apache.org/jira/browse/CASSANDRA-16826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-16826:
Fix Version/s: 4.1-beta
> Fix flaky test
> consistent_bootstrap_test.py::TestBootstrapConsistency::test_consistent_reads_after_move
> ---
>
> Key: CASSANDRA-16826
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16826
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: David Capwell
>Priority: Normal
> Fix For: 4.x, 4.1-beta
>
>
> consistent_bootstrap_test.py::TestBootstrapConsistency::test_consistent_reads_after_move
> can be flaky from time to time on less powerful environments due to
> timeouts; this can be improved by having retries for queries
> Here is the error I was seeing
> {code}
> self = 0x7fad988790f0>
> @pytest.mark.no_vnodes
> def test_consistent_reads_after_move(self):
> logger.debug("Creating a ring")
> cluster = self.cluster
> cluster.set_configuration_options(values={'hinted_handoff_enabled':
> False,
>
> 'write_request_timeout_in_ms': 6,
>
> 'read_request_timeout_in_ms': 6,
>
> 'dynamic_snitch_badness_threshold': 0.0})
> cluster.set_batch_commitlog(enabled=True)
>
> cluster.populate(3, tokens=[0, 2**48, 2**62]).start()
> node1, node2, node3 = cluster.nodelist()
>
> logger.debug("Set to talk to node 2")
> n2session = self.patient_cql_connection(node2)
> create_ks(n2session, 'ks', 2)
> create_c1c2_table(self, n2session)
>
> logger.debug("Generating some data for all nodes")
> insert_c1c2(n2session, keys=list(range(10, 20)),
> consistency=ConsistencyLevel.ALL)
>
> node1.flush()
> logger.debug("Taking down node1")
> node1.stop(wait_other_notice=True)
>
> logger.debug("Writing data to node2")
> insert_c1c2(n2session, keys=list(range(30, 1000)),
> consistency=ConsistencyLevel.ONE)
> node2.flush()
>
> logger.debug("Restart node1")
> node1.start()
>
> logger.debug("Move token on node3")
> node3.move(2)
>
> logger.debug("Checking that no data was lost")
> for n in range(10, 20):
> query_c1c2(n2session, n, ConsistencyLevel.ALL)
>
> for n in range(30, 1000):
> >query_c1c2(n2session, n, ConsistencyLevel.ALL)
> consistent_bootstrap_test.py:55:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> tools/data.py:34: in query_c1c2
> rows = list(session.execute(query))
> cassandra/cluster.py:2618: in cassandra.cluster.Session.execute
> ???
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> >???
> E cassandra.OperationTimedOut: errors={'127.0.0.1:9042': 'Client request
> timeout. See Session.execute[_async](timeout)'}, last_host=127.0.0.1:9042
> cassandra/cluster.py:4894: OperationTimedOut
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17549) jvm-dtest unhandled exceptions failing the test no longer work
[ https://issues.apache.org/jira/browse/CASSANDRA-17549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536294#comment-17536294 ] David Capwell commented on CASSANDRA-17549: --- few tests failed, going to update and try again. > jvm-dtest unhandled exceptions failing the test no longer work > -- > > Key: CASSANDRA-17549 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17549 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 4.1-beta > > > Seems that ([CASSANDRA-16925] CEP-10 Phase 1: Mockable Task Execution) > refactored and avoided using AbstractCluster.uncaughtException, this means > that the logic to detect unexpected exceptions to fail tests no longer works. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17213) CompactStorageUpgradeTest.compactStorageUpgradeTest fails w/OOM
[ https://issues.apache.org/jira/browse/CASSANDRA-17213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17213: Reviewers: Ekaterina Dimitrova > CompactStorageUpgradeTest.compactStorageUpgradeTest fails w/OOM > --- > > Key: CASSANDRA-17213 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17213 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Local Write-Read Paths >Reporter: Josh McKenzie >Assignee: Andres de la Peña >Priority: Normal > Fix For: 4.x > > > [https://ci-cassandra.apache.org/job/Cassandra-trunk/882/testReport/org.apache.cassandra.distributed.upgrade/CompactStorageUpgradeTest/compactStorageUpgradeTest/] > h3. Error Message > GC overhead limit exceeded > h3. Stacktrace > java.lang.OutOfMemoryError: GC overhead limit exceeded at > sun.net.www.ParseUtil.encodePath(ParseUtil.java:105) at > sun.misc.URLClassPath$JarLoader.checkResource(URLClassPath.java:969) at > sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:1056) at > sun.misc.URLClassPath.getResource(URLClassPath.java:249) at > java.net.URLClassLoader$1.run(URLClassLoader.java:366) at > java.net.URLClassLoader$1.run(URLClassLoader.java:363) at > java.security.AccessController.doPrivileged(Native Method) at > java.net.URLClassLoader.findClass(URLClassLoader.java:362) at > org.apache.cassandra.distributed.shared.InstanceClassLoader.findClass(InstanceClassLoader.java:140) > at > org.apache.cassandra.distributed.shared.InstanceClassLoader.loadClassInternal(InstanceClassLoader.java:123) > at > org.apache.cassandra.distributed.shared.InstanceClassLoader.loadClass(InstanceClassLoader.java:109) > at > org.codehaus.jackson.map.introspect.BasicClassIntrospector.(BasicClassIntrospector.java:62) > at org.codehaus.jackson.map.ObjectMapper.(ObjectMapper.java:188) at > org.apache.cassandra.utils.FBUtilities.(FBUtilities.java:74) at > org.apache.cassandra.distributed.impl.Instance.(Instance.java:144) at > org.apache.cassandra.distributed.impl.AbstractCluster$Wrapper$$Lambda$21599/1714755496.apply(Unknown > Source) at > org.apache.cassandra.distributed.impl.AbstractCluster$Wrapper.newInstance(AbstractCluster.java:247) > at > org.apache.cassandra.distributed.impl.AbstractCluster$Wrapper.(AbstractCluster.java:226) > at > org.apache.cassandra.distributed.UpgradeableCluster.newInstanceWrapper(UpgradeableCluster.java:46) > at > org.apache.cassandra.distributed.UpgradeableCluster.newInstanceWrapper(UpgradeableCluster.java:36) > at > org.apache.cassandra.distributed.impl.AbstractCluster.newInstanceWrapperInternal(AbstractCluster.java:515) > at > org.apache.cassandra.distributed.impl.AbstractCluster.(AbstractCluster.java:470) > at > org.apache.cassandra.distributed.UpgradeableCluster.(UpgradeableCluster.java:40) > at > org.apache.cassandra.distributed.UpgradeableCluster.(UpgradeableCluster.java:36) > at > org.apache.cassandra.distributed.UpgradeableCluster$Builder.lambda$new$0(UpgradeableCluster.java:86) > at > org.apache.cassandra.distributed.UpgradeableCluster$Builder$$Lambda$73/1631826609.newCluster(Unknown > Source) at > org.apache.cassandra.distributed.shared.AbstractBuilder.createWithoutStarting(AbstractBuilder.java:158) > at > org.apache.cassandra.distributed.shared.AbstractBuilder.start(AbstractBuilder.java:140) > at > org.apache.cassandra.distributed.UpgradeableCluster.create(UpgradeableCluster.java:73) > at > org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:223) > at > org.apache.cassandra.distributed.upgrade.CompactStorageUpgradeTest.compactStorageUpgradeTest(CompactStorageUpgradeTest.java:159) > h3. Standard Output > out of memory on output stream > > Appears consistent -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17213) CompactStorageUpgradeTest.compactStorageUpgradeTest fails w/OOM
[ https://issues.apache.org/jira/browse/CASSANDRA-17213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536252#comment-17536252 ] Ekaterina Dimitrova commented on CASSANDRA-17213: - I was also looking into this on the side, I was thinking it might be Circle config on different branches (didn't find difference). Also, we see the same behavior in Jenkins. Maybe some in-jvm difference I don't know. The solution SGTM > CompactStorageUpgradeTest.compactStorageUpgradeTest fails w/OOM > --- > > Key: CASSANDRA-17213 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17213 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Local Write-Read Paths >Reporter: Josh McKenzie >Assignee: Andres de la Peña >Priority: Normal > Fix For: 4.x > > > [https://ci-cassandra.apache.org/job/Cassandra-trunk/882/testReport/org.apache.cassandra.distributed.upgrade/CompactStorageUpgradeTest/compactStorageUpgradeTest/] > h3. Error Message > GC overhead limit exceeded > h3. Stacktrace > java.lang.OutOfMemoryError: GC overhead limit exceeded at > sun.net.www.ParseUtil.encodePath(ParseUtil.java:105) at > sun.misc.URLClassPath$JarLoader.checkResource(URLClassPath.java:969) at > sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:1056) at > sun.misc.URLClassPath.getResource(URLClassPath.java:249) at > java.net.URLClassLoader$1.run(URLClassLoader.java:366) at > java.net.URLClassLoader$1.run(URLClassLoader.java:363) at > java.security.AccessController.doPrivileged(Native Method) at > java.net.URLClassLoader.findClass(URLClassLoader.java:362) at > org.apache.cassandra.distributed.shared.InstanceClassLoader.findClass(InstanceClassLoader.java:140) > at > org.apache.cassandra.distributed.shared.InstanceClassLoader.loadClassInternal(InstanceClassLoader.java:123) > at > org.apache.cassandra.distributed.shared.InstanceClassLoader.loadClass(InstanceClassLoader.java:109) > at > org.codehaus.jackson.map.introspect.BasicClassIntrospector.(BasicClassIntrospector.java:62) > at org.codehaus.jackson.map.ObjectMapper.(ObjectMapper.java:188) at > org.apache.cassandra.utils.FBUtilities.(FBUtilities.java:74) at > org.apache.cassandra.distributed.impl.Instance.(Instance.java:144) at > org.apache.cassandra.distributed.impl.AbstractCluster$Wrapper$$Lambda$21599/1714755496.apply(Unknown > Source) at > org.apache.cassandra.distributed.impl.AbstractCluster$Wrapper.newInstance(AbstractCluster.java:247) > at > org.apache.cassandra.distributed.impl.AbstractCluster$Wrapper.(AbstractCluster.java:226) > at > org.apache.cassandra.distributed.UpgradeableCluster.newInstanceWrapper(UpgradeableCluster.java:46) > at > org.apache.cassandra.distributed.UpgradeableCluster.newInstanceWrapper(UpgradeableCluster.java:36) > at > org.apache.cassandra.distributed.impl.AbstractCluster.newInstanceWrapperInternal(AbstractCluster.java:515) > at > org.apache.cassandra.distributed.impl.AbstractCluster.(AbstractCluster.java:470) > at > org.apache.cassandra.distributed.UpgradeableCluster.(UpgradeableCluster.java:40) > at > org.apache.cassandra.distributed.UpgradeableCluster.(UpgradeableCluster.java:36) > at > org.apache.cassandra.distributed.UpgradeableCluster$Builder.lambda$new$0(UpgradeableCluster.java:86) > at > org.apache.cassandra.distributed.UpgradeableCluster$Builder$$Lambda$73/1631826609.newCluster(Unknown > Source) at > org.apache.cassandra.distributed.shared.AbstractBuilder.createWithoutStarting(AbstractBuilder.java:158) > at > org.apache.cassandra.distributed.shared.AbstractBuilder.start(AbstractBuilder.java:140) > at > org.apache.cassandra.distributed.UpgradeableCluster.create(UpgradeableCluster.java:73) > at > org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:223) > at > org.apache.cassandra.distributed.upgrade.CompactStorageUpgradeTest.compactStorageUpgradeTest(CompactStorageUpgradeTest.java:159) > h3. Standard Output > out of memory on output stream > > Appears consistent -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17213) CompactStorageUpgradeTest.compactStorageUpgradeTest fails w/OOM
[
https://issues.apache.org/jira/browse/CASSANDRA-17213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536235#comment-17536235
]
Andres de la Peña edited comment on CASSANDRA-17213 at 5/12/22 5:14 PM:
I have managed to repro the OOM on
[{{cassandra-4.0}}|https://app.circleci.com/pipelines/github/adelapena/cassandra/1546/workflows/2e1a0466-eb37-4c0d-be84-f549d05fd2a0]
with more repetitions, but not on
[{{cassandra-4.1}}|https://app.circleci.com/pipelines/github/adelapena/cassandra/1545/workflows/55c6d848-ca74-495f-a587-665ed1e70fcd].
I don't understand why there is that difference in test flakiness between
branches, but probably we should break the test class in all three branches.
was (Author: adelapena):
I have managed to repro the OOM on
[{{cassandra-4.0}}|https://app.circleci.com/pipelines/github/adelapena/cassandra/1546/workflows/2e1a0466-eb37-4c0d-be84-f549d05fd2a0]
with more repetitions, but not on
[{{cassandra-4.1}}|https://app.circleci.com/pipelines/github/adelapena/cassandra/1545/workflows/55c6d848-ca74-495f-a587-665ed1e70fcd].
I don't understand why there is that difference in test flakiness between
branches, but probably we should break the tests in all three branches.
> CompactStorageUpgradeTest.compactStorageUpgradeTest fails w/OOM
> ---
>
> Key: CASSANDRA-17213
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17213
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
>Reporter: Josh McKenzie
>Priority: Normal
> Fix For: 4.x
>
>
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/882/testReport/org.apache.cassandra.distributed.upgrade/CompactStorageUpgradeTest/compactStorageUpgradeTest/]
> h3. Error Message
> GC overhead limit exceeded
> h3. Stacktrace
> java.lang.OutOfMemoryError: GC overhead limit exceeded at
> sun.net.www.ParseUtil.encodePath(ParseUtil.java:105) at
> sun.misc.URLClassPath$JarLoader.checkResource(URLClassPath.java:969) at
> sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:1056) at
> sun.misc.URLClassPath.getResource(URLClassPath.java:249) at
> java.net.URLClassLoader$1.run(URLClassLoader.java:366) at
> java.net.URLClassLoader$1.run(URLClassLoader.java:363) at
> java.security.AccessController.doPrivileged(Native Method) at
> java.net.URLClassLoader.findClass(URLClassLoader.java:362) at
> org.apache.cassandra.distributed.shared.InstanceClassLoader.findClass(InstanceClassLoader.java:140)
> at
> org.apache.cassandra.distributed.shared.InstanceClassLoader.loadClassInternal(InstanceClassLoader.java:123)
> at
> org.apache.cassandra.distributed.shared.InstanceClassLoader.loadClass(InstanceClassLoader.java:109)
> at
> org.codehaus.jackson.map.introspect.BasicClassIntrospector.(BasicClassIntrospector.java:62)
> at org.codehaus.jackson.map.ObjectMapper.(ObjectMapper.java:188) at
> org.apache.cassandra.utils.FBUtilities.(FBUtilities.java:74) at
> org.apache.cassandra.distributed.impl.Instance.(Instance.java:144) at
> org.apache.cassandra.distributed.impl.AbstractCluster$Wrapper$$Lambda$21599/1714755496.apply(Unknown
> Source) at
> org.apache.cassandra.distributed.impl.AbstractCluster$Wrapper.newInstance(AbstractCluster.java:247)
> at
> org.apache.cassandra.distributed.impl.AbstractCluster$Wrapper.(AbstractCluster.java:226)
> at
> org.apache.cassandra.distributed.UpgradeableCluster.newInstanceWrapper(UpgradeableCluster.java:46)
> at
> org.apache.cassandra.distributed.UpgradeableCluster.newInstanceWrapper(UpgradeableCluster.java:36)
> at
> org.apache.cassandra.distributed.impl.AbstractCluster.newInstanceWrapperInternal(AbstractCluster.java:515)
> at
> org.apache.cassandra.distributed.impl.AbstractCluster.(AbstractCluster.java:470)
> at
> org.apache.cassandra.distributed.UpgradeableCluster.(UpgradeableCluster.java:40)
> at
> org.apache.cassandra.distributed.UpgradeableCluster.(UpgradeableCluster.java:36)
> at
> org.apache.cassandra.distributed.UpgradeableCluster$Builder.lambda$new$0(UpgradeableCluster.java:86)
> at
> org.apache.cassandra.distributed.UpgradeableCluster$Builder$$Lambda$73/1631826609.newCluster(Unknown
> Source) at
> org.apache.cassandra.distributed.shared.AbstractBuilder.createWithoutStarting(AbstractBuilder.java:158)
> at
> org.apache.cassandra.distributed.shared.AbstractBuilder.start(AbstractBuilder.java:140)
> at
> org.apache.cassandra.distributed.UpgradeableCluster.create(UpgradeableCluster.java:73)
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:223)
> at
> org.apache.cassandra.distributed.upgrade.CompactStorageUpgradeTest.compactStorageUpgradeTest(CompactStorageUpgradeTest.java:159)
> h3. Standard Output
> out of memory on output stream
>
>
[jira] [Assigned] (CASSANDRA-17213) CompactStorageUpgradeTest.compactStorageUpgradeTest fails w/OOM
[ https://issues.apache.org/jira/browse/CASSANDRA-17213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andres de la Peña reassigned CASSANDRA-17213: - Assignee: Andres de la Peña > CompactStorageUpgradeTest.compactStorageUpgradeTest fails w/OOM > --- > > Key: CASSANDRA-17213 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17213 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Local Write-Read Paths >Reporter: Josh McKenzie >Assignee: Andres de la Peña >Priority: Normal > Fix For: 4.x > > > [https://ci-cassandra.apache.org/job/Cassandra-trunk/882/testReport/org.apache.cassandra.distributed.upgrade/CompactStorageUpgradeTest/compactStorageUpgradeTest/] > h3. Error Message > GC overhead limit exceeded > h3. Stacktrace > java.lang.OutOfMemoryError: GC overhead limit exceeded at > sun.net.www.ParseUtil.encodePath(ParseUtil.java:105) at > sun.misc.URLClassPath$JarLoader.checkResource(URLClassPath.java:969) at > sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:1056) at > sun.misc.URLClassPath.getResource(URLClassPath.java:249) at > java.net.URLClassLoader$1.run(URLClassLoader.java:366) at > java.net.URLClassLoader$1.run(URLClassLoader.java:363) at > java.security.AccessController.doPrivileged(Native Method) at > java.net.URLClassLoader.findClass(URLClassLoader.java:362) at > org.apache.cassandra.distributed.shared.InstanceClassLoader.findClass(InstanceClassLoader.java:140) > at > org.apache.cassandra.distributed.shared.InstanceClassLoader.loadClassInternal(InstanceClassLoader.java:123) > at > org.apache.cassandra.distributed.shared.InstanceClassLoader.loadClass(InstanceClassLoader.java:109) > at > org.codehaus.jackson.map.introspect.BasicClassIntrospector.(BasicClassIntrospector.java:62) > at org.codehaus.jackson.map.ObjectMapper.(ObjectMapper.java:188) at > org.apache.cassandra.utils.FBUtilities.(FBUtilities.java:74) at > org.apache.cassandra.distributed.impl.Instance.(Instance.java:144) at > org.apache.cassandra.distributed.impl.AbstractCluster$Wrapper$$Lambda$21599/1714755496.apply(Unknown > Source) at > org.apache.cassandra.distributed.impl.AbstractCluster$Wrapper.newInstance(AbstractCluster.java:247) > at > org.apache.cassandra.distributed.impl.AbstractCluster$Wrapper.(AbstractCluster.java:226) > at > org.apache.cassandra.distributed.UpgradeableCluster.newInstanceWrapper(UpgradeableCluster.java:46) > at > org.apache.cassandra.distributed.UpgradeableCluster.newInstanceWrapper(UpgradeableCluster.java:36) > at > org.apache.cassandra.distributed.impl.AbstractCluster.newInstanceWrapperInternal(AbstractCluster.java:515) > at > org.apache.cassandra.distributed.impl.AbstractCluster.(AbstractCluster.java:470) > at > org.apache.cassandra.distributed.UpgradeableCluster.(UpgradeableCluster.java:40) > at > org.apache.cassandra.distributed.UpgradeableCluster.(UpgradeableCluster.java:36) > at > org.apache.cassandra.distributed.UpgradeableCluster$Builder.lambda$new$0(UpgradeableCluster.java:86) > at > org.apache.cassandra.distributed.UpgradeableCluster$Builder$$Lambda$73/1631826609.newCluster(Unknown > Source) at > org.apache.cassandra.distributed.shared.AbstractBuilder.createWithoutStarting(AbstractBuilder.java:158) > at > org.apache.cassandra.distributed.shared.AbstractBuilder.start(AbstractBuilder.java:140) > at > org.apache.cassandra.distributed.UpgradeableCluster.create(UpgradeableCluster.java:73) > at > org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:223) > at > org.apache.cassandra.distributed.upgrade.CompactStorageUpgradeTest.compactStorageUpgradeTest(CompactStorageUpgradeTest.java:159) > h3. Standard Output > out of memory on output stream > > Appears consistent -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17213) CompactStorageUpgradeTest.compactStorageUpgradeTest fails w/OOM
[
https://issues.apache.org/jira/browse/CASSANDRA-17213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536235#comment-17536235
]
Andres de la Peña commented on CASSANDRA-17213:
---
I have managed to repro the OOM on
[{{cassandra-4.0}}|https://app.circleci.com/pipelines/github/adelapena/cassandra/1546/workflows/2e1a0466-eb37-4c0d-be84-f549d05fd2a0]
with more repetitions, but not on
[{{cassandra-4.1}}|https://app.circleci.com/pipelines/github/adelapena/cassandra/1545/workflows/55c6d848-ca74-495f-a587-665ed1e70fcd].
I don't understand why there is that difference in test flakiness between
branches, but probably we should break the tests in all three branches.
> CompactStorageUpgradeTest.compactStorageUpgradeTest fails w/OOM
> ---
>
> Key: CASSANDRA-17213
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17213
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
>Reporter: Josh McKenzie
>Priority: Normal
> Fix For: 4.x
>
>
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/882/testReport/org.apache.cassandra.distributed.upgrade/CompactStorageUpgradeTest/compactStorageUpgradeTest/]
> h3. Error Message
> GC overhead limit exceeded
> h3. Stacktrace
> java.lang.OutOfMemoryError: GC overhead limit exceeded at
> sun.net.www.ParseUtil.encodePath(ParseUtil.java:105) at
> sun.misc.URLClassPath$JarLoader.checkResource(URLClassPath.java:969) at
> sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:1056) at
> sun.misc.URLClassPath.getResource(URLClassPath.java:249) at
> java.net.URLClassLoader$1.run(URLClassLoader.java:366) at
> java.net.URLClassLoader$1.run(URLClassLoader.java:363) at
> java.security.AccessController.doPrivileged(Native Method) at
> java.net.URLClassLoader.findClass(URLClassLoader.java:362) at
> org.apache.cassandra.distributed.shared.InstanceClassLoader.findClass(InstanceClassLoader.java:140)
> at
> org.apache.cassandra.distributed.shared.InstanceClassLoader.loadClassInternal(InstanceClassLoader.java:123)
> at
> org.apache.cassandra.distributed.shared.InstanceClassLoader.loadClass(InstanceClassLoader.java:109)
> at
> org.codehaus.jackson.map.introspect.BasicClassIntrospector.(BasicClassIntrospector.java:62)
> at org.codehaus.jackson.map.ObjectMapper.(ObjectMapper.java:188) at
> org.apache.cassandra.utils.FBUtilities.(FBUtilities.java:74) at
> org.apache.cassandra.distributed.impl.Instance.(Instance.java:144) at
> org.apache.cassandra.distributed.impl.AbstractCluster$Wrapper$$Lambda$21599/1714755496.apply(Unknown
> Source) at
> org.apache.cassandra.distributed.impl.AbstractCluster$Wrapper.newInstance(AbstractCluster.java:247)
> at
> org.apache.cassandra.distributed.impl.AbstractCluster$Wrapper.(AbstractCluster.java:226)
> at
> org.apache.cassandra.distributed.UpgradeableCluster.newInstanceWrapper(UpgradeableCluster.java:46)
> at
> org.apache.cassandra.distributed.UpgradeableCluster.newInstanceWrapper(UpgradeableCluster.java:36)
> at
> org.apache.cassandra.distributed.impl.AbstractCluster.newInstanceWrapperInternal(AbstractCluster.java:515)
> at
> org.apache.cassandra.distributed.impl.AbstractCluster.(AbstractCluster.java:470)
> at
> org.apache.cassandra.distributed.UpgradeableCluster.(UpgradeableCluster.java:40)
> at
> org.apache.cassandra.distributed.UpgradeableCluster.(UpgradeableCluster.java:36)
> at
> org.apache.cassandra.distributed.UpgradeableCluster$Builder.lambda$new$0(UpgradeableCluster.java:86)
> at
> org.apache.cassandra.distributed.UpgradeableCluster$Builder$$Lambda$73/1631826609.newCluster(Unknown
> Source) at
> org.apache.cassandra.distributed.shared.AbstractBuilder.createWithoutStarting(AbstractBuilder.java:158)
> at
> org.apache.cassandra.distributed.shared.AbstractBuilder.start(AbstractBuilder.java:140)
> at
> org.apache.cassandra.distributed.UpgradeableCluster.create(UpgradeableCluster.java:73)
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:223)
> at
> org.apache.cassandra.distributed.upgrade.CompactStorageUpgradeTest.compactStorageUpgradeTest(CompactStorageUpgradeTest.java:159)
> h3. Standard Output
> out of memory on output stream
>
> Appears consistent
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14113) AssertionError while trying to upgrade 2.2.11 -> 3.11.1
[
https://issues.apache.org/jira/browse/CASSANDRA-14113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536209#comment-17536209
]
Brandon Williams commented on CASSANDRA-14113:
--
I've started a circle run here:
https://app.circleci.com/pipelines/github/driftx/cassandra/478/workflows/ffdea584-a280-4d07-932b-36cf5e1dd6b8
> AssertionError while trying to upgrade 2.2.11 -> 3.11.1
> ---
>
> Key: CASSANDRA-14113
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14113
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core
> Environment: Tables have been created in 2.2.11 using thrift and have
> supercolumns
>Reporter: Guillaume Herail
>Assignee: Marten Kenbeek
>Priority: Normal
> Labels: supercolumns
> Attachments: 14113-3.0.txt, data.tar.gz
>
>
> We're trying to upgrade a test cluster from Cassandra 2.2.11 to Cassandra
> 3.11.1. The tables have been created using thrift and have supercolumns. When
> I try to run {{nodetool upgradesstables}} I get the following:
> {noformat}error: null
> -- StackTrace --
> java.lang.AssertionError
> at org.apache.cassandra.db.rows.BufferCell.(BufferCell.java:42)
> at
> org.apache.cassandra.db.LegacyLayout$CellGrouper.addCell(LegacyLayout.java:1242)
> at
> org.apache.cassandra.db.LegacyLayout$CellGrouper.addAtom(LegacyLayout.java:1185)
> at
> org.apache.cassandra.db.UnfilteredDeserializer$OldFormatDeserializer$UnfilteredIterator.readRow(UnfilteredDeserializer.java:498)
> at
> org.apache.cassandra.db.UnfilteredDeserializer$OldFormatDeserializer$UnfilteredIterator.hasNext(UnfilteredDeserializer.java:472)
> at
> org.apache.cassandra.db.UnfilteredDeserializer$OldFormatDeserializer.hasNext(UnfilteredDeserializer.java:306)
> at
> org.apache.cassandra.io.sstable.SSTableSimpleIterator$OldFormatIterator.computeNext(SSTableSimpleIterator.java:188)
> at
> org.apache.cassandra.io.sstable.SSTableSimpleIterator$OldFormatIterator.computeNext(SSTableSimpleIterator.java:140)
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> at
> org.apache.cassandra.io.sstable.SSTableIdentityIterator.hasNext(SSTableIdentityIterator.java:122)
> at
> org.apache.cassandra.db.rows.LazilyInitializedUnfilteredRowIterator.computeNext(LazilyInitializedUnfilteredRowIterator.java:100)
> at
> org.apache.cassandra.db.rows.LazilyInitializedUnfilteredRowIterator.computeNext(LazilyInitializedUnfilteredRowIterator.java:32)
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> at
> org.apache.cassandra.utils.MergeIterator$TrivialOneToOne.computeNext(MergeIterator.java:484)
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:499)
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:359)
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> at org.apache.cassandra.db.transform.BaseRows.hasNext(BaseRows.java:133)
> at
> org.apache.cassandra.db.transform.UnfilteredRows.isEmpty(UnfilteredRows.java:74)
> at
> org.apache.cassandra.db.partitions.PurgeFunction.applyToPartition(PurgeFunction.java:75)
> at
> org.apache.cassandra.db.partitions.PurgeFunction.applyToPartition(PurgeFunction.java:26)
> at
> org.apache.cassandra.db.transform.BasePartitions.hasNext(BasePartitions.java:96)
> at
> org.apache.cassandra.db.compaction.CompactionIterator.hasNext(CompactionIterator.java:233)
> at
> org.apache.cassandra.db.compaction.CompactionTask.runMayThrow(CompactionTask.java:196)
> at
> org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
> at
> org.apache.cassandra.db.compaction.CompactionTask.executeInternal(CompactionTask.java:85)
> at
> org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(AbstractCompactionTask.java:61)
> at
> org.apache.cassandra.db.compaction.CompactionManager$5.execute(CompactionManager.java:428)
> at
> org.apache.cassandra.db.compaction.CompactionManager$2.call(CompactionManager.java:315)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:81)
> at
[jira] [Updated] (CASSANDRA-17565) Fix test_parallel_upgrade_with_internode_ssl
[ https://issues.apache.org/jira/browse/CASSANDRA-17565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-17565: - Fix Version/s: 4.1.x 4.1-beta (was: 4.x) > Fix test_parallel_upgrade_with_internode_ssl > > > Key: CASSANDRA-17565 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17565 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Brandon Williams >Priority: Normal > Fix For: 4.1.x, 4.1-beta > > > While working on CASSANDRA-17341 I hit this flaky test, very rarely failing > but it is failing on trunk. > More info in this CI run: > https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1563/workflows/61bda0b7-f699-4897-877f-c7d523a03127/jobs/10318 -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17565) Fix test_parallel_upgrade_with_internode_ssl
[ https://issues.apache.org/jira/browse/CASSANDRA-17565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536206#comment-17536206 ] Brandon Williams commented on CASSANDRA-17565: -- No, this breaks the handleCorruptionOfLargeMessageFrame test. I'll come back to this at some point and investigate. > Fix test_parallel_upgrade_with_internode_ssl > > > Key: CASSANDRA-17565 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17565 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Brandon Williams >Priority: Normal > Fix For: 4.x > > > While working on CASSANDRA-17341 I hit this flaky test, very rarely failing > but it is failing on trunk. > More info in this CI run: > https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1563/workflows/61bda0b7-f699-4897-877f-c7d523a03127/jobs/10318 -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14113) AssertionError while trying to upgrade 2.2.11 -> 3.11.1
[
https://issues.apache.org/jira/browse/CASSANDRA-14113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536195#comment-17536195
]
Marten Kenbeek commented on CASSANDRA-14113:
Ah sorry, that was my first idea for a patch, but it didn't handle sparse
tables correctly. The latest patch is in an attachment to this issue, or you
can find it at [https://github.com/knbk/cassandra/tree/cassandra-14133/3.11] if
that's easier. That one passed the unit test suite when I ran it locally. I
think the issues were in the upgrade tests.
> AssertionError while trying to upgrade 2.2.11 -> 3.11.1
> ---
>
> Key: CASSANDRA-14113
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14113
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core
> Environment: Tables have been created in 2.2.11 using thrift and have
> supercolumns
>Reporter: Guillaume Herail
>Assignee: Marten Kenbeek
>Priority: Normal
> Labels: supercolumns
> Attachments: 14113-3.0.txt, data.tar.gz
>
>
> We're trying to upgrade a test cluster from Cassandra 2.2.11 to Cassandra
> 3.11.1. The tables have been created using thrift and have supercolumns. When
> I try to run {{nodetool upgradesstables}} I get the following:
> {noformat}error: null
> -- StackTrace --
> java.lang.AssertionError
> at org.apache.cassandra.db.rows.BufferCell.(BufferCell.java:42)
> at
> org.apache.cassandra.db.LegacyLayout$CellGrouper.addCell(LegacyLayout.java:1242)
> at
> org.apache.cassandra.db.LegacyLayout$CellGrouper.addAtom(LegacyLayout.java:1185)
> at
> org.apache.cassandra.db.UnfilteredDeserializer$OldFormatDeserializer$UnfilteredIterator.readRow(UnfilteredDeserializer.java:498)
> at
> org.apache.cassandra.db.UnfilteredDeserializer$OldFormatDeserializer$UnfilteredIterator.hasNext(UnfilteredDeserializer.java:472)
> at
> org.apache.cassandra.db.UnfilteredDeserializer$OldFormatDeserializer.hasNext(UnfilteredDeserializer.java:306)
> at
> org.apache.cassandra.io.sstable.SSTableSimpleIterator$OldFormatIterator.computeNext(SSTableSimpleIterator.java:188)
> at
> org.apache.cassandra.io.sstable.SSTableSimpleIterator$OldFormatIterator.computeNext(SSTableSimpleIterator.java:140)
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> at
> org.apache.cassandra.io.sstable.SSTableIdentityIterator.hasNext(SSTableIdentityIterator.java:122)
> at
> org.apache.cassandra.db.rows.LazilyInitializedUnfilteredRowIterator.computeNext(LazilyInitializedUnfilteredRowIterator.java:100)
> at
> org.apache.cassandra.db.rows.LazilyInitializedUnfilteredRowIterator.computeNext(LazilyInitializedUnfilteredRowIterator.java:32)
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> at
> org.apache.cassandra.utils.MergeIterator$TrivialOneToOne.computeNext(MergeIterator.java:484)
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:499)
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:359)
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> at org.apache.cassandra.db.transform.BaseRows.hasNext(BaseRows.java:133)
> at
> org.apache.cassandra.db.transform.UnfilteredRows.isEmpty(UnfilteredRows.java:74)
> at
> org.apache.cassandra.db.partitions.PurgeFunction.applyToPartition(PurgeFunction.java:75)
> at
> org.apache.cassandra.db.partitions.PurgeFunction.applyToPartition(PurgeFunction.java:26)
> at
> org.apache.cassandra.db.transform.BasePartitions.hasNext(BasePartitions.java:96)
> at
> org.apache.cassandra.db.compaction.CompactionIterator.hasNext(CompactionIterator.java:233)
> at
> org.apache.cassandra.db.compaction.CompactionTask.runMayThrow(CompactionTask.java:196)
> at
> org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
> at
> org.apache.cassandra.db.compaction.CompactionTask.executeInternal(CompactionTask.java:85)
> at
> org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(AbstractCompactionTask.java:61)
> at
> org.apache.cassandra.db.compaction.CompactionManager$5.execute(CompactionManager.java:428)
> at
> org.apache.cassandra.db.compaction.CompactionManager$2.call(CompactionManager.java:315)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
>
[jira] [Updated] (CASSANDRA-17420) Test Failure: org.apache.cassandra.cql3.validation.miscellaneous.CrcCheckChanceTest.testChangingCrcCheckChanceOldFormat
[
https://issues.apache.org/jira/browse/CASSANDRA-17420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17420:
Fix Version/s: 4.1-beta
> Test Failure:
> org.apache.cassandra.cql3.validation.miscellaneous.CrcCheckChanceTest.testChangingCrcCheckChanceOldFormat
> ---
>
> Key: CASSANDRA-17420
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17420
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Priority: Normal
> Fix For: 4.x, 4.1-beta
>
>
> https://ci-cassandra.apache.org/job/Cassandra-trunk/992/testReport/org.apache.cassandra.cql3.validation.miscellaneous/CrcCheckChanceTest/testChangingCrcCheckChanceOldFormat_2/
> bq. Error setting schema for test (query was: CREATE KEYSPACE IF NOT EXISTS
> cql_test_keyspace WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': '1'})
> 1 failure
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17469) Test Failure: org.apache.cassandra.db.commitlog.GroupCommitLogTest
[
https://issues.apache.org/jira/browse/CASSANDRA-17469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17469:
Complexity: Normal
Discovered By: User Report
Fix Version/s: 4.1-beta
Severity: Normal
Status: Open (was: Triage Needed)
> Test Failure: org.apache.cassandra.db.commitlog.GroupCommitLogTest
> --
>
> Key: CASSANDRA-17469
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17469
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.x, 4.1-beta
>
>
> Intermitent failures in
> {{{}org.apache.cassandra.db.commitlog.GroupCommitLogTest{}}}:
> *
> [testTruncateWithoutSnapshotNonDurable|https://ci-cassandra.apache.org/job/Cassandra-trunk/1024/testReport/org.apache.cassandra.db.commitlog/GroupCommitLogTest/testTruncateWithoutSnapshotNonDurable_4__cdc_2/]
> *
> [testRecoveryWithEmptyLog|https://ci-cassandra.apache.org/job/Cassandra-trunk/1024/testReport/org.apache.cassandra.db.commitlog/GroupCommitLogTest/testTruncateWithoutSnapshotNonDurable_4__cdc_2/]
> *
> [testOutOfOrderLogDiscardWithCompaction|https://ci-cassandra.apache.org/job/Cassandra-trunk/1024/testReport/org.apache.cassandra.db.commitlog/GroupCommitLogTest/testTruncateWithoutSnapshotNonDurable_4__cdc_2/]
> *
> [testExceedRecordLimitWithMultiplePartitions|https://ci-cassandra.apache.org/job/Cassandra-trunk/1024/testReport/org.apache.cassandra.db.commitlog/GroupCommitLogTest/testExceedRecordLimitWithMultiplePartitions_5__cdc_2/]
> *
> [testRecoveryWithShortMutationSize|https://ci-cassandra.apache.org/job/Cassandra-trunk/1024/testReport/org.apache.cassandra.db.commitlog/GroupCommitLogTest/testRecoveryWithShortMutationSize_4__cdc_2/]
> {code:java}
> Failed 2 times in the last 11 runs. Flakiness: 30%, Stability: 81%
> Stacktrace
> java.io.UncheckedIOException
> at
> org.apache.cassandra.io.util.PathUtils.propagateUnchecked(PathUtils.java:768)
> at
> org.apache.cassandra.io.util.PathUtils.propagateUnchecked(PathUtils.java:753)
> at org.apache.cassandra.io.util.PathUtils.delete(PathUtils.java:255)
> at org.apache.cassandra.io.util.PathUtils.delete(PathUtils.java:297)
> at org.apache.cassandra.io.util.PathUtils.delete(PathUtils.java:304)
> at org.apache.cassandra.io.util.File.delete(File.java:158)
> at org.apache.cassandra.io.util.File.delete(File.java:167)
> at
> org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDC.discard(CommitLogSegmentManagerCDC.java:75)
> at
> org.apache.cassandra.db.commitlog.AbstractCommitLogSegmentManager.closeAndDeleteSegmentUnsafe(AbstractCommitLogSegmentManager.java:479)
> at
> org.apache.cassandra.db.commitlog.AbstractCommitLogSegmentManager.stopUnsafe(AbstractCommitLogSegmentManager.java:452)
> at
> org.apache.cassandra.db.commitlog.CommitLog.stopUnsafe(CommitLog.java:504)
> at
> org.apache.cassandra.db.commitlog.CommitLog.resetUnsafe(CommitLog.java:470)
> at
> org.apache.cassandra.db.commitlog.CommitLogTest.beforeTest(CommitLogTest.java:184)
> at jdk.internal.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Caused by: java.nio.file.NoSuchFileException:
> build/test/cassandra/commitlog/CommitLog-7-1647704321215.log
> at
> java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:116)
> at
> java.base/sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:249)
> at
> java.base/sun.nio.fs.AbstractFileSystemProvider.delete(AbstractFileSystemProvider.java:105)
> at java.base/java.nio.file.Files.delete(Files.java:1142)
> at org.apache.cassandra.io.util.PathUtils.delete(PathUtils.java:250)
> Standard Output
> DEBUG [main] 2022-03-19 15:41:04,702 InternalLoggerFactory.java:63 - Using
> SLF4J as the default logging framework
> DEBUG [main] 2022-03-19 15:41:04,712 InternalThreadLocalMap.java:83 -
> -Dio.netty.threadLocalMap.stringBuilder.initialSize: 1024
> DEBUG [main] 2022-03-19 15:41:04,712 InternalThreadLocalMap.java:86 -
> -Dio.netty.threadLocalMap.stringBuilder.maxSize: 4096
> INFO [main] 2022-03-19 15:41:04,713 CipherFactory.java:68 - initializing
> CipherFactory
> INFO [main] 2022-03-19 15:41:04,713 JKSKeyPro
> ...[truncated 1879728 chars]...
> tLog-7-1647704466908.log
> INFO [main] 2022-03-19 15:41:26,711 CommitLog.java:175 - No commitlog files
>
[jira] [Updated] (CASSANDRA-17488) Intermittent failure on org.apache.cassandra.distributed.test.UnableToParseClientMessageTest.badHeader
[
https://issues.apache.org/jira/browse/CASSANDRA-17488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17488:
Fix Version/s: (was: 4.1-beta)
> Intermittent failure on
> org.apache.cassandra.distributed.test.UnableToParseClientMessageTest.badHeader
> --
>
> Key: CASSANDRA-17488
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17488
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.0.x, 4.x
>
>
> Intermittent failure on
> {{{}org.apache.cassandra.distributed.test.UnableToParseClientMessageTest.badHeader{}}}:
> [https://ci-cassandra.apache.org/job/Cassandra-4.0/363/testReport/org.apache.cassandra.distributed.test/UnableToParseClientMessageTest/badHeader_version_4_v4__2/]
> {code:java}
> Error Message
> Expecting actual not to be empty
> Stacktrace
> junit.framework.AssertionFailedError:
> Expecting actual not to be empty
> at
> org.apache.cassandra.distributed.test.UnableToParseClientMessageTest.test(UnableToParseClientMessageTest.java:159)
> at
> org.apache.cassandra.distributed.test.UnableToParseClientMessageTest.badHeader(UnableToParseClientMessageTest.java:100)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Standard Output
> INFO [main] 2022-03-22 12:45:37,371 YamlConfigurationLoader.java:97 -
> Configuration location:
> file:/home/cassandra/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2022-03-22 12:45:37,375 YamlConfigurationLoader.java:116
> - Loading settings from
> file:/home/cassandra/cassandra/test/conf/cassandra.yaml
> INFO [main] 2022-03-22 12:45:37,661 Config.java:706 - Node
> configuration:[allocate_tokens_for_keyspace=null;
> allocate_tokens_for_local_replication_factor=null; allow_extra_insec
> ...[truncated 127387 chars]...
> 55,015 StorageService.java:2784 - Node /127.0.0.1:7012 state jump to shutdown
> DEBUG [node1_isolatedExecutor:3] node1 2022-03-22 12:45:55,016
> StorageService.java:2781 - Node /127.0.0.1:7012 state shutdown, token
> [9223372036854775807]
> INFO [node1_isolatedExecutor:3] node1 2022-03-22 12:45:55,017
> StorageService.java:2784 - Node /127.0.0.1:7012 state jump to shutdown
> INFO [node1_isolatedExecutor:14] node1 2022-03-22 12:45:57,023
> MessagingService.java:441 - Waiting for messaging service to quiesce
> {code}
> This failure can also be reproduced on CircleCI test multiplexer for trunk:
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/1442/workflows/b46d2561-1a76-4c75-9f19-9075f42750fb/jobs/14724]
> There is only one recent failure on Jenkins, and the multiplexer only hits it
> once in 500 runs, so flakiness seems very low.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17488) Intermittent failure on org.apache.cassandra.distributed.test.UnableToParseClientMessageTest.badHeader
[
https://issues.apache.org/jira/browse/CASSANDRA-17488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17488:
Fix Version/s: 4.1-beta
> Intermittent failure on
> org.apache.cassandra.distributed.test.UnableToParseClientMessageTest.badHeader
> --
>
> Key: CASSANDRA-17488
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17488
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.0.x, 4.x, 4.1-beta
>
>
> Intermittent failure on
> {{{}org.apache.cassandra.distributed.test.UnableToParseClientMessageTest.badHeader{}}}:
> [https://ci-cassandra.apache.org/job/Cassandra-4.0/363/testReport/org.apache.cassandra.distributed.test/UnableToParseClientMessageTest/badHeader_version_4_v4__2/]
> {code:java}
> Error Message
> Expecting actual not to be empty
> Stacktrace
> junit.framework.AssertionFailedError:
> Expecting actual not to be empty
> at
> org.apache.cassandra.distributed.test.UnableToParseClientMessageTest.test(UnableToParseClientMessageTest.java:159)
> at
> org.apache.cassandra.distributed.test.UnableToParseClientMessageTest.badHeader(UnableToParseClientMessageTest.java:100)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Standard Output
> INFO [main] 2022-03-22 12:45:37,371 YamlConfigurationLoader.java:97 -
> Configuration location:
> file:/home/cassandra/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2022-03-22 12:45:37,375 YamlConfigurationLoader.java:116
> - Loading settings from
> file:/home/cassandra/cassandra/test/conf/cassandra.yaml
> INFO [main] 2022-03-22 12:45:37,661 Config.java:706 - Node
> configuration:[allocate_tokens_for_keyspace=null;
> allocate_tokens_for_local_replication_factor=null; allow_extra_insec
> ...[truncated 127387 chars]...
> 55,015 StorageService.java:2784 - Node /127.0.0.1:7012 state jump to shutdown
> DEBUG [node1_isolatedExecutor:3] node1 2022-03-22 12:45:55,016
> StorageService.java:2781 - Node /127.0.0.1:7012 state shutdown, token
> [9223372036854775807]
> INFO [node1_isolatedExecutor:3] node1 2022-03-22 12:45:55,017
> StorageService.java:2784 - Node /127.0.0.1:7012 state jump to shutdown
> INFO [node1_isolatedExecutor:14] node1 2022-03-22 12:45:57,023
> MessagingService.java:441 - Waiting for messaging service to quiesce
> {code}
> This failure can also be reproduced on CircleCI test multiplexer for trunk:
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/1442/workflows/b46d2561-1a76-4c75-9f19-9075f42750fb/jobs/14724]
> There is only one recent failure on Jenkins, and the multiplexer only hits it
> once in 500 runs, so flakiness seems very low.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17488) Intermittent failure on org.apache.cassandra.distributed.test.UnableToParseClientMessageTest.badHeader
[
https://issues.apache.org/jira/browse/CASSANDRA-17488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17488:
Complexity: Normal
Discovered By: User Report
Severity: Normal
Status: Open (was: Triage Needed)
> Intermittent failure on
> org.apache.cassandra.distributed.test.UnableToParseClientMessageTest.badHeader
> --
>
> Key: CASSANDRA-17488
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17488
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.0.x, 4.x
>
>
> Intermittent failure on
> {{{}org.apache.cassandra.distributed.test.UnableToParseClientMessageTest.badHeader{}}}:
> [https://ci-cassandra.apache.org/job/Cassandra-4.0/363/testReport/org.apache.cassandra.distributed.test/UnableToParseClientMessageTest/badHeader_version_4_v4__2/]
> {code:java}
> Error Message
> Expecting actual not to be empty
> Stacktrace
> junit.framework.AssertionFailedError:
> Expecting actual not to be empty
> at
> org.apache.cassandra.distributed.test.UnableToParseClientMessageTest.test(UnableToParseClientMessageTest.java:159)
> at
> org.apache.cassandra.distributed.test.UnableToParseClientMessageTest.badHeader(UnableToParseClientMessageTest.java:100)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Standard Output
> INFO [main] 2022-03-22 12:45:37,371 YamlConfigurationLoader.java:97 -
> Configuration location:
> file:/home/cassandra/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2022-03-22 12:45:37,375 YamlConfigurationLoader.java:116
> - Loading settings from
> file:/home/cassandra/cassandra/test/conf/cassandra.yaml
> INFO [main] 2022-03-22 12:45:37,661 Config.java:706 - Node
> configuration:[allocate_tokens_for_keyspace=null;
> allocate_tokens_for_local_replication_factor=null; allow_extra_insec
> ...[truncated 127387 chars]...
> 55,015 StorageService.java:2784 - Node /127.0.0.1:7012 state jump to shutdown
> DEBUG [node1_isolatedExecutor:3] node1 2022-03-22 12:45:55,016
> StorageService.java:2781 - Node /127.0.0.1:7012 state shutdown, token
> [9223372036854775807]
> INFO [node1_isolatedExecutor:3] node1 2022-03-22 12:45:55,017
> StorageService.java:2784 - Node /127.0.0.1:7012 state jump to shutdown
> INFO [node1_isolatedExecutor:14] node1 2022-03-22 12:45:57,023
> MessagingService.java:441 - Waiting for messaging service to quiesce
> {code}
> This failure can also be reproduced on CircleCI test multiplexer for trunk:
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/1442/workflows/b46d2561-1a76-4c75-9f19-9075f42750fb/jobs/14724]
> There is only one recent failure on Jenkins, and the multiplexer only hits it
> once in 500 runs, so flakiness seems very low.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17553) NPE in RangeTombstoneTest.overlappingRangeTest-compression
[
https://issues.apache.org/jira/browse/CASSANDRA-17553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17553:
Fix Version/s: 4.1.x
4.1-beta
> NPE in RangeTombstoneTest.overlappingRangeTest-compression
> --
>
> Key: CASSANDRA-17553
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17553
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Caleb Rackliffe
>Priority: Normal
> Fix For: 4.1.x, 4.x, 4.1-beta
>
>
> The trace looks something like this on trunk:
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.cassandra.db.RangeTombstoneTest.overlappingRangeTest(RangeTombstoneTest.java:437)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {noformat}
> See
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1078/testReport/org.apache.cassandra.db/RangeTombstoneTest/overlappingRangeTest_compression/
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17565) Fix test_parallel_upgrade_with_internode_ssl
[ https://issues.apache.org/jira/browse/CASSANDRA-17565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536182#comment-17536182 ] Ekaterina Dimitrova commented on CASSANDRA-17565: - Triaging and found this one, should we move it to patch available? > Fix test_parallel_upgrade_with_internode_ssl > > > Key: CASSANDRA-17565 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17565 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Brandon Williams >Priority: Normal > Fix For: 4.x > > > While working on CASSANDRA-17341 I hit this flaky test, very rarely failing > but it is failing on trunk. > More info in this CI run: > https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1563/workflows/61bda0b7-f699-4897-877f-c7d523a03127/jobs/10318 -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17566) Fix flaky test - org.apache.cassandra.distributed.test.repair.ForceRepairTest.force
[
https://issues.apache.org/jira/browse/CASSANDRA-17566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17566:
Fix Version/s: 4.1-beta
> Fix flaky test -
> org.apache.cassandra.distributed.test.repair.ForceRepairTest.force
> ---
>
> Key: CASSANDRA-17566
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17566
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.x, 4.1-beta
>
>
> Seen on jenkins here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1083/testReport/org.apache.cassandra.distributed.test.repair/ForceRepairTest/force_2/]
>
> and circle here:
> https://app.circleci.com/pipelines/github/driftx/cassandra/440/workflows/42f936c7-2ede-4fbf-957c-5fb4e461dd90/jobs/5160/tests#failed-test-1
> {noformat}
> junit.framework.AssertionFailedError: nodetool command [repair,
> distributed_test_keyspace, --force, --full] was not successful
> stdout:
> [2022-04-20 15:11:01,402] Starting repair command #2
> (1701a090-c0bc-11ec-9898-07c796ce6a49), repairing keyspace
> distributed_test_keyspace with repair options (parallelism: parallel, primary
> range: false, incremental: false, job threads: 1, ColumnFamilies: [],
> dataCenters: [], hosts: [], previewKind: NONE, # of ranges: 3, pull repair:
> false, force repair: true, optimise streams: false, ignore unreplicated
> keyspaces: false, repairPaxos: true, paxosOnly: false)
> [2022-04-20 15:11:11,406] Repair command #2 failed with error Did not get
> replies from all endpoints.
> [2022-04-20 15:11:11,408] Repair command #2 finished with error
> stderr:
> error: Repair job has failed with the error message: Repair command #2 failed
> with error Did not get replies from all endpoints.. Check the logs on the
> repair participants for further details
> -- StackTrace --
> java.lang.RuntimeException: Repair job has failed with the error message:
> Repair command #2 failed with error Did not get replies from all endpoints..
> Check the logs on the repair participants for further details
> at
> org.apache.cassandra.tools.RepairRunner.progress(RepairRunner.java:137)
> at
> org.apache.cassandra.utils.progress.jmx.JMXNotificationProgressListener.handleNotification(JMXNotificationProgressListener.java:77)
> at
> javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:275)
> at
> javax.management.NotificationBroadcasterSupport$SendNotifJob.run(NotificationBroadcasterSupport.java:352)
> at
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:124)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17572) Race condition when IP address changes for a node can cause reads/writes to route to the wrong node
[ https://issues.apache.org/jira/browse/CASSANDRA-17572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17572: Fix Version/s: 3.0.x 3.11.x > Race condition when IP address changes for a node can cause reads/writes to > route to the wrong node > --- > > Key: CASSANDRA-17572 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17572 > Project: Cassandra > Issue Type: Bug > Components: Cluster/Membership >Reporter: Sam Kramer >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.x > > > Hi, > We noticed that there is a race condition present in the trunk of 3.x code, > and confirmed that it’s there in 4.x as well, which will result in incorrect > reads, and missed writes, for a very short period of time. > What brought the race condition to our attention was due to the fact we > started noticing a couple of missed writes for our Cassandra clusters in > Kubernetes. We found the Kubernetes piece interesting, as IP changes are very > frequent as opposed to a traditional setup. > More concretely: > # When a Cassandra node is turned off, and then starts with a new IP address > Z (former IP address X), it announces to the cluster (via gossip) it has IP Z > for Host ID Y > # If there are no conflicts, each node will decide to remove the old IP > address associated with Host ID Y > ([https://github.com/apache/cassandra/blob/cassandra-3.11/src/java/org/apache/cassandra/service/StorageService.java#L2529-L2532]) > from the storage ring. This also causes us to invalidate our token ring > cache > ([https://github.com/apache/cassandra/blob/cassandra-3.11/src/java/org/apache/cassandra/locator/TokenMetadata.java#L488] > ). > # At this time, a new request could come in (read or write), and will > re-calculate which endpoints to send the request to, as we’ve invalidated our > token ring cache > ([https://github.com/apache/cassandra/blob/cassandra-3.11/src/java/org/apache/cassandra/locator/AbstractReplicationStrategy.java#L88-L104]). > # However, at this time we’ve only removed the IP address X (former IP > address), and have not re-added IP address Z. > # As a result, we will choose a new host to route our request to. In our > case, our keyspaces all run with NetworkTopologyStrategy, and so we simply > choose the node with the next closest token in the same rack as host Y > ([https://github.com/apache/cassandra/blob/cassandra-3.11/src/java/org/apache/cassandra/locator/NetworkTopologyStrategy.java#L149-L191]). > # Thus, the request is routed to a _different_ host, rather than the host > that has came back online. > # However, shortly later, we re-add the host (via it’s _new_ endpoint) to > the token ring > [https://github.com/apache/cassandra/blob/cassandra-3.11/src/java/org/apache/cassandra/service/StorageService.java#L2549] > # This will result in us invalidating our cache, and then again re-routing > requests appropriately. > Couple of additional thoughts: > - This doesn’t affect clusters where nodes <= RF with network topology > strategy. > - During this very brief period of time, CL for all user queries are > violated, but are ACK’d as successful. > - It’s easy to reproduce this race condition by simply adding a sleep here > ([https://github.com/apache/cassandra/blob/cassandra-3.11/src/java/org/apache/cassandra/service/StorageService.java#L2529-L2532]) > - If a cleanup is not ran before any range movement, it’s possible for rows > that were temporarily written to the wrong node re-appear. > - We tested that the race condition exists in our Cassandra 2.x fork (we're > not on 3.x or 4.x). So, there is a possibility here that it's only for > Cassandra 2.x, however unlikely from reading the code. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17575) forceCompactionForTokenRange when using a wrapped range may include sstables not within that range
[ https://issues.apache.org/jira/browse/CASSANDRA-17575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536178#comment-17536178 ] Ekaterina Dimitrova commented on CASSANDRA-17575: - Hey [~dcapwell] , I am triaging tickets and I am a bit confused here - (32,31] and (32,32) are kind of the same, no? Did you mean to say 32 was also included during testing? > forceCompactionForTokenRange when using a wrapped range may include sstables > not within that range > -- > > Key: CASSANDRA-17575 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17575 > Project: Cassandra > Issue Type: Bug > Components: Local/Compaction >Reporter: David Capwell >Priority: Normal > Fix For: 4.1.x, 4.1-beta > > > This was found in CASSANDRA-17537 > When you compact the range (32, 31] this should include everything BUT 32, > but in the test > org.apache.cassandra.db.compaction.LeveledCompactionStrategyTest#testTokenRangeCompaction > it found that SSTables with the bounds (32, 32) were getting included in the > set of SSTables to compact -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17575) forceCompactionForTokenRange when using a wrapped range may include sstables not within that range
[ https://issues.apache.org/jira/browse/CASSANDRA-17575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17575: Fix Version/s: 4.1.x 4.1-beta (was: 4.x) > forceCompactionForTokenRange when using a wrapped range may include sstables > not within that range > -- > > Key: CASSANDRA-17575 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17575 > Project: Cassandra > Issue Type: Bug > Components: Local/Compaction >Reporter: David Capwell >Priority: Normal > Fix For: 4.1.x, 4.1-beta > > > This was found in CASSANDRA-17537 > When you compact the range (32, 31] this should include everything BUT 32, > but in the test > org.apache.cassandra.db.compaction.LeveledCompactionStrategyTest#testTokenRangeCompaction > it found that SSTables with the bounds (32, 32) were getting included in the > set of SSTables to compact -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17583) Fix flaky test - org.apache.cassandra.distributed.test.MessageForwardingTest.mutationsForwardedToAllReplicasTest
[
https://issues.apache.org/jira/browse/CASSANDRA-17583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17583:
Fix Version/s: 4.1-beta
> Fix flaky test -
> org.apache.cassandra.distributed.test.MessageForwardingTest.mutationsForwardedToAllReplicasTest
>
>
> Key: CASSANDRA-17583
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17583
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Internode
>Reporter: Brandon Williams
>Priority: Normal
> Fix For: 4.x, 4.1-beta
>
>
> h3. Error Message
> /127.0.0.3 appending to commitlog traces expected:<100> but was:<98>
> h3. Stacktrace
> {noformat}
> junit.framework.AssertionFailedError: /127.0.0.3 appending to commitlog
> traces expected:<100> but was:<98> at
> org.apache.cassandra.distributed.test.MessageForwardingTest.lambda$mutationsForwardedToAllReplicasTest$8(MessageForwardingTest.java:92)
> at java.base/java.util.HashMap.forEach(HashMap.java:1336) at
> org.apache.cassandra.distributed.test.MessageForwardingTest.mutationsForwardedToAllReplicasTest(MessageForwardingTest.java:91)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17607) Fix org.apache.cassandra.db.commitlog.BatchCommitLogTest.testOutOfOrderFlushRecovery[3]-cdc
[
https://issues.apache.org/jira/browse/CASSANDRA-17607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17607:
Fix Version/s: 4.1-beta
> Fix
> org.apache.cassandra.db.commitlog.BatchCommitLogTest.testOutOfOrderFlushRecovery[3]-cdc
> ---
>
> Key: CASSANDRA-17607
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17607
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x, 4.1-beta
>
>
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1130/testReport/org.apache.cassandra.db.commitlog/BatchCommitLogTest/testOutOfOrderFlushRecovery_3__cdc/]
>
> h3.
> {code:java}
> Stacktrace
> java.io.UncheckedIOException at
> org.apache.cassandra.io.util.PathUtils.propagateUnchecked(PathUtils.java:768)
> at
> org.apache.cassandra.io.util.PathUtils.propagateUnchecked(PathUtils.java:753)
> at org.apache.cassandra.io.util.PathUtils.delete(PathUtils.java:255) at
> org.apache.cassandra.io.util.PathUtils.delete(PathUtils.java:297) at
> org.apache.cassandra.io.util.PathUtils.delete(PathUtils.java:304) at
> org.apache.cassandra.io.util.File.delete(File.java:158) at
> org.apache.cassandra.io.util.File.delete(File.java:167) at
> org.apache.cassandra.io.util.FileUtils.deleteWithConfirm(FileUtils.java:691)
> at
> org.apache.cassandra.db.commitlog.CommitLogSegment.discard(CommitLogSegment.java:449)
> at
> org.apache.cassandra.db.commitlog.AbstractCommitLogSegmentManager.discardAvailableSegment(AbstractCommitLogSegmentManager.java:519)
> at
> org.apache.cassandra.db.commitlog.AbstractCommitLogSegmentManager.shutdown(AbstractCommitLogSegmentManager.java:506)
> at
> org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDC.shutdown(CommitLogSegmentManagerCDC.java:157)
> at
> org.apache.cassandra.db.commitlog.AbstractCommitLogSegmentManager.stopUnsafe(AbstractCommitLogSegmentManager.java:452)
> at
> org.apache.cassandra.db.commitlog.CommitLog.stopUnsafe(CommitLog.java:504) at
> org.apache.cassandra.db.commitlog.CommitLog.resetUnsafe(CommitLog.java:470)
> at
> org.apache.cassandra.db.commitlog.CommitLogTest.testOutOfOrderFlushRecovery(CommitLogTest.java:991)
> at
> org.apache.cassandra.db.commitlog.CommitLogTest.testOutOfOrderFlushRecovery(CommitLogTest.java:1057)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Caused by: java.nio.file.NoSuchFileException:
> build/test/cassandra/commitlog/CommitLog-7-1651753848882.log at
> java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:116)
> at
> java.base/sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:249)
> at
> java.base/sun.nio.fs.AbstractFileSystemProvider.delete(AbstractFileSystemProvider.java:105)
> at java.base/java.nio.file.Files.delete(Files.java:1142) at
> org.apache.cassandra.io.util.PathUtils.delete(PathUtils.java:250)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17615) Flaky org.apache.cassandra.cql3.KeywordTest
[
https://issues.apache.org/jira/browse/CASSANDRA-17615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536166#comment-17536166
]
Ekaterina Dimitrova commented on CASSANDRA-17615:
-
It seems the assertions time out, not the test? What do I miss?
> Flaky org.apache.cassandra.cql3.KeywordTest
> ---
>
> Key: CASSANDRA-17615
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17615
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x, 4.1-beta
>
>
> The tests in this class fail very often with:
> h3.
> {code:java}
> Error Message
> Timeout occurred. Please note the time in the report does not reflect the
> time until the timeout.
> Stacktrace
> junit.framework.AssertionFailedError: Timeout occurred. Please note the time
> in the report does not reflect the time until the timeout. at
> java.util.Vector.forEach(Vector.java:1277) at
> java.util.Vector.forEach(Vector.java:1277) at
> java.util.Vector.forEach(Vector.java:1277) at
> org.apache.cassandra.anttasks.TestHelper.execute(TestHelper.java:53) at
> java.util.Vector.forEach(Vector.java:1277)
> {code}
>
> I don't think I've seen them failing in CircleCI, but I see different tests
> from the class in Jenkins timing out.
> Example:
> [https://jenkins-cm4.apache.org/job/Cassandra-4.1/5/testReport/junit/org.apache.cassandra.cql3/KeywordTest/test_keyword_MODIFY_isReserved_true_/]
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14113) AssertionError while trying to upgrade 2.2.11 -> 3.11.1
[
https://issues.apache.org/jira/browse/CASSANDRA-14113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536108#comment-17536108
]
Brandon Williams commented on CASSANDRA-14113:
--
I put [this|https://github.com/driftx/cassandra/tree/CASSANDRA-14113-3.11]
through circle
[here|https://app.circleci.com/pipelines/github/driftx/cassandra/476/workflows/3d84d20f-c919-4974-b7ed-8960381c0a64/jobs/5539]
and unfortunately it looks like it indeed broke some things.
> AssertionError while trying to upgrade 2.2.11 -> 3.11.1
> ---
>
> Key: CASSANDRA-14113
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14113
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core
> Environment: Tables have been created in 2.2.11 using thrift and have
> supercolumns
>Reporter: Guillaume Herail
>Assignee: Marten Kenbeek
>Priority: Normal
> Labels: supercolumns
> Attachments: 14113-3.0.txt, data.tar.gz
>
>
> We're trying to upgrade a test cluster from Cassandra 2.2.11 to Cassandra
> 3.11.1. The tables have been created using thrift and have supercolumns. When
> I try to run {{nodetool upgradesstables}} I get the following:
> {noformat}error: null
> -- StackTrace --
> java.lang.AssertionError
> at org.apache.cassandra.db.rows.BufferCell.(BufferCell.java:42)
> at
> org.apache.cassandra.db.LegacyLayout$CellGrouper.addCell(LegacyLayout.java:1242)
> at
> org.apache.cassandra.db.LegacyLayout$CellGrouper.addAtom(LegacyLayout.java:1185)
> at
> org.apache.cassandra.db.UnfilteredDeserializer$OldFormatDeserializer$UnfilteredIterator.readRow(UnfilteredDeserializer.java:498)
> at
> org.apache.cassandra.db.UnfilteredDeserializer$OldFormatDeserializer$UnfilteredIterator.hasNext(UnfilteredDeserializer.java:472)
> at
> org.apache.cassandra.db.UnfilteredDeserializer$OldFormatDeserializer.hasNext(UnfilteredDeserializer.java:306)
> at
> org.apache.cassandra.io.sstable.SSTableSimpleIterator$OldFormatIterator.computeNext(SSTableSimpleIterator.java:188)
> at
> org.apache.cassandra.io.sstable.SSTableSimpleIterator$OldFormatIterator.computeNext(SSTableSimpleIterator.java:140)
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> at
> org.apache.cassandra.io.sstable.SSTableIdentityIterator.hasNext(SSTableIdentityIterator.java:122)
> at
> org.apache.cassandra.db.rows.LazilyInitializedUnfilteredRowIterator.computeNext(LazilyInitializedUnfilteredRowIterator.java:100)
> at
> org.apache.cassandra.db.rows.LazilyInitializedUnfilteredRowIterator.computeNext(LazilyInitializedUnfilteredRowIterator.java:32)
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> at
> org.apache.cassandra.utils.MergeIterator$TrivialOneToOne.computeNext(MergeIterator.java:484)
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:499)
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:359)
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> at org.apache.cassandra.db.transform.BaseRows.hasNext(BaseRows.java:133)
> at
> org.apache.cassandra.db.transform.UnfilteredRows.isEmpty(UnfilteredRows.java:74)
> at
> org.apache.cassandra.db.partitions.PurgeFunction.applyToPartition(PurgeFunction.java:75)
> at
> org.apache.cassandra.db.partitions.PurgeFunction.applyToPartition(PurgeFunction.java:26)
> at
> org.apache.cassandra.db.transform.BasePartitions.hasNext(BasePartitions.java:96)
> at
> org.apache.cassandra.db.compaction.CompactionIterator.hasNext(CompactionIterator.java:233)
> at
> org.apache.cassandra.db.compaction.CompactionTask.runMayThrow(CompactionTask.java:196)
> at
> org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
> at
> org.apache.cassandra.db.compaction.CompactionTask.executeInternal(CompactionTask.java:85)
> at
> org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(AbstractCompactionTask.java:61)
> at
> org.apache.cassandra.db.compaction.CompactionManager$5.execute(CompactionManager.java:428)
> at
> org.apache.cassandra.db.compaction.CompactionManager$2.call(CompactionManager.java:315)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
>
[jira] [Commented] (CASSANDRA-14113) AssertionError while trying to upgrade 2.2.11 -> 3.11.1
[
https://issues.apache.org/jira/browse/CASSANDRA-14113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536087#comment-17536087
]
Marten Kenbeek commented on CASSANDRA-14113:
Hi [~blerer], is there any improvement in the CI situation? Where would I be
able to see the results (if they're still available)? I found
[https://ci-cassandra.apache.org/,] but wasn't entirely sure where the results
for patches would show up.
It would be great if we could land this patch so we no longer have to run our
own patched version. Please let me know if you have time for this, or if it
would be better to find someone else for the review.
> AssertionError while trying to upgrade 2.2.11 -> 3.11.1
> ---
>
> Key: CASSANDRA-14113
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14113
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core
> Environment: Tables have been created in 2.2.11 using thrift and have
> supercolumns
>Reporter: Guillaume Herail
>Assignee: Marten Kenbeek
>Priority: Normal
> Labels: supercolumns
> Attachments: 14113-3.0.txt, data.tar.gz
>
>
> We're trying to upgrade a test cluster from Cassandra 2.2.11 to Cassandra
> 3.11.1. The tables have been created using thrift and have supercolumns. When
> I try to run {{nodetool upgradesstables}} I get the following:
> {noformat}error: null
> -- StackTrace --
> java.lang.AssertionError
> at org.apache.cassandra.db.rows.BufferCell.(BufferCell.java:42)
> at
> org.apache.cassandra.db.LegacyLayout$CellGrouper.addCell(LegacyLayout.java:1242)
> at
> org.apache.cassandra.db.LegacyLayout$CellGrouper.addAtom(LegacyLayout.java:1185)
> at
> org.apache.cassandra.db.UnfilteredDeserializer$OldFormatDeserializer$UnfilteredIterator.readRow(UnfilteredDeserializer.java:498)
> at
> org.apache.cassandra.db.UnfilteredDeserializer$OldFormatDeserializer$UnfilteredIterator.hasNext(UnfilteredDeserializer.java:472)
> at
> org.apache.cassandra.db.UnfilteredDeserializer$OldFormatDeserializer.hasNext(UnfilteredDeserializer.java:306)
> at
> org.apache.cassandra.io.sstable.SSTableSimpleIterator$OldFormatIterator.computeNext(SSTableSimpleIterator.java:188)
> at
> org.apache.cassandra.io.sstable.SSTableSimpleIterator$OldFormatIterator.computeNext(SSTableSimpleIterator.java:140)
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> at
> org.apache.cassandra.io.sstable.SSTableIdentityIterator.hasNext(SSTableIdentityIterator.java:122)
> at
> org.apache.cassandra.db.rows.LazilyInitializedUnfilteredRowIterator.computeNext(LazilyInitializedUnfilteredRowIterator.java:100)
> at
> org.apache.cassandra.db.rows.LazilyInitializedUnfilteredRowIterator.computeNext(LazilyInitializedUnfilteredRowIterator.java:32)
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> at
> org.apache.cassandra.utils.MergeIterator$TrivialOneToOne.computeNext(MergeIterator.java:484)
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:499)
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:359)
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> at org.apache.cassandra.db.transform.BaseRows.hasNext(BaseRows.java:133)
> at
> org.apache.cassandra.db.transform.UnfilteredRows.isEmpty(UnfilteredRows.java:74)
> at
> org.apache.cassandra.db.partitions.PurgeFunction.applyToPartition(PurgeFunction.java:75)
> at
> org.apache.cassandra.db.partitions.PurgeFunction.applyToPartition(PurgeFunction.java:26)
> at
> org.apache.cassandra.db.transform.BasePartitions.hasNext(BasePartitions.java:96)
> at
> org.apache.cassandra.db.compaction.CompactionIterator.hasNext(CompactionIterator.java:233)
> at
> org.apache.cassandra.db.compaction.CompactionTask.runMayThrow(CompactionTask.java:196)
> at
> org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
> at
> org.apache.cassandra.db.compaction.CompactionTask.executeInternal(CompactionTask.java:85)
> at
> org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(AbstractCompactionTask.java:61)
> at
> org.apache.cassandra.db.compaction.CompactionManager$5.execute(CompactionManager.java:428)
> at
> org.apache.cassandra.db.compaction.CompactionManager$2.call(CompactionManager.java:315)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
>
[jira] [Commented] (CASSANDRA-17621) WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework"
[
https://issues.apache.org/jira/browse/CASSANDRA-17621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536083#comment-17536083
]
Erick Ramirez commented on CASSANDRA-17621:
---
I've completed final verification in staging and [published to
production|https://github.com/apache/cassandra-website#merging-asf-staging-to-asf-site]:
{noformat}
$ git branch
* trunk
$ git fetch origin
$ git checkout asf-site
Branch 'asf-site' set up to track remote branch 'asf-site' from 'origin'.
Switched to a new branch 'asf-site'
$ git branch
* asf-site
trunk
$ git reset --hard origin/asf-staging
HEAD is now at f00461fb generate docs for a5fdecab
$ git push -f origin asf-site
Username for 'https://github.com': erickramirezau
Password for 'https://erickramire...@github.com':
Total 0 (delta 0), reused 0 (delta 0)
To https://github.com/apache/cassandra-website.git
+ 82038370...f00461fb asf-site -> asf-site (forced update){noformat}
The blog post is now live in production –
https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html.
> WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework"
> -
>
> Key: CASSANDRA-17621
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17621
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Andres de la Peña
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.1-rc
>
> Attachments: c17621-01-blog-index.png, c17621-02-blog-post.png
>
>
> This ticket is to capture the work associated with publishing the May 2022
> blog "Apache Cassandra 4.1 Features: Guardrails Framework"
> If this blog cannot be published by the *May 12, 2022 publish date*, please
> contact me, suggest changes, or correct the date when possible in the pull
> request for the appropriate time that the blog will go live (on both the
> blog.adoc and the blog post's file).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-site updated (82038370 -> f00461fb)
This is an automated email from the ASF dual-hosted git repository.
erickramirezau pushed a change to branch asf-site
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git
discard 82038370 generate docs for 7bb7e8e6
add a5fdecab BLOG - Cassandra 4.1 Features: Guardrails Framework
add f00461fb generate docs for a5fdecab
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (82038370)
\
N -- N -- N refs/heads/asf-site (f00461fb)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
...tures-guardrails-framework-unsplash-jj-ying.jpg | Bin 0 -> 136965 bytes
content/_/blog.html| 24 +++
...ssandra-4.1-Features-Guardrails-Framework.html} | 228 ++---
.../cassandra/configuration/cass_yaml_file.html| 154 +-
content/doc/4.1/cassandra/operating/cdc.html | 8 +-
.../cassandra/configuration/cass_yaml_file.html| 154 +-
content/doc/latest/cassandra/operating/cdc.html| 8 +-
.../cassandra/configuration/cass_yaml_file.html| 154 +-
content/doc/trunk/cassandra/operating/cdc.html | 8 +-
content/search-index.js| 2 +-
...tures-guardrails-framework-unsplash-jj-ying.jpg | Bin 0 -> 136965 bytes
site-content/source/modules/ROOT/pages/blog.adoc | 25 +++
...assandra-4.1-Features-Guardrails-Framework.adoc | 136
site-ui/build/ui-bundle.zip| Bin 4740078 -> 4740078
bytes
14 files changed, 687 insertions(+), 214 deletions(-)
create mode 100644
content/_/_images/blog/apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg
copy content/_/blog/{Tightening-Security-for-Apache-Cassandra-Part-2.html =>
Apache-Cassandra-4.1-Features-Guardrails-Framework.html} (50%)
create mode 100644
site-content/source/modules/ROOT/images/blog/apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg
create mode 100644
site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.adoc
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17621) WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework"
[ https://issues.apache.org/jira/browse/CASSANDRA-17621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536080#comment-17536080 ] Erick Ramirez commented on CASSANDRA-17621: --- The blog post is now in staging – https://cassandra.staged.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html. > WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework" > - > > Key: CASSANDRA-17621 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17621 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Andres de la Peña >Priority: Normal > Labels: pull-request-available > Fix For: 4.1-rc > > Attachments: c17621-01-blog-index.png, c17621-02-blog-post.png > > > This ticket is to capture the work associated with publishing the May 2022 > blog "Apache Cassandra 4.1 Features: Guardrails Framework" > If this blog cannot be published by the *May 12, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17621) WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework"
[
https://issues.apache.org/jira/browse/CASSANDRA-17621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536079#comment-17536079
]
Erick Ramirez commented on CASSANDRA-17621:
---
||Branch||PR||Commit||Build||
|{{trunk}}|[#128|https://github.com/apache/cassandra-website/pull/127]|[a5fdeca
|https://github.com/apache/cassandra-website/commit/a5fdecabfb800cb6638086739171bbe0faebd20e]|[#239|https://ci-cassandra.apache.org/job/cassandra-website/239/]|
> WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework"
> -
>
> Key: CASSANDRA-17621
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17621
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Andres de la Peña
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.1-rc
>
> Attachments: c17621-01-blog-index.png, c17621-02-blog-post.png
>
>
> This ticket is to capture the work associated with publishing the May 2022
> blog "Apache Cassandra 4.1 Features: Guardrails Framework"
> If this blog cannot be published by the *May 12, 2022 publish date*, please
> contact me, suggest changes, or correct the date when possible in the pull
> request for the appropriate time that the blog will go live (on both the
> blog.adoc and the blog post's file).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (1309ecba -> f00461fb)
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a change to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git
discard 1309ecba generate docs for 7bb7e8e6
add a5fdecab BLOG - Cassandra 4.1 Features: Guardrails Framework
new f00461fb generate docs for a5fdecab
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (1309ecba)
\
N -- N -- N refs/heads/asf-staging (f00461fb)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
...tures-guardrails-framework-unsplash-jj-ying.jpg | Bin 0 -> 136965 bytes
content/_/blog.html| 24 +++
...ssandra-4.1-Features-Guardrails-Framework.html} | 228 ++---
content/search-index.js| 2 +-
...tures-guardrails-framework-unsplash-jj-ying.jpg | Bin 0 -> 136965 bytes
site-content/source/modules/ROOT/pages/blog.adoc | 25 +++
...assandra-4.1-Features-Guardrails-Framework.adoc | 136
site-ui/build/ui-bundle.zip| Bin 4740078 -> 4740078
bytes
8 files changed, 345 insertions(+), 70 deletions(-)
create mode 100644
content/_/_images/blog/apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg
copy content/_/blog/{Tightening-Security-for-Apache-Cassandra-Part-2.html =>
Apache-Cassandra-4.1-Features-Guardrails-Framework.html} (50%)
create mode 100644
site-content/source/modules/ROOT/images/blog/apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg
create mode 100644
site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.adoc
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17621) WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework"
[
https://issues.apache.org/jira/browse/CASSANDRA-17621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-17621:
--
Source Control Link:
https://github.com/apache/cassandra-website/commit/a5fdecabfb800cb6638086739171bbe0faebd20e
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed:
||Branch||PR||Commit||
|{{trunk}}|[#128|https://github.com/apache/cassandra-website/pull/127]|[a5fdeca
|https://github.com/apache/cassandra-website/commit/a5fdecabfb800cb6638086739171bbe0faebd20e]|
> WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework"
> -
>
> Key: CASSANDRA-17621
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17621
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Andres de la Peña
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.1-rc
>
> Attachments: c17621-01-blog-index.png, c17621-02-blog-post.png
>
>
> This ticket is to capture the work associated with publishing the May 2022
> blog "Apache Cassandra 4.1 Features: Guardrails Framework"
> If this blog cannot be published by the *May 12, 2022 publish date*, please
> contact me, suggest changes, or correct the date when possible in the pull
> request for the appropriate time that the blog will go live (on both the
> blog.adoc and the blog post's file).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17621) WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework"
[ https://issues.apache.org/jira/browse/CASSANDRA-17621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17621: -- Reviewers: Andres de la Peña, Erick Ramirez, Stefan Miklosovic (was: Andres de la Peña, Erick Ramirez) > WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework" > - > > Key: CASSANDRA-17621 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17621 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Andres de la Peña >Priority: Normal > Labels: pull-request-available > Fix For: 4.1-rc > > Attachments: c17621-01-blog-index.png, c17621-02-blog-post.png > > > This ticket is to capture the work associated with publishing the May 2022 > blog "Apache Cassandra 4.1 Features: Guardrails Framework" > If this blog cannot be published by the *May 12, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17621) WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework"
[ https://issues.apache.org/jira/browse/CASSANDRA-17621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17621: -- Status: Ready to Commit (was: Review In Progress) > WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework" > - > > Key: CASSANDRA-17621 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17621 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Andres de la Peña >Priority: Normal > Labels: pull-request-available > Fix For: 4.1-rc > > Attachments: c17621-01-blog-index.png, c17621-02-blog-post.png > > > This ticket is to capture the work associated with publishing the May 2022 > blog "Apache Cassandra 4.1 Features: Guardrails Framework" > If this blog cannot be published by the *May 12, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17621) WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework"
[ https://issues.apache.org/jira/browse/CASSANDRA-17621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17621: -- Status: Review In Progress (was: Changes Suggested) > WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework" > - > > Key: CASSANDRA-17621 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17621 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Andres de la Peña >Priority: Normal > Labels: pull-request-available > Fix For: 4.1-rc > > Attachments: c17621-01-blog-index.png, c17621-02-blog-post.png > > > This ticket is to capture the work associated with publishing the May 2022 > blog "Apache Cassandra 4.1 Features: Guardrails Framework" > If this blog cannot be published by the *May 12, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17621) WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework"
[
https://issues.apache.org/jira/browse/CASSANDRA-17621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536076#comment-17536076
]
Erick Ramirez commented on CASSANDRA-17621:
---
Noting here that I've also added an extra paragraph at the end of the blog
based on the excellent suggestion from [~stefan.miklosovic] in PR#128:
{quote}If you have ideas for new guardrails, please feel free [to log a
ticket|https://issues.apache.org/jira/secure/CreateIssue.jspa?pid=12310865]
with details of your proposal and we would be happy to look into it.
{quote}
> WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework"
> -
>
> Key: CASSANDRA-17621
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17621
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Andres de la Peña
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.1-rc
>
> Attachments: c17621-01-blog-index.png, c17621-02-blog-post.png
>
>
> This ticket is to capture the work associated with publishing the May 2022
> blog "Apache Cassandra 4.1 Features: Guardrails Framework"
> If this blog cannot be published by the *May 12, 2022 publish date*, please
> contact me, suggest changes, or correct the date when possible in the pull
> request for the appropriate time that the blog will go live (on both the
> blog.adoc and the blog post's file).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch trunk updated: BLOG - Cassandra 4.1 Features: Guardrails Framework
This is an automated email from the ASF dual-hosted git repository. erickramirezau pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra-website.git The following commit(s) were added to refs/heads/trunk by this push: new a5fdecab BLOG - Cassandra 4.1 Features: Guardrails Framework a5fdecab is described below commit a5fdecabfb800cb6638086739171bbe0faebd20e Author: Diogenese Topper AuthorDate: Wed May 11 11:20:41 2022 -0700 BLOG - Cassandra 4.1 Features: Guardrails Framework patch by Andrés de la Peña, Chris Thornett, Diogenese Topper, Erick Ramirez; reviewed by Erick Ramirez, Štefan Miklošovič for CASSANDRA-17621 Co-authored by: Andrés de la Peña Co-authored by: Chris Thornett Co-authored by: Diogenese Topper Co-authored by: Erick Ramirez --- ...tures-guardrails-framework-unsplash-jj-ying.jpg | Bin 0 -> 136965 bytes site-content/source/modules/ROOT/pages/blog.adoc | 25 ...assandra-4.1-Features-Guardrails-Framework.adoc | 136 + 3 files changed, 161 insertions(+) diff --git a/site-content/source/modules/ROOT/images/blog/apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg b/site-content/source/modules/ROOT/images/blog/apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg new file mode 100644 index ..dc9c187f Binary files /dev/null and b/site-content/source/modules/ROOT/images/blog/apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg differ diff --git a/site-content/source/modules/ROOT/pages/blog.adoc b/site-content/source/modules/ROOT/pages/blog.adoc index 5b6dd9fb..f7bc32a9 100644 --- a/site-content/source/modules/ROOT/pages/blog.adoc +++ b/site-content/source/modules/ROOT/pages/blog.adoc @@ -8,6 +8,31 @@ NOTES FOR CONTENT CREATORS - Replace post tile, date, description and link to you post. +//start card +[openblock,card shadow relative test] + +[openblock,card-header] +-- +[discrete] +=== Apache Cassandra 4.1 Features: Guardrails Framework +[discrete] + May 12, 2022 +-- +[openblock,card-content] +-- +Cassandra 4.1 introduces Guardrails - a framework that helps enforce good practices to avoid poor cluster performance and availability because of certain user actions. + +[openblock,card-btn card-btn--blog] + + +[.btn.btn--alt] +xref:blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.adoc[Read More] + + +-- + +//end card + //start card [openblock,card shadow relative test] diff --git a/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.adoc b/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.adoc new file mode 100644 index ..c0dfcd40 --- /dev/null +++ b/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.adoc @@ -0,0 +1,136 @@ += Apache Cassandra 4.1 Features: Guardrails Framework +:page-layout: single-post +:page-role: blog-post +:page-post-date: May 12, 2022 +:page-post-author: Andrés de la Peña +:description: New Guardrails Framework in Apache Cassandra 4.1 +:keywords: 4.1, features, guardrails + +:!figure-caption: + +.Image credit: https://unsplash.com/@jjying[JJ Ying on Unsplash^] +image::blog/apache-cassandra-4.1-features-guardrails-framework-unsplash-jj-ying.jpg[New Guardrails framework] + +In Apache Cassandra 4.1.0, we are introducing a new framework called Guardrails. The framework helps operators avoid certain configuration and usage pitfalls that can degrade the performance and availability of an Apache Cassandra cluster when taken to scale. + +For example, on the schema side, users can create too many tables or secondary indexes, leading to excessive use of resources. On the query side, users can run queries touching too many partitions that might involve all nodes in the cluster. Even worse, they can simply run a query using costly replica-side filtering, potentially reading all the table contents into memory on all nodes across the cluster. All these are well-known Cassandra anti-patterns, and administrators have to be vigil [...] + +The new framework allows operators to restrict how Cassandra is used by: + +* Disabling certain features. +* Disallowing some specific values. +* Defining soft and hard limits to certain database magnitudes. + +=== Configuring Guardrails + +Guardrails are defined as regular properties in the Cassandra configuration file, https://cassandra.apache.org/doc/latest/cassandra/configuration/cass_yaml_file.html[`cassandra.yaml`]. They look like: + +``` +tables_warn_threshold: -1 +tables_fail_threshold: -1 +secondary_indexes_per_table_warn_threshold: -1 +secondary_indexes_per_table_fail_threshold: -1 +allow_filtering_enabled: true +partition_keys_in_select_warn_threshold: -1 +partition_keys_in_select_fail_threshold: -1 +collection_size_warn_threshold:
[jira] [Commented] (CASSANDRA-17615) Flaky org.apache.cassandra.cql3.KeywordTest
[
https://issues.apache.org/jira/browse/CASSANDRA-17615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536066#comment-17536066
]
Brandon Williams commented on CASSANDRA-17615:
--
That sounds good to me.
> Flaky org.apache.cassandra.cql3.KeywordTest
> ---
>
> Key: CASSANDRA-17615
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17615
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x, 4.1-beta
>
>
> The tests in this class fail very often with:
> h3.
> {code:java}
> Error Message
> Timeout occurred. Please note the time in the report does not reflect the
> time until the timeout.
> Stacktrace
> junit.framework.AssertionFailedError: Timeout occurred. Please note the time
> in the report does not reflect the time until the timeout. at
> java.util.Vector.forEach(Vector.java:1277) at
> java.util.Vector.forEach(Vector.java:1277) at
> java.util.Vector.forEach(Vector.java:1277) at
> org.apache.cassandra.anttasks.TestHelper.execute(TestHelper.java:53) at
> java.util.Vector.forEach(Vector.java:1277)
> {code}
>
> I don't think I've seen them failing in CircleCI, but I see different tests
> from the class in Jenkins timing out.
> Example:
> [https://jenkins-cm4.apache.org/job/Cassandra-4.1/5/testReport/junit/org.apache.cassandra.cql3/KeywordTest/test_keyword_MODIFY_isReserved_true_/]
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17455) Flaky org.apache.cassandra.tools TopPartitionsTest testServiceTopPartitionsSingleTable
[
https://issues.apache.org/jira/browse/CASSANDRA-17455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536065#comment-17536065
]
Brandon Williams commented on CASSANDRA-17455:
--
Looks reasonable to me. It would be nice if we had the ability to loop this in
jenkins so we could verify it solves the issue in that environment beforehand,
but today is not that day.
> Flaky org.apache.cassandra.tools TopPartitionsTest
> testServiceTopPartitionsSingleTable
> --
>
> Key: CASSANDRA-17455
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17455
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Stefan Miklosovic
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 4.1-beta
>
>
> {code:java}
> Error Messageexpected:<1> but
> was:<0>Stacktracejunit.framework.AssertionFailedError: expected:<1> but
> was:<0>
> at
> org.apache.cassandra.tools.TopPartitionsTest.testServiceTopPartitionsSingleTable(TopPartitionsTest.java:82)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Standard OutputINFO [main] 2022-03-17 23:37:01,750
> YamlConfigurationLoader.java:103 - Configuration location:
> file:/home/cassandra/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2022-03-17 23:37:01,754 YamlConfigurationLoader.java:124 -
> Loading settings from file:/home/cassandra/cassandra/test/conf/cassandra.yaml
> INFO [main] 2022-03-17 23:37:01,878 Config.java:1119 - Node
> configuration:[allocate_tokens_for_keyspace=null;
> allocate_tokens_for_local_replication_factor=null;
> allow_extra_insecure_udfs=false; all
> ...[truncated 49100 chars]...
> lizing counter cache with capacity of 2 MiBs
> INFO [MemtableFlushWriter:1] 2022-03-17 23:37:03,857 CacheService.java:164 -
> Scheduling counter cache save to every 7200 seconds (going to save all keys).
> DEBUG [MemtableFlushWriter:1] 2022-03-17 23:37:03,883
> ColumnFamilyStore.java:1249 - Flushed to
> [BigTableReader(path='/home/cassandra/cassandra/build/test/cassandra/data/system/IndexInfo-9f5c6374d48532299a0a5094af9ad1e3/nb-1-big-Data.db')]
> (1 sstables, 4.915KiB), biggest 4.915KiB, smallest 4.915KiB {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17621) WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework"
[
https://issues.apache.org/jira/browse/CASSANDRA-17621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-17621:
--
Status: Changes Suggested (was: Review In Progress)
I've reviewed the PR and recommend the following changes:
* The cards on the blog index can only have a maximum of 175 characters (or
roughly 25 words) so the blog summary needs to be edited to fit within the card.
* Replace the hardcoded {{/doc}} URLs with a {{link:}} to the corresponding
{{*.adoc}} page.
!c17621-01-blog-index.png|width=400!
!c17621-02-blog-post.png|width=400!
> WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework"
> -
>
> Key: CASSANDRA-17621
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17621
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Andres de la Peña
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.1-rc
>
> Attachments: c17621-01-blog-index.png, c17621-02-blog-post.png
>
>
> This ticket is to capture the work associated with publishing the May 2022
> blog "Apache Cassandra 4.1 Features: Guardrails Framework"
> If this blog cannot be published by the *May 12, 2022 publish date*, please
> contact me, suggest changes, or correct the date when possible in the pull
> request for the appropriate time that the blog will go live (on both the
> blog.adoc and the blog post's file).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17621) WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework"
[ https://issues.apache.org/jira/browse/CASSANDRA-17621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17621: -- Attachment: c17621-02-blog-post.png c17621-01-blog-index.png > WEBSITE - May 2022 blog "Apache Cassandra 4.1 Features: Guardrails Framework" > - > > Key: CASSANDRA-17621 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17621 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Andres de la Peña >Priority: Normal > Labels: pull-request-available > Fix For: 4.1-rc > > Attachments: c17621-01-blog-index.png, c17621-02-blog-post.png > > > This ticket is to capture the work associated with publishing the May 2022 > blog "Apache Cassandra 4.1 Features: Guardrails Framework" > If this blog cannot be published by the *May 12, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
