[jira] [Commented] (CASSANDRA-17964) Some tests are never executed due to naming violation - fix it and add checkstyle where applicable
[ https://issues.apache.org/jira/browse/CASSANDRA-17964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646946#comment-17646946 ] Berenguer Blasi commented on CASSANDRA-17964: - I will be starting my xmas break this week #justfyi in case I don't answer. > Some tests are never executed due to naming violation - fix it and add > checkstyle where applicable > -- > > Key: CASSANDRA-17964 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17964 > Project: Cassandra > Issue Type: Task > Components: Test/unit >Reporter: Ruslan Fomkin >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 4.x > > Time Spent: 2h 40m > Remaining Estimate: 0h > > [BatchTests|https://github.com/apache/cassandra/blob/trunk/test/unit/org/apache/cassandra/cql3/BatchTests.java] > doesn't follow naming convention to be run as unit tests and, thus, is never > run. > The rule in build expects names as `*Test`. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (ad7b2d9c4 -> 3680edf51)
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 ad7b2d9c4 generate docs for fcd28e0f add 4d3ddc0d2 ninja-fix link in Cassandra Day China to Azul new 3680edf51 generate docs for 4d3ddc0d 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 (ad7b2d9c4) \ N -- N -- N refs/heads/asf-staging (3680edf51) 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: content/_/events/20221222-cday-china.html | 4 ++-- content/search-index.js| 2 +- .../ROOT/pages/events/20221222-cday-china.adoc | 4 ++-- site-ui/build/ui-bundle.zip| Bin 4970898 -> 4970898 bytes 4 files changed, 5 insertions(+), 5 deletions(-) - 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 (2f54b3a6a -> ad7b2d9c4)
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 2f54b3a6a generate docs for fcd28e0f new ad7b2d9c4 generate docs for fcd28e0f 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 (2f54b3a6a) \ N -- N -- N refs/heads/asf-staging (ad7b2d9c4) 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: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4970898 -> 4970898 bytes 2 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
[cassandra-website] branch trunk updated: ninja-fix link in Cassandra Day China to Azul
This is an automated email from the ASF dual-hosted git repository. mck 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 4d3ddc0d ninja-fix link in Cassandra Day China to Azul 4d3ddc0d is described below commit 4d3ddc0d28627007d7cd80fa004333931e244e11 Author: mck AuthorDate: Tue Dec 13 21:45:27 2022 -0800 ninja-fix link in Cassandra Day China to Azul --- .../source/modules/ROOT/pages/events/20221222-cday-china.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/site-content/source/modules/ROOT/pages/events/20221222-cday-china.adoc b/site-content/source/modules/ROOT/pages/events/20221222-cday-china.adoc index 4147f953..a51efc04 100644 --- a/site-content/source/modules/ROOT/pages/events/20221222-cday-china.adoc +++ b/site-content/source/modules/ROOT/pages/events/20221222-cday-china.adoc @@ -64,7 +64,7 @@ Cassandra Day China 2022将为您揭晓！ Apache Cassandra是一个开源的NoSQL分布式数据库，在不影响性能的情况下，其可扩展性和高可用性受到数千家公司的信赖。常见硬件或云基础设施上的线性可扩展性和经验证的容错能力使其成为任务关键型数据的完美平台。 -为帮助更更多开发者了解Cassandra，Cassandra Day China 2022将于12月22日在线上举行，并将邀请来自 http://www.itcgb.com[中达金桥^]、 https://www.mgtv.com/[芒果TV^]、 https://www.360.cn/[360^]、 https://www.azul.com/[Azul^]、 https://www.huawei.com/[华为^]、 https://www.intel.com/[Intel Corporation^], https://www.datastax.com/[DataStax^]等知名企业的技术专家，为大家从实际使用角度带来Cassandra的相关应用经验分享，助力更多开发者构建更便捷、安全易用的应用与数据库，发现更多可能！会上更有专家问答、幸运抽奖等环节，诚邀各位开发者拨冗参会！ +为帮助更更多开发者了解Cassandra，Cassandra Day China 2022将于12月22日在线上举行，并将邀请来自 http://www.itcgb.com[中达金桥^]、 https://www.mgtv.com/[芒果TV^]、 https://www.360.cn/[360^]、 https://https://www.azul.com/zh-hans/[Azul^]、 https://www.huawei.com/[华为^]、 https://www.intel.com/[Intel Corporation^], https://www.datastax.com/[DataStax^]等知名企业的技术专家，为大家从实际使用角度带来Cassandra的相关应用经验分享，助力更多开发者构建更便捷、安全易用的应用与数据库，发现更多可能！会上更有专家问答、幸运抽奖等环节，诚邀各位开发者拨冗参会！ === 日程 @@ -78,7 +78,7 @@ Apache Cassandra是一个开源的NoSQL分布式数据库，在不影响性能 === 致谢 -非常感谢活动赞助商 https://www.azul.com/[Azul Systems^]和 https://www.intel.com/[Intel Corporation^]，以及 http://www.itcgb.com[中达金桥^]和 https://www.apache.org/[Apache软件基金会的支持^]。 +非常感谢活动赞助商 https://www.azul.com/zh-hans/[Azul Systems^]和 https://www.intel.com/[Intel Corporation^]，以及 http://www.itcgb.com[中达金桥^]和 https://www.apache.org/[Apache软件基金会的支持^]。 === 反骚扰政策 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18112) Add the feature of INDEX HINT for CQL
[ https://issues.apache.org/jira/browse/CASSANDRA-18112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646908#comment-17646908 ] maxwellguo commented on CASSANDRA-18112: Besides I think the Hint feature is not limited to Index Hint , can be extends to others , see https://phoenix.apache.org/language/index.html#hint and mysql hint https://dev.mysql.com/doc/refman/8.0/en/optimizer-hints.html , so in the future the hint can be extends to some what CQL's hint for cassandra. > Add the feature of INDEX HINT for CQL > -- > > Key: CASSANDRA-18112 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18112 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Syntax, Feature/2i Index >Reporter: maxwellguo >Priority: Normal > > It seems that CQL do not have the ability of INDEX HINT , such as when we > have more than one secondary index for some data table,And if the query hit > the indexes, the index with more estimate rows will be returned. But if we > want the query to be executed under our willing , we can use a hint like > ,hint specified index or ignore the index. > At first I want to open a jira that to add the feature of hint for CQL ,But I > think that may be a gigantic task with no clear goal. > Besides I think there may need a DISSCUSS for the specific grammatical form > before starting the work. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18112) Add the feature of INDEX HINT for CQL
[ https://issues.apache.org/jira/browse/CASSANDRA-18112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646894#comment-17646894 ] maxwellguo edited comment on CASSANDRA-18112 at 12/14/22 2:07 AM: -- Hey [~maedhroz], thanks for your reply . CASSANDRA-16052 is a great job, and I am looking forward to it from the time the cep is created. As you have saied, So that means there is no need for cql to add this feature？for us we have encountered similar needs ，that is why this jira was created. besides the secondary index will evolute and finnally the index can be production-usable. So the feature may be needed sonner or latter. and this feature does not blocked by CASSANDRA-16052 ，right？☺️☺️☺️ was (Author: maxwellguo): Hey [~maedhroz], thanks for your reply . So that means there is no need for cql to add this feature？for us we have encountered similar needs ，that is why this jira was created. besides the secondary index will evolute and finnally the index can be production-usable. So the feature may be needed sonner or latter. and this feature does not blocked by CASSANDRA-16052 ，right？☺️☺️☺️ > Add the feature of INDEX HINT for CQL > -- > > Key: CASSANDRA-18112 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18112 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Syntax, Feature/2i Index >Reporter: maxwellguo >Priority: Normal > > It seems that CQL do not have the ability of INDEX HINT , such as when we > have more than one secondary index for some data table,And if the query hit > the indexes, the index with more estimate rows will be returned. But if we > want the query to be executed under our willing , we can use a hint like > ,hint specified index or ignore the index. > At first I want to open a jira that to add the feature of hint for CQL ,But I > think that may be a gigantic task with no clear goal. > Besides I think there may need a DISSCUSS for the specific grammatical form > before starting the work. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18112) Add the feature of INDEX HINT for CQL
[ https://issues.apache.org/jira/browse/CASSANDRA-18112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646894#comment-17646894 ] maxwellguo edited comment on CASSANDRA-18112 at 12/14/22 2:04 AM: -- Hey [~maedhroz], thanks for your reply . So that means there is no need for cql to add this feature？for us we have encountered similar needs ，that is why this jira was created. besides the secondary index will evolute and finnally the index can be production-usable. So the feature may be needed sonner or latter. and this feature does not blocked by CASSANDRA-16052 ，right？☺️☺️☺️ was (Author: maxwellguo): so that means there is no need for cql to add this feature？for us we have encountered similar needs ，that is why this jira was created. besides the secondary index will evolute and finnally the index can be production-usable. So the feature may be needed sonner or latter. and this feature does not blocked by CASSANDRA-16052 ，right？☺️☺️☺️ > Add the feature of INDEX HINT for CQL > -- > > Key: CASSANDRA-18112 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18112 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Syntax, Feature/2i Index >Reporter: maxwellguo >Priority: Normal > > It seems that CQL do not have the ability of INDEX HINT , such as when we > have more than one secondary index for some data table,And if the query hit > the indexes, the index with more estimate rows will be returned. But if we > want the query to be executed under our willing , we can use a hint like > ,hint specified index or ignore the index. > At first I want to open a jira that to add the feature of hint for CQL ,But I > think that may be a gigantic task with no clear goal. > Besides I think there may need a DISSCUSS for the specific grammatical form > before starting the work. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18112) Add the feature of INDEX HINT for CQL
[ https://issues.apache.org/jira/browse/CASSANDRA-18112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646894#comment-17646894 ] maxwellguo commented on CASSANDRA-18112: so that means there is no need for cql to add this feature？for us we have encountered similar needs ，that is why this jira was created. besides the secondary index will evolute and finnally the index can be production-usable. So the feature may be needed sonner or latter. and this feature does not blocked by CASSANDRA-16052 ，right？☺️☺️☺️ > Add the feature of INDEX HINT for CQL > -- > > Key: CASSANDRA-18112 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18112 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Syntax, Feature/2i Index >Reporter: maxwellguo >Priority: Normal > > It seems that CQL do not have the ability of INDEX HINT , such as when we > have more than one secondary index for some data table,And if the query hit > the indexes, the index with more estimate rows will be returned. But if we > want the query to be executed under our willing , we can use a hint like > ,hint specified index or ignore the index. > At first I want to open a jira that to add the feature of hint for CQL ,But I > think that may be a gigantic task with no clear goal. > Besides I think there may need a DISSCUSS for the specific grammatical form > before starting the work. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17178) CEP-10: Simulator Java11 Support
[ https://issues.apache.org/jira/browse/CASSANDRA-17178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-17178: -- Fix Version/s: 4.2 (was: NA) Source Control Link: https://github.com/apache/cassandra/commit/4941b279bceb3a0fbe388be4305d25ec771f7b78 Resolution: Fixed Status: Resolved (was: Ready to Commit) > CEP-10: Simulator Java11 Support > > > Key: CASSANDRA-17178 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17178 > Project: Cassandra > Issue Type: Task > Components: Test/fuzz >Reporter: Benedict Elliott Smith >Assignee: David Capwell >Priority: Normal > Fix For: 4.2 > > > Java11 introduces new protection domains for package private methods, so that > classes loaded with different class loaders may not access each others’ > package private methods, regardless of the package they are declared within. > There are differences within the JDK also, and there may be byte weaving > targets that need updating (ThreadLocalRandom was one that has been handled) -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated: CEP-10: Simulator Java11 Support
This is an automated email from the ASF dual-hosted git repository. dcapwell pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/trunk by this push: new 4941b279bc CEP-10: Simulator Java11 Support 4941b279bc is described below commit 4941b279bceb3a0fbe388be4305d25ec771f7b78 Author: David Capwell AuthorDate: Tue Dec 13 13:37:40 2022 -0800 CEP-10: Simulator Java11 Support patch by David Capwell; reviewed by Benedict Elliott Smith, Ekaterina Dimitrova for CASSANDRA-17178 --- .circleci/config-2_1.yml | 35 .circleci/config-2_1.yml.high_res.patch| 12 +- .circleci/config-2_1.yml.mid_res.patch | 50 ++--- .circleci/config.yml | 217 + .circleci/config.yml.HIGHRES | 217 + .circleci/config.yml.LOWRES| 217 + .circleci/config.yml.MIDRES| 217 + CHANGES.txt| 1 + build.xml | 23 ++- .../cassandra/simulator/asm/ClassTransformer.java | 51 - .../cassandra/simulator/asm/InterceptAgent.java| 6 +- .../cassandra/simulator/asm/InterceptClasses.java | 1 + .../org/apache/cassandra/simulator/asm/Utils.java | 8 + .../simulator/test/ShortPaxosSimulationTest.java | 1 + 14 files changed, 1017 insertions(+), 39 deletions(-) diff --git a/.circleci/config-2_1.yml b/.circleci/config-2_1.yml index 6e695e1930..0ec3e98fc6 100644 --- a/.circleci/config-2_1.yml +++ b/.circleci/config-2_1.yml @@ -1164,6 +1164,18 @@ j11_separate_jobs: _separate_jobs requires: - start_j11_jvm_dtests_vnode_repeat - j11_build +- start_j11_simulator_dtests: +type: approval +- j11_simulator_dtests: +requires: + - start_j11_simulator_dtests + - j11_build +- start_j11_simulator_dtests_repeat: +type: approval +- j11_simulator_dtests_repeat: +requires: + - start_j11_simulator_dtests_repeat + - j11_build - start_j11_cqlshlib_tests: type: approval - j11_cqlshlib_tests: @@ -1384,6 +1396,12 @@ j11_pre-commit_jobs: _pre-commit_jobs - j11_jvm_dtests_vnode_repeat: requires: - j11_build +- j11_simulator_dtests: +requires: + - j11_build +- j11_simulator_dtests_repeat: +requires: + - j11_build - j11_cqlshlib_tests: requires: - j11_build @@ -1623,6 +1641,15 @@ jobs: - log_environment - run_simulator_tests + j11_simulator_dtests: +<<: *j11_small_executor +steps: + - attach_workspace: + at: /home/cassandra + - create_junit_containers + - log_environment + - run_simulator_tests + j8_jvm_dtests: <<: *j8_small_par_executor steps: @@ -2362,6 +2389,14 @@ jobs: - log_environment - run_simulator_dtests_repeat + j11_simulator_dtests_repeat: +<<: *j11_repeated_utest_executor +steps: + - attach_workspace: + at: /home/cassandra + - log_environment + - run_simulator_dtests_repeat + j8_jvm_upgrade_dtests_repeat: <<: *j8_repeated_jvm_upgrade_dtest_executor steps: diff --git a/.circleci/config-2_1.yml.high_res.patch b/.circleci/config-2_1.yml.high_res.patch index 7da8d902fb..376471d7e2 100644 --- a/.circleci/config-2_1.yml.high_res.patch +++ b/.circleci/config-2_1.yml.high_res.patch @@ -1,5 +1,5 @@ config-2_1.yml 2022-11-15 12:54:54.0 -0500 -+++ config-2_1.yml.HIGHRES 2022-11-15 12:56:26.0 -0500 +--- config-2_1.yml 2022-12-13 13:30:41.0 -0800 config-2_1.yml.HIGHRES 2022-12-13 13:31:44.0 -0800 @@ -158,14 +158,14 @@ j8_par_executor: _par_executor executor: @@ -111,7 +111,7 @@ j8_separate_jobs: _separate_jobs jobs: -@@ -2155,7 +2161,7 @@ +@@ -2182,7 +2188,7 @@ python_version: '3.8' j8_dtests_large_vnode: @@ -120,7 +120,7 @@ steps: - attach_workspace: at: /home/cassandra -@@ -2169,7 +2175,7 @@ +@@ -2196,7 +2202,7 @@ pytest_extra_args: '--use-vnodes --num-tokens=16 --only-resource-intensive-tests --force-resource-intensive-tests' j8_dtests_large: @@ -129,7 +129,7 @@ steps: - attach_workspace: at: /home/cassandra -@@ -2183,7 +2189,7 @@ +@@ -2210,7 +2216,7 @@ pytest_extra_args: '--only-resource-intensive-tests --force-resource-intensive-tests' j11_dtests_large_vnode: @@ -138,7 +138,7 @@ steps: - attach_workspace: at: /home/cassandra -@@ -2197,7 +2203,7 @@ +@@ -2224,7 +2230,7 @@ pytest_extra_args: '--use-vnodes --num-tokens=16 --only-resource-intensive-tests
[jira] [Commented] (CASSANDRA-18077) Add SpotBugs to the build
[ https://issues.apache.org/jira/browse/CASSANDRA-18077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646841#comment-17646841 ] David Capwell commented on CASSANDRA-18077: --- [~e.dimitrova] I honestly don't have the time to follow through with the feedback you are requesting... so I will need to stop trying to add SpotBugs. I can depend on CASSANDRA-17964 and move the serializer check into ant, this would solve the simulator issue at least > Add SpotBugs to the build > - > > Key: CASSANDRA-18077 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18077 > Project: Cassandra > Issue Type: Improvement > Components: Build, CI >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 4.x > > Attachments: spotbugs.html > > Time Spent: 50m > Remaining Estimate: 0h > > When working on CASSANDRA-17178 I found that several classes were being > reported by the Simulator for not defining serializer version when they are > Serializable; this may cause issues for the Simulator so felt it would be > best to detect these earlier on before merging new ones. > SpotBugs has a large set of checks, some more valuable than others for the > project; so we should maintain a curated list of issues to fail the build on, > and others to warn on. > This topic was discussed in the following mail threads: > * Should we add?: > https://lists.apache.org/thread/1ro1mvkpvt4vr24nw7dbpdlxo82mq3hz > * Should we fix UTF-8 issues? > https://lists.apache.org/thread/sokxf46s7hyoxr9q4wm7dv3q2nm19nt3 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17964) Some tests are never executed due to naming violation - fix it and add checkstyle where applicable
[ https://issues.apache.org/jira/browse/CASSANDRA-17964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646838#comment-17646838 ] David Capwell commented on CASSANDRA-17964: --- 4.1 is out, looking forward to this! > Some tests are never executed due to naming violation - fix it and add > checkstyle where applicable > -- > > Key: CASSANDRA-17964 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17964 > Project: Cassandra > Issue Type: Task > Components: Test/unit >Reporter: Ruslan Fomkin >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 4.x > > Time Spent: 2h 40m > Remaining Estimate: 0h > > [BatchTests|https://github.com/apache/cassandra/blob/trunk/test/unit/org/apache/cassandra/cql3/BatchTests.java] > doesn't follow naming convention to be run as unit tests and, thus, is never > run. > The rule in build expects names as `*Test`. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18115) WEBSITE - Fix text labels for C* versions on Download page
[ https://issues.apache.org/jira/browse/CASSANDRA-18115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646834#comment-17646834 ] Erick Ramirez commented on CASSANDRA-18115: --- The updated page is now live on the site – [https://cassandra.apache.org/_/download.html.] Thanks [~mck] for the quick fix! > WEBSITE - Fix text labels for C* versions on Download page > -- > > Key: CASSANDRA-18115 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18115 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Erick Ramirez >Assignee: Michael Semb Wever >Priority: Normal > Fix For: NA > > Attachments: c18115-01-download.png, image.png > > > The text labels for the C* versions on the Download page need to be updated > with the release of C* 4.1 this morning. > !image.png|width=300! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18077) Add SpotBugs to the build
[ https://issues.apache.org/jira/browse/CASSANDRA-18077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-18077: -- Fix Version/s: 4.x (was: NA) > Add SpotBugs to the build > - > > Key: CASSANDRA-18077 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18077 > Project: Cassandra > Issue Type: Improvement > Components: Build, CI >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 4.x > > Attachments: spotbugs.html > > Time Spent: 50m > Remaining Estimate: 0h > > When working on CASSANDRA-17178 I found that several classes were being > reported by the Simulator for not defining serializer version when they are > Serializable; this may cause issues for the Simulator so felt it would be > best to detect these earlier on before merging new ones. > SpotBugs has a large set of checks, some more valuable than others for the > project; so we should maintain a curated list of issues to fail the build on, > and others to warn on. > This topic was discussed in the following mail threads: > * Should we add?: > https://lists.apache.org/thread/1ro1mvkpvt4vr24nw7dbpdlxo82mq3hz > * Should we fix UTF-8 issues? > https://lists.apache.org/thread/sokxf46s7hyoxr9q4wm7dv3q2nm19nt3 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-site updated (b2ceec70 -> 2f54b3a6)
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 b2ceec70 generate docs for dc9c4ad8 add fcd28e0f ninja-fix downloads for 4.0.7 and 3.11.14 add 2f54b3a6 generate docs for fcd28e0f 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 (b2ceec70) \ N -- N -- N refs/heads/asf-site (2f54b3a6) 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: content/_/download.html| 8 .../source/modules/ROOT/pages/download.adoc| 8 site-ui/build/ui-bundle.zip| Bin 4970898 -> 4970898 bytes 3 files changed, 8 insertions(+), 8 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17178) CEP-10: Simulator Java11 Support
[ https://issues.apache.org/jira/browse/CASSANDRA-17178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646832#comment-17646832 ] David Capwell commented on CASSANDRA-17178: --- Starting commit CI Results (pending): ||Branch||Source||Circle CI||Jenkins|| |trunk|[branch|https://github.com/dcapwell/cassandra/tree/commit_remote_branch/CASSANDRA-17178-trunk-85E6B0BD-18BA-4BCA-BCDB-990D442D1248]|[build|https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-17178-trunk-85E6B0BD-18BA-4BCA-BCDB-990D442D1248]|[build|https://ci-cassandra.apache.org/job/Cassandra-devbranch/2102/]| > CEP-10: Simulator Java11 Support > > > Key: CASSANDRA-17178 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17178 > Project: Cassandra > Issue Type: Task > Components: Test/fuzz >Reporter: Benedict Elliott Smith >Assignee: David Capwell >Priority: Normal > Fix For: NA > > > Java11 introduces new protection domains for package private methods, so that > classes loaded with different class loaders may not access each others’ > package private methods, regardless of the package they are declared within. > There are differences within the JDK also, and there may be byte weaving > targets that need updating (ThreadLocalRandom was one that has been handled) -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17178) CEP-10: Simulator Java11 Support
[ https://issues.apache.org/jira/browse/CASSANDRA-17178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-17178: -- Status: Ready to Commit (was: Review In Progress) > CEP-10: Simulator Java11 Support > > > Key: CASSANDRA-17178 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17178 > Project: Cassandra > Issue Type: Task > Components: Test/fuzz >Reporter: Benedict Elliott Smith >Assignee: David Capwell >Priority: Normal > Fix For: NA > > > Java11 introduces new protection domains for package private methods, so that > classes loaded with different class loaders may not access each others’ > package private methods, regardless of the package they are declared within. > There are differences within the JDK also, and there may be byte weaving > targets that need updating (ThreadLocalRandom was one that has been handled) -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18115) WEBSITE - Fix text labels for C* versions on Download page
[ https://issues.apache.org/jira/browse/CASSANDRA-18115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646829#comment-17646829 ] Erick Ramirez commented on CASSANDRA-18115: --- I've verified the fix in staging and it's ready to push to production: https://cassandra.staged.apache.org/_/download.html !c18115-01-download.png|width=300! > WEBSITE - Fix text labels for C* versions on Download page > -- > > Key: CASSANDRA-18115 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18115 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Erick Ramirez >Assignee: Michael Semb Wever >Priority: Normal > Fix For: NA > > Attachments: c18115-01-download.png, image.png > > > The text labels for the C* versions on the Download page need to be updated > with the release of C* 4.1 this morning. > !image.png|width=300! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17178) CEP-10: Simulator Java11 Support
[
https://issues.apache.org/jira/browse/CASSANDRA-17178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646828#comment-17646828
]
David Capwell commented on CASSANDRA-17178:
---
Updated patches and saw
{code}
$ git st
On branch CASSANDRA-17178
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git restore ..." to discard changes in working directory)
modified: config-2_1.yml.high_res.patch
modified: config-2_1.yml.mid_res.patch
{code}
ran generate
{code}
$ ./generate.sh -a
Generating new config.yml file with low resources and LOWRES/MIDRES/HIGHRES
templates from config-2_1.yml
gpatching file ./config-2_1.yml
patching file ./config-2_1.yml
{code}
I did have to modify each yaml it generates as the bug I reported isn't fixed,
so it adds non-yaml... once I cleanup the error msg in the output I get
{code}
$ git st
On branch CASSANDRA-17178
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git restore ..." to discard changes in working directory)
modified: config-2_1.yml.high_res.patch
modified: config-2_1.yml.mid_res.patch
modified: config.yml
{code}
config.yml is different as it overrides my changes to enable CI, main takeaway
is that LOW/MID/HIGH are not changed
> CEP-10: Simulator Java11 Support
>
>
> Key: CASSANDRA-17178
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17178
> Project: Cassandra
> Issue Type: Task
> Components: Test/fuzz
>Reporter: Benedict Elliott Smith
>Assignee: David Capwell
>Priority: Normal
> Fix For: NA
>
>
> Java11 introduces new protection domains for package private methods, so that
> classes loaded with different class loaders may not access each others’
> package private methods, regardless of the package they are declared within.
> There are differences within the JDK also, and there may be byte weaving
> targets that need updating (ThreadLocalRandom was one that has been handled)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18115) WEBSITE - Fix text labels for C* versions on Download page
[ https://issues.apache.org/jira/browse/CASSANDRA-18115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646827#comment-17646827 ] Erick Ramirez commented on CASSANDRA-18115: --- Fixed committed by [~mck] as [fcd28e0|https://github.com/apache/cassandra-website/commit/fcd28e0fbd3824004b5ce74cfc9ff282b524bd59]. > WEBSITE - Fix text labels for C* versions on Download page > -- > > Key: CASSANDRA-18115 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18115 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Erick Ramirez >Assignee: Michael Semb Wever >Priority: Normal > Fix For: NA > > Attachments: c18115-01-download.png, image.png > > > The text labels for the C* versions on the Download page need to be updated > with the release of C* 4.1 this morning. > !image.png|width=300! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18115) WEBSITE - Fix text labels for C* versions on Download page
[ https://issues.apache.org/jira/browse/CASSANDRA-18115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-18115: -- Source Control Link: https://github.com/apache/cassandra-website/commit/fcd28e0fbd3824004b5ce74cfc9ff282b524bd59 > WEBSITE - Fix text labels for C* versions on Download page > -- > > Key: CASSANDRA-18115 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18115 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Erick Ramirez >Assignee: Michael Semb Wever >Priority: Normal > Fix For: NA > > Attachments: c18115-01-download.png, image.png > > > The text labels for the C* versions on the Download page need to be updated > with the release of C* 4.1 this morning. > !image.png|width=300! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18115) WEBSITE - Fix text labels for C* versions on Download page
[ https://issues.apache.org/jira/browse/CASSANDRA-18115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-18115: -- Reviewers: Erick Ramirez (was: Michael Semb Wever) > WEBSITE - Fix text labels for C* versions on Download page > -- > > Key: CASSANDRA-18115 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18115 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Erick Ramirez >Assignee: Michael Semb Wever >Priority: Normal > Fix For: NA > > Attachments: c18115-01-download.png, image.png > > > The text labels for the C* versions on the Download page need to be updated > with the release of C* 4.1 this morning. > !image.png|width=300! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-18115) WEBSITE - Fix text labels for C* versions on Download page
[ https://issues.apache.org/jira/browse/CASSANDRA-18115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez reassigned CASSANDRA-18115: - Assignee: Michael Semb Wever (was: Erick Ramirez) > WEBSITE - Fix text labels for C* versions on Download page > -- > > Key: CASSANDRA-18115 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18115 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Erick Ramirez >Assignee: Michael Semb Wever >Priority: Normal > Fix For: NA > > Attachments: c18115-01-download.png, image.png > > > The text labels for the C* versions on the Download page need to be updated > with the release of C* 4.1 this morning. > !image.png|width=300! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18115) WEBSITE - Fix text labels for C* versions on Download page
[ https://issues.apache.org/jira/browse/CASSANDRA-18115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-18115: -- Resolution: Fixed Status: Resolved (was: Open) > WEBSITE - Fix text labels for C* versions on Download page > -- > > Key: CASSANDRA-18115 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18115 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Erick Ramirez >Assignee: Michael Semb Wever >Priority: Normal > Fix For: NA > > Attachments: c18115-01-download.png, image.png > > > The text labels for the C* versions on the Download page need to be updated > with the release of C* 4.1 this morning. > !image.png|width=300! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18115) WEBSITE - Fix text labels for C* versions on Download page
[ https://issues.apache.org/jira/browse/CASSANDRA-18115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-18115: -- Attachment: c18115-01-download.png > WEBSITE - Fix text labels for C* versions on Download page > -- > > Key: CASSANDRA-18115 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18115 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Fix For: NA > > Attachments: c18115-01-download.png, image.png > > > The text labels for the C* versions on the Download page need to be updated > with the release of C* 4.1 this morning. > !image.png|width=300! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17850) Find a way to get FileDescriptor.fd and sun.nio.ch.FileChannelImpl.fd without opening internals
[
https://issues.apache.org/jira/browse/CASSANDRA-17850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17850:
Description:
With Java 17 if we do not add below to the jvm17 server options:
{code:java}
--add-opens java.base/sun.nio.ch=ALL-UNNAMED
--add-opens java.base/java.io=ALL-UNNAMED{code}
we get on startup (considering I comment out the scripted UDFs and apply a few
changes to the startup scripts):
{code:java}
ERROR [ScheduledTasks:1] 2022-08-23 12:29:25,652 JVMStabilityInspector.java:68
- Exception in thread Thread[ScheduledTasks:1,5,ScheduledTasks]
java.lang.AssertionError: java.lang.reflect.InaccessibleObjectException: Unable
to make field private int java.io.FileDescriptor.fd accessible: module
java.base does not "opens java.io" to unnamed module @11d8ae8b
at
org.apache.cassandra.utils.FBUtilities.getProtectedField(FBUtilities.java:801)
at org.apache.cassandra.utils.NativeLibrary.(NativeLibrary.java:84)
at org.apache.cassandra.utils.TimeUUID$Generator.hash(TimeUUID.java:496)
at org.apache.cassandra.utils.TimeUUID$Generator.makeNode(TimeUUID.java:474)
at
org.apache.cassandra.utils.TimeUUID$Generator.makeClockSeqAndNode(TimeUUID.java:452)
at org.apache.cassandra.utils.TimeUUID$Generator.(TimeUUID.java:368)
at
org.apache.cassandra.streaming.StreamingState.(StreamingState.java:50)
at org.apache.cassandra.streaming.StreamManager.(StreamManager.java:257)
at org.apache.cassandra.streaming.StreamManager.(StreamManager.java:58)
at org.apache.cassandra.service.StorageService.(StorageService.java:376)
at org.apache.cassandra.service.StorageService.(StorageService.java:226)
at
org.apache.cassandra.locator.DynamicEndpointSnitch.updateScores(DynamicEndpointSnitch.java:274)
at
org.apache.cassandra.locator.DynamicEndpointSnitch$1.run(DynamicEndpointSnitch.java:91)
at
org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make field
private int java.io.FileDescriptor.fd accessible: module java.base does not
"opens java.io" to unnamed module @11d8ae8b
at
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
at
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178)
at java.base/java.lang.reflect.Field.setAccessible(Field.java:172)
at
org.apache.cassandra.utils.FBUtilities.getProtectedField(FBUtilities.java:796)
... 20 common frames omitted
{code}
and
{code:java}
ERROR [ScheduledTasks:1] 2022-08-23 12:31:18,443 JVMStabilityInspector.java:68
- Exception in thread Thread[ScheduledTasks:1,5,ScheduledTasks]
java.lang.AssertionError: java.lang.reflect.InaccessibleObjectException: Unable
to make field private final java.io.FileDescriptor
sun.nio.ch.FileChannelImpl.fd accessible: module java.base does not "opens
sun.nio.ch" to unnamed module @4c012563
at
org.apache.cassandra.utils.FBUtilities.getProtectedField(FBUtilities.java:801)
at org.apache.cassandra.utils.NativeLibrary.(NativeLibrary.java:87)
at org.apache.cassandra.utils.TimeUUID$Generator.hash(TimeUUID.java:496)
at org.apache.cassandra.utils.TimeUUID$Generator.makeNode(TimeUUID.java:474)
at
org.apache.cassandra.utils.TimeUUID$Generator.makeClockSeqAndNode(TimeUUID.java:452)
at org.apache.cassandra.utils.TimeUUID$Generator.(TimeUUID.java:368)
at
org.apache.cassandra.streaming.StreamingState.(StreamingState.java:50)
at org.apache.cassandra.streaming.StreamManager.(StreamManager.java:257)
at org.apache.cassandra.streaming.StreamManager.(StreamManager.java:58)
at org.apache.cassandra.service.StorageService.(StorageService.java:376)
at org.apache.cassandra.service.StorageService.(StorageService.java:226)
at
org.apache.cassandra.locator.DynamicEndpointSnitch.updateScores(DynamicEndpointSnitch.java:274)
at
org.apache.cassandra.locator.DynamicEndpointSnitch$1.run(DynamicEndpointSnitch.java:91)
at
org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at
[jira] [Updated] (CASSANDRA-17850) Find a way to get FileDescriptor.fd and sun.nio.ch.FileChannelImpl.fd without opening internals
[
https://issues.apache.org/jira/browse/CASSANDRA-17850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17850:
Description:
With Java 17 if we do not add below to the jvm17 server options:
{code:java}
--add-opens java.base/sun.nio.ch=ALL-UNNAMED
--add-opens java.base/java.io=ALL-UNNAMED{code}
we get on startup (considering I comment out the scripted UDFs and apply a few
changes to the startup scripts):
{code:java}
ERROR [ScheduledTasks:1] 2022-08-23 12:29:25,652 JVMStabilityInspector.java:68
- Exception in thread Thread[ScheduledTasks:1,5,ScheduledTasks]
java.lang.AssertionError: java.lang.reflect.InaccessibleObjectException: Unable
to make field private int java.io.FileDescriptor.fd accessible: module
java.base does not "opens java.io" to unnamed module @11d8ae8b
at
org.apache.cassandra.utils.FBUtilities.getProtectedField(FBUtilities.java:801)
at org.apache.cassandra.utils.NativeLibrary.(NativeLibrary.java:84)
at org.apache.cassandra.utils.TimeUUID$Generator.hash(TimeUUID.java:496)
at org.apache.cassandra.utils.TimeUUID$Generator.makeNode(TimeUUID.java:474)
at
org.apache.cassandra.utils.TimeUUID$Generator.makeClockSeqAndNode(TimeUUID.java:452)
at org.apache.cassandra.utils.TimeUUID$Generator.(TimeUUID.java:368)
at
org.apache.cassandra.streaming.StreamingState.(StreamingState.java:50)
at org.apache.cassandra.streaming.StreamManager.(StreamManager.java:257)
at org.apache.cassandra.streaming.StreamManager.(StreamManager.java:58)
at org.apache.cassandra.service.StorageService.(StorageService.java:376)
at org.apache.cassandra.service.StorageService.(StorageService.java:226)
at
org.apache.cassandra.locator.DynamicEndpointSnitch.updateScores(DynamicEndpointSnitch.java:274)
at
org.apache.cassandra.locator.DynamicEndpointSnitch$1.run(DynamicEndpointSnitch.java:91)
at
org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make field
private int java.io.FileDescriptor.fd accessible: module java.base does not
"opens java.io" to unnamed module @11d8ae8b
at
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
at
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178)
at java.base/java.lang.reflect.Field.setAccessible(Field.java:172)
at
org.apache.cassandra.utils.FBUtilities.getProtectedField(FBUtilities.java:796)
... 20 common frames omitted
{code}
and
{code:java}
ERROR [ScheduledTasks:1] 2022-08-23 12:31:18,443 JVMStabilityInspector.java:68
- Exception in thread Thread[ScheduledTasks:1,5,ScheduledTasks]
java.lang.AssertionError: java.lang.reflect.InaccessibleObjectException: Unable
to make field private final java.io.FileDescriptor
sun.nio.ch.FileChannelImpl.fd accessible: module java.base does not "opens
sun.nio.ch" to unnamed module @4c012563
at
org.apache.cassandra.utils.FBUtilities.getProtectedField(FBUtilities.java:801)
at org.apache.cassandra.utils.NativeLibrary.(NativeLibrary.java:87)
at org.apache.cassandra.utils.TimeUUID$Generator.hash(TimeUUID.java:496)
at org.apache.cassandra.utils.TimeUUID$Generator.makeNode(TimeUUID.java:474)
at
org.apache.cassandra.utils.TimeUUID$Generator.makeClockSeqAndNode(TimeUUID.java:452)
at org.apache.cassandra.utils.TimeUUID$Generator.(TimeUUID.java:368)
at
org.apache.cassandra.streaming.StreamingState.(StreamingState.java:50)
at org.apache.cassandra.streaming.StreamManager.(StreamManager.java:257)
at org.apache.cassandra.streaming.StreamManager.(StreamManager.java:58)
at org.apache.cassandra.service.StorageService.(StorageService.java:376)
at org.apache.cassandra.service.StorageService.(StorageService.java:226)
at
org.apache.cassandra.locator.DynamicEndpointSnitch.updateScores(DynamicEndpointSnitch.java:274)
at
org.apache.cassandra.locator.DynamicEndpointSnitch$1.run(DynamicEndpointSnitch.java:91)
at
org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at
[cassandra-website] branch asf-staging updated (b2ceec70 -> 2f54b3a6)
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 b2ceec70 generate docs for dc9c4ad8 add fcd28e0f ninja-fix downloads for 4.0.7 and 3.11.14 new 2f54b3a6 generate docs for fcd28e0f 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 (b2ceec70) \ N -- N -- N refs/heads/asf-staging (2f54b3a6) 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: content/_/download.html| 8 .../source/modules/ROOT/pages/download.adoc| 8 site-ui/build/ui-bundle.zip| Bin 4970898 -> 4970898 bytes 3 files changed, 8 insertions(+), 8 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18116) Denylist can load perpetually and too frequently if it fails persistently
[ https://issues.apache.org/jira/browse/CASSANDRA-18116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan West updated CASSANDRA-18116: Bug Category: Parent values: Degradation(12984)Level 1 values: Other Exception(12998) Complexity: Low Hanging Fruit Component/s: Feature/Rate Limiting Discovered By: User Report Fix Version/s: 4.0.x 4.1.x Severity: Normal Status: Open (was: Triage Needed) > Denylist can load perpetually and too frequently if it fails persistently > -- > > Key: CASSANDRA-18116 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18116 > Project: Cassandra > Issue Type: Bug > Components: Feature/Rate Limiting >Reporter: Jordan West >Assignee: Jordan West >Priority: Normal > Fix For: 4.0.x, 4.1.x > > > When the denylist fails its initial load it can [return a value of > null|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/schema/PartitionDenylist.java#L453] > for a key in the cache. The [BoundedLoadingCache > implementation|https://github.com/ben-manes/caffeine/blob/master/caffeine/src/main/java/com/github/benmanes/caffeine/cache/BoundedLocalCache.java#L2591-L2615] > that is used treats null as missing and will end up trying to load the key > on reads. Besides the performance impact this can also lead to significant > log spam leading to disk or CPU usage issues. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-18116) Denylist can load perpetually and too frequently if it fails persistently
Jordan West created CASSANDRA-18116: --- Summary: Denylist can load perpetually and too frequently if it fails persistently Key: CASSANDRA-18116 URL: https://issues.apache.org/jira/browse/CASSANDRA-18116 Project: Cassandra Issue Type: Bug Reporter: Jordan West Assignee: Jordan West When the denylist fails its initial load it can [return a value of null|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/schema/PartitionDenylist.java#L453] for a key in the cache. The [BoundedLoadingCache implementation|https://github.com/ben-manes/caffeine/blob/master/caffeine/src/main/java/com/github/benmanes/caffeine/cache/BoundedLocalCache.java#L2591-L2615] that is used treats null as missing and will end up trying to load the key on reads. Besides the performance impact this can also lead to significant log spam leading to disk or CPU usage issues. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch trunk updated: ninja-fix downloads for 4.0.7 and 3.11.14
This is an automated email from the ASF dual-hosted git repository. mck 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 fcd28e0f ninja-fix downloads for 4.0.7 and 3.11.14 fcd28e0f is described below commit fcd28e0fbd3824004b5ce74cfc9ff282b524bd59 Author: mck AuthorDate: Tue Dec 13 12:06:12 2022 -0800 ninja-fix downloads for 4.0.7 and 3.11.14 --- site-content/source/modules/ROOT/pages/download.adoc | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/site-content/source/modules/ROOT/pages/download.adoc b/site-content/source/modules/ROOT/pages/download.adoc index 0f6764e7..499a7fa3 100644 --- a/site-content/source/modules/ROOT/pages/download.adoc +++ b/site-content/source/modules/ROOT/pages/download.adoc @@ -40,9 +40,9 @@ https://www.apache.org/dyn/closer.lua/cassandra/4.1.0/apache-cassandra-4.1.0-bin Maintained until 4.3.0 release (May-July 2024) [.btn.btn--alt] -https://www.apache.org/dyn/closer.lua/cassandra/3.11.14/apache-cassandra-3.11.14-bin.tar.gz[3.11.14,window=blank] +https://www.apache.org/dyn/closer.lua/cassandra/4.0.7/apache-cassandra-4.0.7-bin.tar.gz[4.0.7,window=blank] -(https://downloads.apache.org/cassandra/3.11.14/apache-cassandra-3.11.14-bin.tar.gz.asc[pgp,window=blank], https://downloads.apache.org/cassandra/3.11.14/apache-cassandra-3.11.14-bin.tar.gz.sha256[sha256,window=blank] and https://downloads.apache.org/cassandra/3.11.14/apache-cassandra-3.11.14-bin.tar.gz.sha512[sha512,window=blank]) +(https://downloads.apache.org/cassandra/4.0.7/apache-cassandra-4.0.7-bin.tar.gz.asc[pgp,window=blank], https://downloads.apache.org/cassandra/4.0.7/apache-cassandra-4.0.7-bin.tar.gz.sha256[sha256,window=blank] and https://downloads.apache.org/cassandra/4.0.7/apache-cassandra-4.0.7-bin.tar.gz.sha512[sha512,window=blank]) -- [openblock, inline100 inline-top] @@ -65,9 +65,9 @@ The following older Cassandra releases are still supported: Maintained until 4.2.0 release (May-July 2023) [.btn.btn--alt] -https://www.apache.org/dyn/closer.lua/cassandra/3.0.28/apache-cassandra-3.0.28-bin.tar.gz[3.0.28,window=blank] +https://www.apache.org/dyn/closer.lua/cassandra/3.11.14/apache-cassandra-3.11.14-bin.tar.gz[3.11.14,window=blank] -(https://downloads.apache.org/cassandra/3.0.28/apache-cassandra-3.0.28-bin.tar.gz.asc[pgp,window=blank], https://downloads.apache.org/cassandra/3.0.28/apache-cassandra-3.0.28-bin.tar.gz.sha256[sha256,window=blank] and https://downloads.apache.org/cassandra/3.0.28/apache-cassandra-3.0.28-bin.tar.gz.sha512[sha512,window=blank]) +(https://downloads.apache.org/cassandra/3.11.14/apache-cassandra-3.11.14-bin.tar.gz.asc[pgp,window=blank], https://downloads.apache.org/cassandra/3.11.14/apache-cassandra-3.11.14-bin.tar.gz.sha256[sha256,window=blank] and https://downloads.apache.org/cassandra/3.11.14/apache-cassandra-3.11.14-bin.tar.gz.sha512[sha512,window=blank]) -- [openblock, inline50 inline-top] - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cep-15-accord updated: Ninja for CASSANDRA-17719: TransactionStatement now logs every exception, will revert before trunk but needed for debugging
This is an automated email from the ASF dual-hosted git repository.
dcapwell pushed a commit to branch cep-15-accord
in repository https://gitbox.apache.org/repos/asf/cassandra.git
The following commit(s) were added to refs/heads/cep-15-accord by this push:
new aac0fe0ff6 Ninja for CASSANDRA-17719: TransactionStatement now logs
every exception, will revert before trunk but needed for debugging
aac0fe0ff6 is described below
commit aac0fe0ff649fdd28320e679591dd87bde3b70f1
Author: David Capwell
AuthorDate: Tue Dec 13 12:05:30 2022 -0800
Ninja for CASSANDRA-17719: TransactionStatement now logs every exception,
will revert before trunk but needed for debugging
---
.../cql3/statements/TransactionStatement.java | 85 +-
1 file changed, 49 insertions(+), 36 deletions(-)
diff --git
a/src/java/org/apache/cassandra/cql3/statements/TransactionStatement.java
b/src/java/org/apache/cassandra/cql3/statements/TransactionStatement.java
index 064c6abf83..baead627dc 100644
--- a/src/java/org/apache/cassandra/cql3/statements/TransactionStatement.java
+++ b/src/java/org/apache/cassandra/cql3/statements/TransactionStatement.java
@@ -37,6 +37,9 @@ import com.google.common.annotations.VisibleForTesting;
import com.google.common.base.Preconditions;
import com.google.common.collect.Iterables;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
import accord.api.Key;
import accord.primitives.Keys;
import accord.primitives.Txn;
@@ -81,6 +84,8 @@ import static
org.apache.cassandra.utils.Clock.Global.nanoTime;
public class TransactionStatement implements CQLStatement
{
+private static final Logger logger =
LoggerFactory.getLogger(TransactionStatement.class);
+
public static final String DUPLICATE_TUPLE_NAME_MESSAGE = "The name '%s'
has already been used by a LET assignment.";
public static final String INCOMPLETE_PRIMARY_KEY_LET_MESSAGE = "SELECT in
LET assignment without LIMIT 1 must specify all primary key elements; CQL %s";
public static final String INCOMPLETE_PRIMARY_KEY_SELECT_MESSAGE = "Normal
SELECT without LIMIT 1 must specify all primary key elements; CQL %s";
@@ -292,52 +297,60 @@ public class TransactionStatement implements CQLStatement
@Override
public ResultMessage execute(QueryState state, QueryOptions options, long
queryStartNanoTime)
{
-for (NamedSelect assignment : assignments)
-checkAtMostOneRowSpecified(state.getClientState(), options,
assignment.select, INCOMPLETE_PRIMARY_KEY_LET_MESSAGE);
+try
+{
+for (NamedSelect assignment : assignments)
+checkAtMostOneRowSpecified(state.getClientState(), options,
assignment.select, INCOMPLETE_PRIMARY_KEY_LET_MESSAGE);
-if (returningSelect != null)
-checkAtMostOneRowSpecified(state.getClientState(), options,
returningSelect.select, INCOMPLETE_PRIMARY_KEY_SELECT_MESSAGE);
+if (returningSelect != null)
+checkAtMostOneRowSpecified(state.getClientState(), options,
returningSelect.select, INCOMPLETE_PRIMARY_KEY_SELECT_MESSAGE);
-TxnData data =
AccordService.instance().coordinate(createTxn(state.getClientState(), options),
options);
-
-if (returningSelect != null)
-{
-FilteredPartition partition = data.get(TxnDataName.returning());
-Selection.Selectors selectors =
returningSelect.select.getSelection().newSelectors(options);
-ResultSetBuilder result = new
ResultSetBuilder(returningSelect.select.getResultMetadata(), selectors, null);
-returningSelect.select.processPartition(partition.rowIterator(),
options, result, FBUtilities.nowInSeconds());
-return new ResultMessage.Rows(result.build());
-}
-
-if (returningReferences != null)
-{
-List names = new
ArrayList<>(returningReferences.size());
-List columns = new
ArrayList<>(returningReferences.size());
+TxnData data =
AccordService.instance().coordinate(createTxn(state.getClientState(), options),
options);
-for (RowDataReference reference : returningReferences)
+if (returningSelect != null)
{
-ColumnMetadata forMetadata = reference.toResultMetadata();
-names.add(forMetadata);
-columns.add(reference.column());
+FilteredPartition partition =
data.get(TxnDataName.returning());
+Selection.Selectors selectors =
returningSelect.select.getSelection().newSelectors(options);
+ResultSetBuilder result = new
ResultSetBuilder(returningSelect.select.getResultMetadata(), selectors, null);
+
returningSelect.select.processPartition(partition.rowIterator(), options,
result, FBUtilities.nowInSeconds());
+return new ResultMessage.Rows(result.build());
}
-ResultSetBuilder result
[jira] [Commented] (CASSANDRA-17964) Some tests are never executed due to naming violation - fix it and add checkstyle where applicable
[ https://issues.apache.org/jira/browse/CASSANDRA-17964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646808#comment-17646808 ] Stefan Miklosovic commented on CASSANDRA-17964: --- I will merge this soonish, we were just waiting on 4.1 to be out. cc [~bereng] [~dcapwell] > Some tests are never executed due to naming violation - fix it and add > checkstyle where applicable > -- > > Key: CASSANDRA-17964 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17964 > Project: Cassandra > Issue Type: Task > Components: Test/unit >Reporter: Ruslan Fomkin >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 4.x > > Time Spent: 2h 40m > Remaining Estimate: 0h > > [BatchTests|https://github.com/apache/cassandra/blob/trunk/test/unit/org/apache/cassandra/cql3/BatchTests.java] > doesn't follow naming convention to be run as unit tests and, thus, is never > run. > The rule in build expects names as `*Test`. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18115) WEBSITE - Fix text labels for C* versions on Download page
[ https://issues.apache.org/jira/browse/CASSANDRA-18115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-18115: -- Change Category: Semantic Complexity: Normal Component/s: Documentation/Website Fix Version/s: NA Reviewers: Michael Semb Wever Status: Open (was: Triage Needed) > WEBSITE - Fix text labels for C* versions on Download page > -- > > Key: CASSANDRA-18115 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18115 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Fix For: NA > > Attachments: image.png > > > The text labels for the C* versions on the Download page need to be updated > with the release of C* 4.1 this morning. > !image.png|width=300! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18115) WEBSITE - Fix text labels for C* versions on Download page
[ https://issues.apache.org/jira/browse/CASSANDRA-18115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-18115: -- Description: The text labels for the C* versions on the Download page need to be updated with the release of C* 4.1 this morning. !image.png|width=300! was: The text labels for the C* versions on the Download page need to be updated with the release of C* 4.1 this morning. !image.png|width-300! > WEBSITE - Fix text labels for C* versions on Download page > -- > > Key: CASSANDRA-18115 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18115 > Project: Cassandra > Issue Type: Task >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Attachments: image.png > > > The text labels for the C* versions on the Download page need to be updated > with the release of C* 4.1 this morning. > !image.png|width=300! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18115) WEBSITE - Fix text labels for C* versions on Download page
[ https://issues.apache.org/jira/browse/CASSANDRA-18115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-18115: -- Description: The text labels for the C* versions on the Download page need to be updated with the release of C* 4.1 this morning. !image.png! was: The text labels for the C* versions on the Download page need to be updated with the release of C* 4.1 this morning. > WEBSITE - Fix text labels for C* versions on Download page > -- > > Key: CASSANDRA-18115 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18115 > Project: Cassandra > Issue Type: Task >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Attachments: image.png > > > The text labels for the C* versions on the Download page need to be updated > with the release of C* 4.1 this morning. > !image.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-18115) WEBSITE - Fix text labels for C* versions on Download page
Erick Ramirez created CASSANDRA-18115: - Summary: WEBSITE - Fix text labels for C* versions on Download page Key: CASSANDRA-18115 URL: https://issues.apache.org/jira/browse/CASSANDRA-18115 Project: Cassandra Issue Type: Task Reporter: Erick Ramirez Assignee: Erick Ramirez Attachments: image.png The text labels for the C* versions on the Download page need to be updated with the release of C* 4.1 this morning. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18115) WEBSITE - Fix text labels for C* versions on Download page
[ https://issues.apache.org/jira/browse/CASSANDRA-18115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-18115: -- Description: The text labels for the C* versions on the Download page need to be updated with the release of C* 4.1 this morning. !image.png|width-300! was: The text labels for the C* versions on the Download page need to be updated with the release of C* 4.1 this morning. !image.png! > WEBSITE - Fix text labels for C* versions on Download page > -- > > Key: CASSANDRA-18115 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18115 > Project: Cassandra > Issue Type: Task >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Attachments: image.png > > > The text labels for the C* versions on the Download page need to be updated > with the release of C* 4.1 this morning. > !image.png|width-300! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18114) Remove ProtocolVersion entirely from the CollectionSerializer ecosystem
[
https://issues.apache.org/jira/browse/CASSANDRA-18114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-18114:
Change Category: Code Clarity
Complexity: Low Hanging Fruit
Component/s: Legacy/CQL
Fix Version/s: 5.x
Status: Open (was: Triage Needed)
> Remove ProtocolVersion entirely from the CollectionSerializer ecosystem
> ---
>
> Key: CASSANDRA-18114
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18114
> Project: Cassandra
> Issue Type: Task
> Components: Legacy/CQL
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 5.x
>
>
> {{CollectionSerializer}} and its subclasses have completely ignored
> {{ProtocolVersion}} for a very long time. It’s possible we may need to
> version their behavior in the future, but there’s no reason to keep the dead
> code in the meantime, as it causes confusion around whether code that uses
> these classes needs to provide a version.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-18114) Remove ProtocolVersion entirely from the CollectionSerializer ecosystem
Caleb Rackliffe created CASSANDRA-18114:
---
Summary: Remove ProtocolVersion entirely from the
CollectionSerializer ecosystem
Key: CASSANDRA-18114
URL: https://issues.apache.org/jira/browse/CASSANDRA-18114
Project: Cassandra
Issue Type: Task
Reporter: Caleb Rackliffe
Assignee: Caleb Rackliffe
{{CollectionSerializer}} and its subclasses have completely ignored
{{ProtocolVersion}} for a very long time. It’s possible we may need to version
their behavior in the future, but there’s no reason to keep the dead code in
the meantime, as it causes confusion around whether code that uses these
classes needs to provide a version.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18112) Add the feature of INDEX HINT for CQL
[ https://issues.apache.org/jira/browse/CASSANDRA-18112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646795#comment-17646795 ] Caleb Rackliffe commented on CASSANDRA-18112: - Historically, I think we've never seriously considered this, because we've never had a truly production-usable 2i implementation. Hopefully that will change w/ CASSANDRA-16052 ;) > Add the feature of INDEX HINT for CQL > -- > > Key: CASSANDRA-18112 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18112 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Syntax, Feature/2i Index >Reporter: maxwellguo >Priority: Normal > > It seems that CQL do not have the ability of INDEX HINT , such as when we > have more than one secondary index for some data table,And if the query hit > the indexes, the index with more estimate rows will be returned. But if we > want the query to be executed under our willing , we can use a hint like > ,hint specified index or ignore the index. > At first I want to open a jira that to add the feature of hint for CQL ,But I > think that may be a gigantic task with no clear goal. > Besides I think there may need a DISSCUSS for the specific grammatical form > before starting the work. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18113) fqltool dump results NPE when null value inserted using prepared query
[
https://issues.apache.org/jira/browse/CASSANDRA-18113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646794#comment-17646794
]
n.v.harikrishna commented on CASSANDRA-18113:
-
Prepared a patch for the fix: [https://github.com/apache/cassandra/pull/2050]
> fqltool dump results NPE when null value inserted using prepared query
> --
>
> Key: CASSANDRA-18113
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18113
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/fql
>Reporter: n.v.harikrishna
>Assignee: n.v.harikrishna
>Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Enable fullquerylog, prepare insert statement and bind it with a null value
> and execute it. Executing fqltool dump after insert will result into
> NullPointerException.
>
> Stept to reproduce:
> * Create cluster using ccm
> * Create a table something like:
> {code:java}
> CREATE TABLE ks1.t2 (
> id int PRIMARY KEY,
> value text
> ) ;
> {code}
> * Execute below code
> {code:java}
> try (CqlSession cqlSession = CqlSession.builder().build()) {
> PreparedStatement preparedStatement = cqlSession.prepare("INSERT INTO
> ks1.t2 (id, value) VALUES (?, ?)");
> cqlSession.execute(preparedStatement.bind(6, null));
> }
> {code}
> * Now running fqltool dump. It will run into NPE
>
>
> Stack trace:
> {code:java}
> error: null
> -- StackTrace --
> java.lang.NullPointerException
> at net.openhft.chronicle.bytes.BytesStore.wrap(BytesStore.java:76)
> at net.openhft.chronicle.bytes.Bytes.wrapForRead(Bytes.java:179)
> at
> org.apache.cassandra.fqltool.commands.Dump.appendValuesToStringBuilder(Dump.java:222)
> at org.apache.cassandra.fqltool.commands.Dump.dumpQuery(Dump.java:179)
> at org.apache.cassandra.fqltool.commands.Dump.lambda$dump$0(Dump.java:123)
> at
> net.openhft.chronicle.queue.impl.single.StoreTailer.readDocument(StoreTailer.java:111)
> at org.apache.cassandra.fqltool.commands.Dump.dump(Dump.java:148)
> at org.apache.cassandra.fqltool.commands.Dump.run(Dump.java:68)
> at
> org.apache.cassandra.fqltool.FullQueryLogTool.main(FullQueryLogTool.java:65)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-18113) fqltool dump results NPE when null value inserted using prepared query
[
https://issues.apache.org/jira/browse/CASSANDRA-18113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
n.v.harikrishna reassigned CASSANDRA-18113:
---
Assignee: n.v.harikrishna
> fqltool dump results NPE when null value inserted using prepared query
> --
>
> Key: CASSANDRA-18113
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18113
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/fql
>Reporter: n.v.harikrishna
>Assignee: n.v.harikrishna
>Priority: Normal
>
> Enable fullquerylog, prepare insert statement and bind it with a null value
> and execute it. Executing fqltool dump after insert will result into
> NullPointerException.
>
> Stept to reproduce:
> * Create cluster using ccm
> * Create a table something like:
> {code:java}
> CREATE TABLE ks1.t2 (
> id int PRIMARY KEY,
> value text
> ) ;
> {code}
> * Execute below code
> {code:java}
> try (CqlSession cqlSession = CqlSession.builder().build()) {
> PreparedStatement preparedStatement = cqlSession.prepare("INSERT INTO
> ks1.t2 (id, value) VALUES (?, ?)");
> cqlSession.execute(preparedStatement.bind(6, null));
> }
> {code}
> * Now running fqltool dump. It will run into NPE
>
>
> Stack trace:
> {code:java}
> error: null
> -- StackTrace --
> java.lang.NullPointerException
> at net.openhft.chronicle.bytes.BytesStore.wrap(BytesStore.java:76)
> at net.openhft.chronicle.bytes.Bytes.wrapForRead(Bytes.java:179)
> at
> org.apache.cassandra.fqltool.commands.Dump.appendValuesToStringBuilder(Dump.java:222)
> at org.apache.cassandra.fqltool.commands.Dump.dumpQuery(Dump.java:179)
> at org.apache.cassandra.fqltool.commands.Dump.lambda$dump$0(Dump.java:123)
> at
> net.openhft.chronicle.queue.impl.single.StoreTailer.readDocument(StoreTailer.java:111)
> at org.apache.cassandra.fqltool.commands.Dump.dump(Dump.java:148)
> at org.apache.cassandra.fqltool.commands.Dump.run(Dump.java:68)
> at
> org.apache.cassandra.fqltool.FullQueryLogTool.main(FullQueryLogTool.java:65)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-18113) fqltool dump results NPE when null value inserted using prepared query
n.v.harikrishna created CASSANDRA-18113:
---
Summary: fqltool dump results NPE when null value inserted using
prepared query
Key: CASSANDRA-18113
URL: https://issues.apache.org/jira/browse/CASSANDRA-18113
Project: Cassandra
Issue Type: Bug
Components: Tool/fql
Reporter: n.v.harikrishna
Enable fullquerylog, prepare insert statement and bind it with a null value and
execute it. Executing fqltool dump after insert will result into
NullPointerException.
Stept to reproduce:
* Create cluster using ccm
* Create a table something like:
{code:java}
CREATE TABLE ks1.t2 (
id int PRIMARY KEY,
value text
) ;
{code}
* Execute below code
{code:java}
try (CqlSession cqlSession = CqlSession.builder().build()) {
PreparedStatement preparedStatement = cqlSession.prepare("INSERT INTO
ks1.t2 (id, value) VALUES (?, ?)");
cqlSession.execute(preparedStatement.bind(6, null));
}
{code}
* Now running fqltool dump. It will run into NPE
Stack trace:
{code:java}
error: null
-- StackTrace --
java.lang.NullPointerException
at net.openhft.chronicle.bytes.BytesStore.wrap(BytesStore.java:76)
at net.openhft.chronicle.bytes.Bytes.wrapForRead(Bytes.java:179)
at
org.apache.cassandra.fqltool.commands.Dump.appendValuesToStringBuilder(Dump.java:222)
at org.apache.cassandra.fqltool.commands.Dump.dumpQuery(Dump.java:179)
at org.apache.cassandra.fqltool.commands.Dump.lambda$dump$0(Dump.java:123)
at
net.openhft.chronicle.queue.impl.single.StoreTailer.readDocument(StoreTailer.java:111)
at org.apache.cassandra.fqltool.commands.Dump.dump(Dump.java:148)
at org.apache.cassandra.fqltool.commands.Dump.run(Dump.java:68)
at
org.apache.cassandra.fqltool.FullQueryLogTool.main(FullQueryLogTool.java:65)
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18104) Major Performance degradation of Casandara 4.0.7 against Casandra 3.11.14
[
https://issues.apache.org/jira/browse/CASSANDRA-18104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646765#comment-17646765
]
Brandon Williams commented on CASSANDRA-18104:
--
Both machines are running:
{noformat}
openjdk version "1.8.0_342"
OpenJDK Runtime Environment (build 1.8.0_342-8u342-b07-0ubuntu1~20.04-b07)
OpenJDK 64-Bit Server VM (build 25.342-b07, mixed mode)
{noformat}
No configuration changes.
> Major Performance degradation of Casandara 4.0.7 against Casandra 3.11.14
>
>
> Key: CASSANDRA-18104
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18104
> Project: Cassandra
> Issue Type: Bug
>Reporter: Sreedhar J
>Priority: Urgent
> Attachments: 3.11.14.txt, 4.0.7.txt,
> cassandra-4x-test-1.0-jar-with-dependencies.jar, mailboxes_snapshot.zip,
> query30.txt, screenshot-1.png, screenshot-2.png
>
>
> Our application uses Casandra 3.11.x and has lot of security vulnerabilities
> which are addressed in 4.0.x. So we have upgraded the Casandra to 4.0.7
> and our performance tests have shown aorund 20% degradation compare to
> 3.11.x
> We are now able to reproduce the same performance degradation using the
> standalone queries. Here are the steps.
> 1. Expand Cassandra 3.11.14 tarball and 4.0.7 tarball to different folders
> 2. Import the attached data from the snapshot (mailboxes_snapshot.zip) into
> each Cassandra instance, see schema.cql for CQL for creating the required
> table and indexes before import
> 3. With CQLSH run the following query several times with TRACING ON and
> PAGING OFF against both versions of Cassandra: select * from
> mailbox.mailboxes where mbx_id= 6c57da2e-7ddd-4984-be62-105415e6b48a;
> 4. Compare results
> IWe ran the target query 30 times. Here's the average times to run the query:
> 3.11.14 - 19400.77
> 4.0.7 - 34906.03
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18104) Major Performance degradation of Casandara 4.0.7 against Casandra 3.11.14
[ https://issues.apache.org/jira/browse/CASSANDRA-18104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646762#comment-17646762 ] Sreedhar J commented on CASSANDRA-18104: Thanks [~brandon.williams] for quick updates. which JDK are you using ? we are using IBM JDK 8.0.7.15 ( JDK 8.0 SR7 FP15). Any changes done to Cassandra 4.x configuration ? We have seen the performance degradation in multiple environments. > Major Performance degradation of Casandara 4.0.7 against Casandra 3.11.14 > > > Key: CASSANDRA-18104 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18104 > Project: Cassandra > Issue Type: Bug >Reporter: Sreedhar J >Priority: Urgent > Attachments: 3.11.14.txt, 4.0.7.txt, > cassandra-4x-test-1.0-jar-with-dependencies.jar, mailboxes_snapshot.zip, > query30.txt, screenshot-1.png, screenshot-2.png > > > Our application uses Casandra 3.11.x and has lot of security vulnerabilities > which are addressed in 4.0.x. So we have upgraded the Casandra to 4.0.7 > and our performance tests have shown aorund 20% degradation compare to > 3.11.x > We are now able to reproduce the same performance degradation using the > standalone queries. Here are the steps. > 1. Expand Cassandra 3.11.14 tarball and 4.0.7 tarball to different folders > 2. Import the attached data from the snapshot (mailboxes_snapshot.zip) into > each Cassandra instance, see schema.cql for CQL for creating the required > table and indexes before import > 3. With CQLSH run the following query several times with TRACING ON and > PAGING OFF against both versions of Cassandra: select * from > mailbox.mailboxes where mbx_id= 6c57da2e-7ddd-4984-be62-105415e6b48a; > 4. Compare results > IWe ran the target query 30 times. Here's the average times to run the query: > 3.11.14 - 19400.77 > 4.0.7 - 34906.03 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18104) Major Performance degradation of Casandara 4.0.7 against Casandra 3.11.14
[
https://issues.apache.org/jira/browse/CASSANDRA-18104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646743#comment-17646743
]
Brandon Williams commented on CASSANDRA-18104:
--
I preheated the server with 100 runs before taking these:
3.11:
{noformat}
$ for x in {1..10}; do java -jar
cassandra-4x-test-1.0-jar-with-dependencies.jar Cassandra4xTest 1000 127.0.0.1
"6c57da2e-7ddd-4984-be62-105415e6b48a"; done 2>/dev/null | grep timeElapsed
timeElapsed = 5939
timeElapsed = 5769
timeElapsed = 4480
timeElapsed = 4496
timeElapsed = 5979
timeElapsed = 4934
timeElapsed = 5948
timeElapsed = 4801
timeElapsed = 5587
timeElapsed = 5754
{noformat}
4.0:
{noformat}
$ for x in {1..10}; do java -jar
cassandra-4x-test-1.0-jar-with-dependencies.jar Cassandra4xTest 1000 127.0.0.1
"6c57da2e-7ddd-4984-be62-105415e6b48a"; done 2>/dev/null | grep timeElapsed
timeElapsed = 4504
timeElapsed = 5007
timeElapsed = 5301
timeElapsed = 3456
timeElapsed = 4063
timeElapsed = 3851
timeElapsed = 4878
timeElapsed = 4294
timeElapsed = 4182
timeElapsed = 4620
{noformat}
> Major Performance degradation of Casandara 4.0.7 against Casandra 3.11.14
>
>
> Key: CASSANDRA-18104
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18104
> Project: Cassandra
> Issue Type: Bug
>Reporter: Sreedhar J
>Priority: Urgent
> Attachments: 3.11.14.txt, 4.0.7.txt,
> cassandra-4x-test-1.0-jar-with-dependencies.jar, mailboxes_snapshot.zip,
> query30.txt, screenshot-1.png, screenshot-2.png
>
>
> Our application uses Casandra 3.11.x and has lot of security vulnerabilities
> which are addressed in 4.0.x. So we have upgraded the Casandra to 4.0.7
> and our performance tests have shown aorund 20% degradation compare to
> 3.11.x
> We are now able to reproduce the same performance degradation using the
> standalone queries. Here are the steps.
> 1. Expand Cassandra 3.11.14 tarball and 4.0.7 tarball to different folders
> 2. Import the attached data from the snapshot (mailboxes_snapshot.zip) into
> each Cassandra instance, see schema.cql for CQL for creating the required
> table and indexes before import
> 3. With CQLSH run the following query several times with TRACING ON and
> PAGING OFF against both versions of Cassandra: select * from
> mailbox.mailboxes where mbx_id= 6c57da2e-7ddd-4984-be62-105415e6b48a;
> 4. Compare results
> IWe ran the target query 30 times. Here's the average times to run the query:
> 3.11.14 - 19400.77
> 4.0.7 - 34906.03
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-site updated (c1542aea -> b2ceec70)
This is an automated email from the ASF dual-hosted git repository.
mck pushed a change to branch asf-site
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git
discard c1542aea generate docs for 091d00dd
add 4f139602 Major Release 4.1.0
add dc9c4ad8 BLOG - Cassandra 4.1 is here
add b2ceec70 generate docs for dc9c4ad8
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 (c1542aea)
\
N -- N -- N refs/heads/asf-site (b2ceec70)
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:
content/_/_images/blog/cassandra-4.1-is-here.png | Bin 0 -> 795101 bytes
content/_/blog.html| 24 +++
...Replication.html => Cassandra-4.1-is-here.html} | 231 -
content/_/download.html| 57 +++--
content/_/index.html | 17 +-
content/search-index.js| 2 +-
.../ROOT/images/blog/cassandra-4.1-is-here.png | Bin 0 -> 795101 bytes
site-content/source/modules/ROOT/pages/blog.adoc | 24 +++
.../ROOT/pages/blog/Cassandra-4.1-is-here.adoc | 121 +++
.../source/modules/ROOT/pages/download.adoc| 63 --
site-content/source/modules/ROOT/pages/index.adoc | 19 +-
site-ui/build/ui-bundle.zip| Bin 4970898 -> 4970898
bytes
12 files changed, 360 insertions(+), 198 deletions(-)
create mode 100644 content/_/_images/blog/cassandra-4.1-is-here.png
copy content/_/blog/{Introducing-Transient-Replication.html =>
Cassandra-4.1-is-here.html} (50%)
create mode 100644
site-content/source/modules/ROOT/images/blog/cassandra-4.1-is-here.png
create mode 100644
site-content/source/modules/ROOT/pages/blog/Cassandra-4.1-is-here.adoc
-
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 (6cd794f4 -> b2ceec70)
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 6cd794f4 generate docs for 091d00dd
add 4f139602 Major Release 4.1.0
add dc9c4ad8 BLOG - Cassandra 4.1 is here
new b2ceec70 generate docs for dc9c4ad8
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 (6cd794f4)
\
N -- N -- N refs/heads/asf-staging (b2ceec70)
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:
content/_/_images/blog/cassandra-4.1-is-here.png | Bin 0 -> 795101 bytes
content/_/blog.html| 24 +++
...Replication.html => Cassandra-4.1-is-here.html} | 231 -
content/_/download.html| 57 +++--
content/_/index.html | 17 +-
content/search-index.js| 2 +-
.../ROOT/images/blog/cassandra-4.1-is-here.png | Bin 0 -> 795101 bytes
site-content/source/modules/ROOT/pages/blog.adoc | 24 +++
.../ROOT/pages/blog/Cassandra-4.1-is-here.adoc | 121 +++
.../source/modules/ROOT/pages/download.adoc| 63 --
site-content/source/modules/ROOT/pages/index.adoc | 19 +-
site-ui/build/ui-bundle.zip| Bin 4970898 -> 4970898
bytes
12 files changed, 360 insertions(+), 198 deletions(-)
create mode 100644 content/_/_images/blog/cassandra-4.1-is-here.png
copy content/_/blog/{Introducing-Transient-Replication.html =>
Cassandra-4.1-is-here.html} (50%)
create mode 100644
site-content/source/modules/ROOT/images/blog/cassandra-4.1-is-here.png
create mode 100644
site-content/source/modules/ROOT/pages/blog/Cassandra-4.1-is-here.adoc
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18104) Major Performance degradation of Casandara 4.0.7 against Casandra 3.11.14
[
https://issues.apache.org/jira/browse/CASSANDRA-18104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646715#comment-17646715
]
Sreedhar J commented on CASSANDRA-18104:
[~brandon.williams] We have written a standalone java program which executes
this query select * from mailbox.mailboxes where mbx_id=
6c57da2e-7ddd-4984-be62-105415e6b48a; 1000 times against cassandra 3.11.14
and 4.0.7. Here are the results.
!screenshot-2.png!
from the above data, we can clearly see Cassandra 4.x is slower compare to
3.x
please run the attached jar file against your 3.x and 4.x servers.
*for i in {1..10}; do java -jar cassandra-4x-test-1.0-jar-with-dependencies.jar
Cassandra4xTest 1000 127.0.0.1 "6c57da2e-7ddd-4984-be62-105415e6b48a" ; done
2>/dev/null | grep timeElapsed*
> Major Performance degradation of Casandara 4.0.7 against Casandra 3.11.14
>
>
> Key: CASSANDRA-18104
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18104
> Project: Cassandra
> Issue Type: Bug
>Reporter: Sreedhar J
>Priority: Urgent
> Attachments: 3.11.14.txt, 4.0.7.txt, mailboxes_snapshot.zip,
> query30.txt, screenshot-1.png, screenshot-2.png
>
>
> Our application uses Casandra 3.11.x and has lot of security vulnerabilities
> which are addressed in 4.0.x. So we have upgraded the Casandra to 4.0.7
> and our performance tests have shown aorund 20% degradation compare to
> 3.11.x
> We are now able to reproduce the same performance degradation using the
> standalone queries. Here are the steps.
> 1. Expand Cassandra 3.11.14 tarball and 4.0.7 tarball to different folders
> 2. Import the attached data from the snapshot (mailboxes_snapshot.zip) into
> each Cassandra instance, see schema.cql for CQL for creating the required
> table and indexes before import
> 3. With CQLSH run the following query several times with TRACING ON and
> PAGING OFF against both versions of Cassandra: select * from
> mailbox.mailboxes where mbx_id= 6c57da2e-7ddd-4984-be62-105415e6b48a;
> 4. Compare results
> IWe ran the target query 30 times. Here's the average times to run the query:
> 3.11.14 - 19400.77
> 4.0.7 - 34906.03
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18104) Major Performance degradation of Casandara 4.0.7 against Casandra 3.11.14
[ https://issues.apache.org/jira/browse/CASSANDRA-18104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreedhar J updated CASSANDRA-18104: --- Attachment: cassandra-4x-test-1.0-jar-with-dependencies.jar > Major Performance degradation of Casandara 4.0.7 against Casandra 3.11.14 > > > Key: CASSANDRA-18104 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18104 > Project: Cassandra > Issue Type: Bug >Reporter: Sreedhar J >Priority: Urgent > Attachments: 3.11.14.txt, 4.0.7.txt, > cassandra-4x-test-1.0-jar-with-dependencies.jar, mailboxes_snapshot.zip, > query30.txt, screenshot-1.png, screenshot-2.png > > > Our application uses Casandra 3.11.x and has lot of security vulnerabilities > which are addressed in 4.0.x. So we have upgraded the Casandra to 4.0.7 > and our performance tests have shown aorund 20% degradation compare to > 3.11.x > We are now able to reproduce the same performance degradation using the > standalone queries. Here are the steps. > 1. Expand Cassandra 3.11.14 tarball and 4.0.7 tarball to different folders > 2. Import the attached data from the snapshot (mailboxes_snapshot.zip) into > each Cassandra instance, see schema.cql for CQL for creating the required > table and indexes before import > 3. With CQLSH run the following query several times with TRACING ON and > PAGING OFF against both versions of Cassandra: select * from > mailbox.mailboxes where mbx_id= 6c57da2e-7ddd-4984-be62-105415e6b48a; > 4. Compare results > IWe ran the target query 30 times. Here's the average times to run the query: > 3.11.14 - 19400.77 > 4.0.7 - 34906.03 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch trunk updated: BLOG - Cassandra 4.1 is here
This is an automated email from the ASF dual-hosted git repository. mck 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 dc9c4ad8 BLOG - Cassandra 4.1 is here dc9c4ad8 is described below commit dc9c4ad83f44eff2cf3b4325addb62714ec37fa7 Author: Erick Ramirez AuthorDate: Sun Dec 11 23:38:35 2022 +1100 BLOG - Cassandra 4.1 is here Patch by Chris Thornett, Diogenese Topper, Erick Ramirez; reviewed by Erick Ramirez, Michael Semb Wever for CASSANDRA-18063 --- .../ROOT/images/blog/cassandra-4.1-is-here.png | Bin 0 -> 795101 bytes site-content/source/modules/ROOT/pages/blog.adoc | 24 .../ROOT/pages/blog/Cassandra-4.1-is-here.adoc | 121 + site-content/source/modules/ROOT/pages/index.adoc | 19 ++-- 4 files changed, 155 insertions(+), 9 deletions(-) diff --git a/site-content/source/modules/ROOT/images/blog/cassandra-4.1-is-here.png b/site-content/source/modules/ROOT/images/blog/cassandra-4.1-is-here.png new file mode 100644 index ..7e447b26 Binary files /dev/null and b/site-content/source/modules/ROOT/images/blog/cassandra-4.1-is-here.png differ diff --git a/site-content/source/modules/ROOT/pages/blog.adoc b/site-content/source/modules/ROOT/pages/blog.adoc index 2822cd63..0a5fc46a 100644 --- a/site-content/source/modules/ROOT/pages/blog.adoc +++ b/site-content/source/modules/ROOT/pages/blog.adoc @@ -8,6 +8,30 @@ 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 is here! +[discrete] + December 13, 2022 +-- +[openblock,card-content] +-- +Apache Cassandra 4.1 is GA! Read the blog for more details on the key features you won't want to miss in the next major release from the project. + +[openblock,card-btn card-btn--blog] + +[.btn.btn--alt] +xref:blog/Cassandra-4.1-is-here.adoc[Read More] + + +-- + +//end card + //start card [openblock,card shadow relative test] diff --git a/site-content/source/modules/ROOT/pages/blog/Cassandra-4.1-is-here.adoc b/site-content/source/modules/ROOT/pages/blog/Cassandra-4.1-is-here.adoc new file mode 100644 index ..72f75dfa --- /dev/null +++ b/site-content/source/modules/ROOT/pages/blog/Cassandra-4.1-is-here.adoc @@ -0,0 +1,121 @@ += Apache Cassandra 4.1: Rock Solid, Cloud-Native, Strongly Consistent and Highly Scalable +:page-layout: single-post +:page-role: blog-post +:page-post-date: December 13, 2022 +:page-post-author: Cassandra Community +:description: Apache Cassandra 4.1 released + +:!figure-caption: + +._Image credit: https://www.pexels.com/@roman-odintsov/[Roman Odintsov on Pexels^]_ +image::blog/cassandra-4.1-is-here.png[Christmas present] + +Today, we are excited to announce General Availability (GA) of Apache Cassandra 4.1, the project's major release for 2022 with lots of new features. This release paves the way to a more cloud-native future for the project by externalizing important key functions, extending Apache Cassandra, and enabling an expanded ecosystem without compromising the stable core code. + +Cassandra 4.1 also marks the delivery of our commitment to a yearly release. + +The release of 4.0 last year laid the foundations for growth. It established an important baseline for any future version of Cassandra while providing the needed infrastructure to ensure future releases maintain high quality and correctness. The 4.0 release was also the most stable GA for the project, and arguably any distributed open source database system, and opened the floodgates to a host of new community-developed features that are either included in 4.1 or in development. + +== New Features in 4.1 + +A major theme for Apache Cassandra 4.1 is pluggability. With each new framework, we are establishing a straightforward interface to Cassandra internals and an understood contract when using outside code. This theme sits alongside a strong focus on features that provide better control, improved ease of use, and flexibility that benefits developers and operators significantly. + +=== For Developers and Users + +The community is continuing to improve the performance of the database and make Cassandra both easier to use for end users and easier to onboard key development requests from the community. + + Paxos Improvements + +Cassandra uses a Paxos consensus protocol implementation that creates strong consistency. This is achieved by quorum reads to ensure a single value is selected and executed from all the proposed updates at any given time. Where an action needs to persist based on the current state of the system then Lightweight Transactions (LWTs) are used. Some examples of use cases are selling seats to a concert and where an `INSERT`
[jira] [Updated] (CASSANDRA-18104) Major Performance degradation of Casandara 4.0.7 against Casandra 3.11.14
[ https://issues.apache.org/jira/browse/CASSANDRA-18104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreedhar J updated CASSANDRA-18104: --- Attachment: screenshot-2.png > Major Performance degradation of Casandara 4.0.7 against Casandra 3.11.14 > > > Key: CASSANDRA-18104 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18104 > Project: Cassandra > Issue Type: Bug >Reporter: Sreedhar J >Priority: Urgent > Attachments: 3.11.14.txt, 4.0.7.txt, mailboxes_snapshot.zip, > query30.txt, screenshot-1.png, screenshot-2.png > > > Our application uses Casandra 3.11.x and has lot of security vulnerabilities > which are addressed in 4.0.x. So we have upgraded the Casandra to 4.0.7 > and our performance tests have shown aorund 20% degradation compare to > 3.11.x > We are now able to reproduce the same performance degradation using the > standalone queries. Here are the steps. > 1. Expand Cassandra 3.11.14 tarball and 4.0.7 tarball to different folders > 2. Import the attached data from the snapshot (mailboxes_snapshot.zip) into > each Cassandra instance, see schema.cql for CQL for creating the required > table and indexes before import > 3. With CQLSH run the following query several times with TRACING ON and > PAGING OFF against both versions of Cassandra: select * from > mailbox.mailboxes where mbx_id= 6c57da2e-7ddd-4984-be62-105415e6b48a; > 4. Compare results > IWe ran the target query 30 times. Here's the average times to run the query: > 3.11.14 - 19400.77 > 4.0.7 - 34906.03 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch trunk updated: Major Release 4.1.0
This is an automated email from the ASF dual-hosted git repository. mck 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 4f139602 Major Release 4.1.0 4f139602 is described below commit 4f139602d7ed849efe1ff461e061ec5f5acc5ba6 Author: mck AuthorDate: Sat Dec 10 15:13:54 2022 +0100 Major Release 4.1.0 --- .../source/modules/ROOT/pages/download.adoc| 63 +++--- 1 file changed, 44 insertions(+), 19 deletions(-) diff --git a/site-content/source/modules/ROOT/pages/download.adoc b/site-content/source/modules/ROOT/pages/download.adoc index 2c880554..0f6764e7 100644 --- a/site-content/source/modules/ROOT/pages/download.adoc +++ b/site-content/source/modules/ROOT/pages/download.adoc @@ -16,16 +16,16 @@ [discrete] === Latest GA Version [discrete] - Download the latest Apache Cassandra 4.0 GA release: + Download the latest Apache Cassandra 4.1 GA release: [discrete] -== Released on 2022-10-23 + Latest release on 2022-12-13 [discrete] -== Maintained until 4.3.0 release (May-July 2024) + Maintained until 4.4.0 release (May-July 2025) [.btn.btn--alt] -https://www.apache.org/dyn/closer.lua/cassandra/4.0.7/apache-cassandra-4.0.7-bin.tar.gz[4.0.7,window=blank] +https://www.apache.org/dyn/closer.lua/cassandra/4.1.0/apache-cassandra-4.1.0-bin.tar.gz[4.1.0,window=blank] -(https://downloads.apache.org/cassandra/4.0.7/apache-cassandra-4.0.7-bin.tar.gz.asc[pgp,window=blank], https://downloads.apache.org/cassandra/4.0.7/apache-cassandra-4.0.7-bin.tar.gz.sha256[sha256,window=blank] and https://downloads.apache.org/cassandra/4.0.7/apache-cassandra-4.0.7-bin.tar.gz.sha512[sha512,window=blank]) +(https://downloads.apache.org/cassandra/4.1.0/apache-cassandra-4.1.0-bin.tar.gz.asc[pgp,window=blank], https://downloads.apache.org/cassandra/4.1.0/apache-cassandra-4.1.0-bin.tar.gz.sha256[sha256,window=blank] and https://downloads.apache.org/cassandra/4.1.0/apache-cassandra-4.1.0-bin.tar.gz.sha512[sha512,window=blank]) -- [openblock, inline50 inline-top] @@ -33,11 +33,11 @@ https://www.apache.org/dyn/closer.lua/cassandra/4.0.7/apache-cassandra-4.0.7-bin [discrete] === Previous Stable Version [discrete] - Download the latest Apache Cassandra 3.11 release: + Download the latest Apache Cassandra 4.0 release: [discrete] -== Released on 2022-10-23 + Latest release on 2022-10-23 [discrete] -== Maintained until 4.2.0 release (May-July 2023) + Maintained until 4.3.0 release (May-July 2024) [.btn.btn--alt] https://www.apache.org/dyn/closer.lua/cassandra/3.11.14/apache-cassandra-3.11.14-bin.tar.gz[3.11.14,window=blank] @@ -45,27 +45,52 @@ https://www.apache.org/dyn/closer.lua/cassandra/3.11.14/apache-cassandra-3.11.14 (https://downloads.apache.org/cassandra/3.11.14/apache-cassandra-3.11.14-bin.tar.gz.asc[pgp,window=blank], https://downloads.apache.org/cassandra/3.11.14/apache-cassandra-3.11.14-bin.tar.gz.sha256[sha256,window=blank] and https://downloads.apache.org/cassandra/3.11.14/apache-cassandra-3.11.14-bin.tar.gz.sha512[sha512,window=blank]) -- -[openblock, inline50 inline-top] +[openblock, inline100 inline-top] -- [discrete] === Older Supported Releases - +[discrete] The following older Cassandra releases are still supported: +-- + +[openblock, inline50 inline-top] +-- + +[discrete] + Download the latest Apache Cassandra 3.11 release: +[discrete] + Latest release on 2022-10-23 +[discrete] + Maintained until 4.2.0 release (May-July 2023) + +[.btn.btn--alt] +https://www.apache.org/dyn/closer.lua/cassandra/3.0.28/apache-cassandra-3.0.28-bin.tar.gz[3.0.28,window=blank] + +(https://downloads.apache.org/cassandra/3.0.28/apache-cassandra-3.0.28-bin.tar.gz.asc[pgp,window=blank], https://downloads.apache.org/cassandra/3.0.28/apache-cassandra-3.0.28-bin.tar.gz.sha256[sha256,window=blank] and https://downloads.apache.org/cassandra/3.0.28/apache-cassandra-3.0.28-bin.tar.gz.sha512[sha512,window=blank]) +-- + +[openblock, inline50 inline-top] +-- + [discrete] Apache Cassandra 3.0 [discrete] -== Released on 2022-10-23 + Latest release on 2022-10-23 [discrete] -== Maintained until 4.2.0 release (May-July 2023) + Maintained until 4.2.0 release (May-July 2023) [.btn.btn--alt] https://www.apache.org/dyn/closer.lua/cassandra/3.0.28/apache-cassandra-3.0.28-bin.tar.gz[3.0.28,window=blank] (https://downloads.apache.org/cassandra/3.0.28/apache-cassandra-3.0.28-bin.tar.gz.asc[pgp,window=blank], https://downloads.apache.org/cassandra/3.0.28/apache-cassandra-3.0.28-bin.tar.gz.sha256[sha256,window=blank] and https://downloads.apache.org/cassandra/3.0.28/apache-cassandra-3.0.28-bin.tar.gz.sha512[sha512,window=blank]) +-- +[openblock, inline100 inline-top] +-- -Older (unsupported)
[jira] [Commented] (CASSANDRA-18102) Add a virtual table to list snapshots
[
https://issues.apache.org/jira/browse/CASSANDRA-18102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646694#comment-17646694
]
maxwellguo commented on CASSANDRA-18102:
OK thx
> Add a virtual table to list snapshots
> -
>
> Key: CASSANDRA-18102
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18102
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Virtual Tables, Local/Snapshots
>Reporter: Paulo Motta
>Assignee: maxwellguo
>Priority: Normal
>
> It should be possible to query a node's snapshots via virtual tables.
> The table should expose the same fields/columns as the
> [TableSnapshot|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/service/snapshot/TableSnapshot.java]
> class.
> Something along these lines:
> {noformat}
> cqlsh> SELECT * FROM system_views.snapshots;
>
> tag | keyspace_name | table_name | table_id | is_ephemeral | created_at |
> expires_at | directories
> +---++---+--+---++
> 1670460346841 | system | compaction_info |
> 123e4567-e89b-12d3-a456-426614174000 | false | 2022-12-08T00:45:47.108Z |
> null |
> {'/var/lib/cassandra/data/system/compaction_history-b4dbb7b4dc493fb5b3bfce6e434832ca/snapshots/1670460346841'}
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17797) All system properties and environment variables should be accessed via the new CassandraRelevantProperties and CassandraRelevantEnv classes
[ https://issues.apache.org/jira/browse/CASSANDRA-17797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646686#comment-17646686 ] Ekaterina Dimitrova commented on CASSANDRA-17797: - Thank you [~smiklosovic] > All system properties and environment variables should be accessed via the > new CassandraRelevantProperties and CassandraRelevantEnv classes > --- > > Key: CASSANDRA-17797 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17797 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Maxim Muzafarov >Priority: Low > Fix For: 4.x > > Time Spent: 10m > Remaining Estimate: 0h > > Follow up ticket for CASSANDRA-15876 - > "Always access system properties and environment variables via the new > CassandraRelevantProperties and CassandraRelevantEnv classes" > As part of that ticket we moved to the two new classes only > properties/variables that were currently listed in System Properties Virtual > Table. > We have to move to those classes the rest of the properties around the code > and start using those classes to access all of them. > +Additional information for newcomers:+ > You might want to start by getting acquainted with > CassandraRelevantProperties and CassandraRelevantEnv classes. Also, you might > want to check what changes were done and how the first batch was transferred > to this new framework as part of > [CASSANDRA-15876|https://github.com/apache/cassandra/commit/7694c1d191531ac152db55e83bc0db6864a5441e] > We are interested into the properties accessed currently through > getProperties around the code. > As part of CASSANDRA-15876 relevant unit tests were added > (CassandraRelevantPropertiesTest). To verify the new patch we need to ensure > that all tests Cassandra pass and also to think about potential update of the > mentioned test class. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17797) All system properties and environment variables should be accessed via the new CassandraRelevantProperties and CassandraRelevantEnv classes
[ https://issues.apache.org/jira/browse/CASSANDRA-17797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17797: Status: Needs Committer (was: Review In Progress) > All system properties and environment variables should be accessed via the > new CassandraRelevantProperties and CassandraRelevantEnv classes > --- > > Key: CASSANDRA-17797 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17797 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Maxim Muzafarov >Priority: Low > Fix For: 4.x > > Time Spent: 10m > Remaining Estimate: 0h > > Follow up ticket for CASSANDRA-15876 - > "Always access system properties and environment variables via the new > CassandraRelevantProperties and CassandraRelevantEnv classes" > As part of that ticket we moved to the two new classes only > properties/variables that were currently listed in System Properties Virtual > Table. > We have to move to those classes the rest of the properties around the code > and start using those classes to access all of them. > +Additional information for newcomers:+ > You might want to start by getting acquainted with > CassandraRelevantProperties and CassandraRelevantEnv classes. Also, you might > want to check what changes were done and how the first batch was transferred > to this new framework as part of > [CASSANDRA-15876|https://github.com/apache/cassandra/commit/7694c1d191531ac152db55e83bc0db6864a5441e] > We are interested into the properties accessed currently through > getProperties around the code. > As part of CASSANDRA-15876 relevant unit tests were added > (CassandraRelevantPropertiesTest). To verify the new patch we need to ensure > that all tests Cassandra pass and also to think about potential update of the > mentioned test class. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17797) All system properties and environment variables should be accessed via the new CassandraRelevantProperties and CassandraRelevantEnv classes
[ https://issues.apache.org/jira/browse/CASSANDRA-17797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17797: -- Reviewers: Stefan Miklosovic Status: Review In Progress (was: Needs Committer) I ll take a look. [~e.dimitrova] tag along anyway if you wish as we need 2 committers eventually. > All system properties and environment variables should be accessed via the > new CassandraRelevantProperties and CassandraRelevantEnv classes > --- > > Key: CASSANDRA-17797 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17797 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Maxim Muzafarov >Priority: Low > Fix For: 4.x > > Time Spent: 10m > Remaining Estimate: 0h > > Follow up ticket for CASSANDRA-15876 - > "Always access system properties and environment variables via the new > CassandraRelevantProperties and CassandraRelevantEnv classes" > As part of that ticket we moved to the two new classes only > properties/variables that were currently listed in System Properties Virtual > Table. > We have to move to those classes the rest of the properties around the code > and start using those classes to access all of them. > +Additional information for newcomers:+ > You might want to start by getting acquainted with > CassandraRelevantProperties and CassandraRelevantEnv classes. Also, you might > want to check what changes were done and how the first batch was transferred > to this new framework as part of > [CASSANDRA-15876|https://github.com/apache/cassandra/commit/7694c1d191531ac152db55e83bc0db6864a5441e] > We are interested into the properties accessed currently through > getProperties around the code. > As part of CASSANDRA-15876 relevant unit tests were added > (CassandraRelevantPropertiesTest). To verify the new patch we need to ensure > that all tests Cassandra pass and also to think about potential update of the > mentioned test class. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17797) All system properties and environment variables should be accessed via the new CassandraRelevantProperties and CassandraRelevantEnv classes
[ https://issues.apache.org/jira/browse/CASSANDRA-17797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646664#comment-17646664 ] Ekaterina Dimitrova commented on CASSANDRA-17797: - About CI: Are you familiar with [Butler|https://butler.cassandra.apache.org/#/]? You can use it to see what are the current failures/flaky tests in Cassandra to compare with your results. Butler gets its data from Jenkins so I would advise you if you do not find any failure there, also to check for open tickets in Jira, based on CircleCI findings. > All system properties and environment variables should be accessed via the > new CassandraRelevantProperties and CassandraRelevantEnv classes > --- > > Key: CASSANDRA-17797 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17797 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Maxim Muzafarov >Priority: Low > Fix For: 4.x > > Time Spent: 10m > Remaining Estimate: 0h > > Follow up ticket for CASSANDRA-15876 - > "Always access system properties and environment variables via the new > CassandraRelevantProperties and CassandraRelevantEnv classes" > As part of that ticket we moved to the two new classes only > properties/variables that were currently listed in System Properties Virtual > Table. > We have to move to those classes the rest of the properties around the code > and start using those classes to access all of them. > +Additional information for newcomers:+ > You might want to start by getting acquainted with > CassandraRelevantProperties and CassandraRelevantEnv classes. Also, you might > want to check what changes were done and how the first batch was transferred > to this new framework as part of > [CASSANDRA-15876|https://github.com/apache/cassandra/commit/7694c1d191531ac152db55e83bc0db6864a5441e] > We are interested into the properties accessed currently through > getProperties around the code. > As part of CASSANDRA-15876 relevant unit tests were added > (CassandraRelevantPropertiesTest). To verify the new patch we need to ensure > that all tests Cassandra pass and also to think about potential update of the > mentioned test class. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-18112) Add the feature of INDEX HINT for CQL
maxwellguo created CASSANDRA-18112: -- Summary: Add the feature of INDEX HINT for CQL Key: CASSANDRA-18112 URL: https://issues.apache.org/jira/browse/CASSANDRA-18112 Project: Cassandra Issue Type: Improvement Components: CQL/Syntax, Feature/2i Index Reporter: maxwellguo It seems that CQL do not have the ability of INDEX HINT , such as when we have more than one secondary index for some data table,And if the query hit the indexes, the index with more estimate rows will be returned. But if we want the query to be executed under our willing , we can use a hint like ,hint specified index or ignore the index. At first I want to open a jira that to add the feature of hint for CQL ,But I think that may be a gigantic task with no clear goal. Besides I think there may need a DISSCUSS for the specific grammatical form before starting the work. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17797) All system properties and environment variables should be accessed via the new CassandraRelevantProperties and CassandraRelevantEnv classes
[ https://issues.apache.org/jira/browse/CASSANDRA-17797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646662#comment-17646662 ] Ekaterina Dimitrova commented on CASSANDRA-17797: - Hi [~mmuzaf] , Thank you for the patch and the summary. Unfortunately, I have only 8 business days until the end of this year and I do not believe I will be able to get to it before January some time. I changed the status to NEEDS COMMITTER in case someone else from the community has cycles earlier than me. Thank you! > All system properties and environment variables should be accessed via the > new CassandraRelevantProperties and CassandraRelevantEnv classes > --- > > Key: CASSANDRA-17797 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17797 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Maxim Muzafarov >Priority: Low > Fix For: 4.x > > Time Spent: 10m > Remaining Estimate: 0h > > Follow up ticket for CASSANDRA-15876 - > "Always access system properties and environment variables via the new > CassandraRelevantProperties and CassandraRelevantEnv classes" > As part of that ticket we moved to the two new classes only > properties/variables that were currently listed in System Properties Virtual > Table. > We have to move to those classes the rest of the properties around the code > and start using those classes to access all of them. > +Additional information for newcomers:+ > You might want to start by getting acquainted with > CassandraRelevantProperties and CassandraRelevantEnv classes. Also, you might > want to check what changes were done and how the first batch was transferred > to this new framework as part of > [CASSANDRA-15876|https://github.com/apache/cassandra/commit/7694c1d191531ac152db55e83bc0db6864a5441e] > We are interested into the properties accessed currently through > getProperties around the code. > As part of CASSANDRA-15876 relevant unit tests were added > (CassandraRelevantPropertiesTest). To verify the new patch we need to ensure > that all tests Cassandra pass and also to think about potential update of the > mentioned test class. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17797) All system properties and environment variables should be accessed via the new CassandraRelevantProperties and CassandraRelevantEnv classes
[ https://issues.apache.org/jira/browse/CASSANDRA-17797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17797: Status: Needs Committer (was: Patch Available) > All system properties and environment variables should be accessed via the > new CassandraRelevantProperties and CassandraRelevantEnv classes > --- > > Key: CASSANDRA-17797 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17797 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Maxim Muzafarov >Priority: Low > Fix For: 4.x > > Time Spent: 10m > Remaining Estimate: 0h > > Follow up ticket for CASSANDRA-15876 - > "Always access system properties and environment variables via the new > CassandraRelevantProperties and CassandraRelevantEnv classes" > As part of that ticket we moved to the two new classes only > properties/variables that were currently listed in System Properties Virtual > Table. > We have to move to those classes the rest of the properties around the code > and start using those classes to access all of them. > +Additional information for newcomers:+ > You might want to start by getting acquainted with > CassandraRelevantProperties and CassandraRelevantEnv classes. Also, you might > want to check what changes were done and how the first batch was transferred > to this new framework as part of > [CASSANDRA-15876|https://github.com/apache/cassandra/commit/7694c1d191531ac152db55e83bc0db6864a5441e] > We are interested into the properties accessed currently through > getProperties around the code. > As part of CASSANDRA-15876 relevant unit tests were added > (CassandraRelevantPropertiesTest). To verify the new patch we need to ensure > that all tests Cassandra pass and also to think about potential update of the > mentioned test class. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18108) Data loss after a system restart/upgrade (3.11.14)
[
https://issues.apache.org/jira/browse/CASSANDRA-18108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646651#comment-17646651
]
Aleksey Yeschenko commented on CASSANDRA-18108:
---
[~maedhroz] It should be perfectly safe, seeing as you are essentially changing
an alias for an component that is positionally set in stone. There is no reason
to forbid it, and it has never been problematic. If there is a bug somewhere,
it's the bug that needs to be fixed.
> Data loss after a system restart/upgrade (3.11.14)
> --
>
> Key: CASSANDRA-18108
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18108
> Project: Cassandra
> Issue Type: Bug
>Reporter: Ke Han
>Priority: Normal
>
> When we upgrade Cassandra from 3.11.14 to 4.0.7, we found a data loss during
> the upgrade process. This bug can also be triggered if simply performing a
> system restart.
> h1. Steps to reproduce
> Start a 3.11.14 or 4.0.7 Cassandra node using default configurations. Execute
> the following cqlsh commands.
> {code:java}
> CREATE KEYSPACE ks WITH REPLICATION = { 'class' : 'SimpleStrategy',
> 'replication_factor' : 1 };
> CREATE TABLE IF NOT EXISTS ks.tb (c1 INT,c3 INT,c2 TEXT, PRIMARY KEY (c1 ))
> WITH speculative_retry = 'ALWAYS';
> INSERT INTO ks.tb (c1, c2) VALUES (2,'val');
> ALTER TABLE ks.tb DROP c2 ;
> ALTER TABLE ks.tb RENAME c1 TO c2; {code}
> Then execute a SELECT command, we get the correct data
> {code:java}
> cqlsh> SELECT * FROM ks.tb;
> c2 | c3
> +--
> 2 | null
> (1 rows){code}
> Flush and stop the Cassandra daemon.
> {code:java}
> bin/nodetool flush
> bin/nodetool stopdaemon{code}
> Then restart the node.
> {code:java}
> bin/cassandra{code}
> Start cqlsh, and execute the same SELECT command. The data in ks.tb is lost.
> {code:java}
> cqlsh> SELECT * FROM ks.tb;
> c2 | c3
> +
> (0 rows){code}
>
> During the node restart, we found an error log about initializing the table,
> but it didn't prevent the system from starting up.
> {code:java}
> INFO [main] 2022-12-09 21:37:54,234 ColumnFamilyStore.java:432 -
> Initializing ks.tb
> ERROR [SSTableBatchOpen:1] 2022-12-09 21:37:54,237 CassandraDaemon.java:244 -
> Exception in thread Thread[SSTableBatchOpen:1,5,main]
> java.lang.AssertionError: null
> at
> org.apache.cassandra.db.PartitionColumns$Builder.add(PartitionColumns.java:161)
> at
> org.apache.cassandra.db.SerializationHeader$Component.toHeader(SerializationHeader.java:340)
> at
> org.apache.cassandra.io.sstable.format.SSTableReader.open(SSTableReader.java:522)
> at
> org.apache.cassandra.io.sstable.format.SSTableReader.open(SSTableReader.java:385)
> at
> org.apache.cassandra.io.sstable.format.SSTableReader$3.run(SSTableReader.java:570)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 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:84)
> at java.lang.Thread.run(Thread.java:750) {code}
>
> This bug can also be triggered if we perform an upgrade from 3.11.14 to 4.0.7
> and execute the SELECT command in the new version. (*The token_num
> configuration in 4.0.7 is modified to 16 for upgrade compatibility purposes,
> all the other configurations are using default values)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (c1542aea -> 6cd794f4)
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 c1542aea generate docs for 091d00dd new 6cd794f4 generate docs for 091d00dd 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 (c1542aea) \ N -- N -- N refs/heads/asf-staging (6cd794f4) 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: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4970898 -> 4970898 bytes 2 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] [Updated] (CASSANDRA-17797) All system properties and environment variables should be accessed via the new CassandraRelevantProperties and CassandraRelevantEnv classes
[ https://issues.apache.org/jira/browse/CASSANDRA-17797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated CASSANDRA-17797: Impacts: None,Docs (was: None) Test and Documentation Plan: The patch requires running all tests related to the CI part. Documentation is not required for now due to no new system properties were added. Status: Patch Available (was: In Progress) > All system properties and environment variables should be accessed via the > new CassandraRelevantProperties and CassandraRelevantEnv classes > --- > > Key: CASSANDRA-17797 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17797 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Maxim Muzafarov >Priority: Low > Fix For: 4.x > > Time Spent: 10m > Remaining Estimate: 0h > > Follow up ticket for CASSANDRA-15876 - > "Always access system properties and environment variables via the new > CassandraRelevantProperties and CassandraRelevantEnv classes" > As part of that ticket we moved to the two new classes only > properties/variables that were currently listed in System Properties Virtual > Table. > We have to move to those classes the rest of the properties around the code > and start using those classes to access all of them. > +Additional information for newcomers:+ > You might want to start by getting acquainted with > CassandraRelevantProperties and CassandraRelevantEnv classes. Also, you might > want to check what changes were done and how the first batch was transferred > to this new framework as part of > [CASSANDRA-15876|https://github.com/apache/cassandra/commit/7694c1d191531ac152db55e83bc0db6864a5441e] > We are interested into the properties accessed currently through > getProperties around the code. > As part of CASSANDRA-15876 relevant unit tests were added > (CassandraRelevantPropertiesTest). To verify the new patch we need to ensure > that all tests Cassandra pass and also to think about potential update of the > mentioned test class. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17797) All system properties and environment variables should be accessed via the new CassandraRelevantProperties and CassandraRelevantEnv classes
[
https://issues.apache.org/jira/browse/CASSANDRA-17797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646618#comment-17646618
]
Maxim Muzafarov commented on CASSANDRA-17797:
-
Hey,
[~mck], [~e.dimitrova]
Please, take a look at my pull request - [GitHub PullRequest:
2010|https://github.com/apache/cassandra/pull/2046/files]. As you mentioned
earlier, we will expose some added system properties (properties with
_cassandra._ prefix are already exposed) to the public API via a virtual table.
If we agree on this pull request in general I'll post a new message to the dev
list to share it with the community.
I think it may be a good idea to add a new column to the system properties
virtual table thus users will be able to see the impact of a particular
property on their production environment. The list properties are easy to
filter. To achieve this goal I've marked the properties related to the test
environment with the {_}TEST_{_} prefix. If we agree on this I can create a new
JIRA issue.
h3. The implementation notes
- the checkstyle rule added to force the CassandraRelevantProperties usage;
- the enum pattern that was used: upper-casing property name with replacing
{*}`{*}{_}.`{*}{*}{_} to *{_}`{_}`* _and removing _cassandra._ prefix;
- all newly added properties are sorted by their name;
- properties that are related to test/debug are marked with the {_}TEST{_}_
prefix;
- setInt(), setString() etc. now return the previous value for convenient
usage in the test source code;
h3. The public API changes
Newly production system properties added:
- io.netty.eventLoopThreads
- io.netty.transport.estimateSizeOnSubmit
- java.security.auth.login.config
- javax.rmi.ssl.client.enabledCipherSuites
- javax.rmi.ssl.client.enabledProtocols
- ssl.enable
- log4j2.disable.jmx
- log4j2.shutdownHookEnabled
- logback.configurationFile
Newly added and used for tests only:
- invalid-legacy-sstable-root
- legacy-sstable-root
- org.apache.cassandra.tools.UtilALLOW_TOOL_REINIT_FOR_TEST
- org.caffinitas.ohc.segmentCount
- suitename
- sun.stderr.encoding
- sun.stdout.encoding
- test.bbfailhelper.enabled
- write_survey
I've run some tests over my PR, but I'm not sure that I did everything
correctly since I have a lack of experience with the Cassandras test for now. I
will be very appreciative if you tell me what I should pay attention to first.
https://app.circleci.com/pipelines/github/Mmuzaf/cassandra/23/workflows/91bae849-8d91-47d0-8bc6-d9fc6ac7dd76
https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/2100/
> All system properties and environment variables should be accessed via the
> new CassandraRelevantProperties and CassandraRelevantEnv classes
> ---
>
> Key: CASSANDRA-17797
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17797
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Config
>Reporter: Ekaterina Dimitrova
>Assignee: Maxim Muzafarov
>Priority: Low
> Fix For: 4.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Follow up ticket for CASSANDRA-15876 -
> "Always access system properties and environment variables via the new
> CassandraRelevantProperties and CassandraRelevantEnv classes"
> As part of that ticket we moved to the two new classes only
> properties/variables that were currently listed in System Properties Virtual
> Table.
> We have to move to those classes the rest of the properties around the code
> and start using those classes to access all of them.
> +Additional information for newcomers:+
> You might want to start by getting acquainted with
> CassandraRelevantProperties and CassandraRelevantEnv classes. Also, you might
> want to check what changes were done and how the first batch was transferred
> to this new framework as part of
> [CASSANDRA-15876|https://github.com/apache/cassandra/commit/7694c1d191531ac152db55e83bc0db6864a5441e]
> We are interested into the properties accessed currently through
> getProperties around the code.
> As part of CASSANDRA-15876 relevant unit tests were added
> (CassandraRelevantPropertiesTest). To verify the new patch we need to ensure
> that all tests Cassandra pass and also to think about potential update of the
> mentioned test class.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-5534) Writing wide row causes high CPU usage after compaction
[
https://issues.apache.org/jira/browse/CASSANDRA-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams reassigned CASSANDRA-5534:
---
Assignee: Sylvain Lebresne (was: ZheyuanLin)
> Writing wide row causes high CPU usage after compaction
> ---
>
> Key: CASSANDRA-5534
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5534
> Project: Cassandra
> Issue Type: Bug
>Affects Versions: 2.0 beta 1
>Reporter: Ryan McGuire
>Assignee: Sylvain Lebresne
>Priority: Normal
> Fix For: 2.0.0
>
> Attachments: wide_row_stress.trunk.log.txt.gz
>
>
> Introduced in commit -e74c13ff08663d306dcc5cdc99c07e9e6c12ca21- (see below)
> there is a significant slow down when creating a wide row with
> cassandra-stress:
> Testing with the prior (good) commit I used this to write a single wide row,
> which completed rather quickly:
> {code}
> $ ccm create -v git:60f09f0121e0801851b9ab017eddf7e326fa05fb wide-row
> Fetching Cassandra updates...
> Cloning Cassandra (from local cache)
> Checking out requested branch (60f09f0121e0801851b9ab017eddf7e326fa05fb)
> Compiling Cassandra 60f09f0121e0801851b9ab017eddf7e326fa05fb ...
> Current cluster is now: wide-row
> $ ccm populate -n 1
> $ ccm start
> $ time ccm node1 stress -c 1 -S 1000 -n 1
> Created keyspaces. Sleeping 1s for propagation.
> total,interval_op_rate,interval_key_rate,latency/95th/99th,elapsed_time
> 1,0,0,273.3,273.3,273.3,0
> END
> real 0m7.106s
> user 0m1.710s
> sys 0m0.120s
> {code}
> Using the bugged commit (e74c13ff08663d306dcc5cdc99c07e9e6c12ca21) I get a
> significant slow down:
> {code}
> 02:42 PM:~$ ccm create -v git:e74c13ff08663d306dcc5cdc99c07e9e6c12ca21
> wide-row
> Fetching Cassandra updates...
> Current cluster is now: wide-row
> 02:42 PM:~$ ccm populate -n 1
> 02:42 PM:~$ ccm start
> 02:42 PM:~$ time ccm node1 stress -c 1 -S 1000 -n 1
> Created keyspaces. Sleeping 1s for propagation.
> total,interval_op_rate,interval_key_rate,latency,95th,99th,elapsed_time
> 1,0,0,423.2,423.2,423.2,0
> Total operation time : 00:00:00
> END
> real 4m16.394s
> user 0m2.230s
> sys 0m0.137s
> {code}
> Interestingly, the commit in question just says it's a merge from
> cassandra-1.2, but I do not see this same slowdown using that branch, this
> only occurs in trunk.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-5534) Writing wide row causes high CPU usage after compaction
[
https://issues.apache.org/jira/browse/CASSANDRA-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ZheyuanLin reassigned CASSANDRA-5534:
-
Assignee: ZheyuanLin (was: Sylvain Lebresne)
> Writing wide row causes high CPU usage after compaction
> ---
>
> Key: CASSANDRA-5534
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5534
> Project: Cassandra
> Issue Type: Bug
>Affects Versions: 2.0 beta 1
>Reporter: Ryan McGuire
>Assignee: ZheyuanLin
>Priority: Normal
> Fix For: 2.0.0
>
> Attachments: wide_row_stress.trunk.log.txt.gz
>
>
> Introduced in commit -e74c13ff08663d306dcc5cdc99c07e9e6c12ca21- (see below)
> there is a significant slow down when creating a wide row with
> cassandra-stress:
> Testing with the prior (good) commit I used this to write a single wide row,
> which completed rather quickly:
> {code}
> $ ccm create -v git:60f09f0121e0801851b9ab017eddf7e326fa05fb wide-row
> Fetching Cassandra updates...
> Cloning Cassandra (from local cache)
> Checking out requested branch (60f09f0121e0801851b9ab017eddf7e326fa05fb)
> Compiling Cassandra 60f09f0121e0801851b9ab017eddf7e326fa05fb ...
> Current cluster is now: wide-row
> $ ccm populate -n 1
> $ ccm start
> $ time ccm node1 stress -c 1 -S 1000 -n 1
> Created keyspaces. Sleeping 1s for propagation.
> total,interval_op_rate,interval_key_rate,latency/95th/99th,elapsed_time
> 1,0,0,273.3,273.3,273.3,0
> END
> real 0m7.106s
> user 0m1.710s
> sys 0m0.120s
> {code}
> Using the bugged commit (e74c13ff08663d306dcc5cdc99c07e9e6c12ca21) I get a
> significant slow down:
> {code}
> 02:42 PM:~$ ccm create -v git:e74c13ff08663d306dcc5cdc99c07e9e6c12ca21
> wide-row
> Fetching Cassandra updates...
> Current cluster is now: wide-row
> 02:42 PM:~$ ccm populate -n 1
> 02:42 PM:~$ ccm start
> 02:42 PM:~$ time ccm node1 stress -c 1 -S 1000 -n 1
> Created keyspaces. Sleeping 1s for propagation.
> total,interval_op_rate,interval_key_rate,latency,95th,99th,elapsed_time
> 1,0,0,423.2,423.2,423.2,0
> Total operation time : 00:00:00
> END
> real 4m16.394s
> user 0m2.230s
> sys 0m0.137s
> {code}
> Interestingly, the commit in question just says it's a merge from
> cassandra-1.2, but I do not see this same slowdown using that branch, this
> only occurs in trunk.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
