[jira] [Updated] (CASSANDRA-15471) Run Jenkins Cqlsh Tests using the in-tree cassandra-cqlsh-tests.sh
[ https://issues.apache.org/jira/browse/CASSANDRA-15471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Joshi updated CASSANDRA-15471: - Reviewers: Dinesh Joshi > Run Jenkins Cqlsh Tests using the in-tree cassandra-cqlsh-tests.sh > -- > > Key: CASSANDRA-15471 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15471 > Project: Cassandra > Issue Type: Task > Components: Test/dtest >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > > Make the Jenkins Cqlsh test job to use the in-tree cassandra-cqlsh-tests.sh > instead of the same script from the cassandra-builds repo. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15470) Potential Overflow in DatabaseDescriptor Functions That Convert Between KB/MB & Bytes
[
https://issues.apache.org/jira/browse/CASSANDRA-15470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009409#comment-17009409
]
Dinesh Joshi commented on CASSANDRA-15470:
--
[~mallika] sure. Here's some [documentation to get
started|http://cassandra.apache.org/doc/latest/development/how_to_review.html]
and [code
style|http://cassandra.apache.org/doc/latest/development/code_style.html] for
contributing code. Please open a github PR and link it on this ticket and mark
this ticket as Patch Available when you're ready.
> Potential Overflow in DatabaseDescriptor Functions That Convert Between KB/MB
> & Bytes
> -
>
> Key: CASSANDRA-15470
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15470
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Config
>Reporter: Jordan West
>Assignee: Dinesh Joshi
>Priority: Normal
> Fix For: 4.0-rc
>
>
> {{DatabaseDescriptor}} has several functions that convert between user
> supplied sizes in KB/MB and bytes. These are implemented without much
> consistency and, while unlikely, several have the potential to overflow since
> validation on the input is missing. Meanwhile, some widen the number to a
> long correctly. Options include: widening in all places or simply doing
> better validation on start up — currently only the lower bound of the valid
> range is checked for many of these fields.
> List of Affected {{DatabaseDescriptor}} Methods:
> * {{getColumnIndexSize}}
> * {{getColumnIndexCacheSize}}
> * {{getBatchSizeWarnThreshold}}
> * {{getNativeTransportFrameBlockSize}}
> * {{getRepairSessionSpaceInMegabytes}}
> * {{getNativeTransportMaxFrameSize}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-15470) Potential Overflow in DatabaseDescriptor Functions That Convert Between KB/MB & Bytes
[
https://issues.apache.org/jira/browse/CASSANDRA-15470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Joshi reassigned CASSANDRA-15470:
Assignee: Mallika Kulkarni (was: Dinesh Joshi)
> Potential Overflow in DatabaseDescriptor Functions That Convert Between KB/MB
> & Bytes
> -
>
> Key: CASSANDRA-15470
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15470
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Config
>Reporter: Jordan West
>Assignee: Mallika Kulkarni
>Priority: Normal
> Fix For: 4.0-rc
>
>
> {{DatabaseDescriptor}} has several functions that convert between user
> supplied sizes in KB/MB and bytes. These are implemented without much
> consistency and, while unlikely, several have the potential to overflow since
> validation on the input is missing. Meanwhile, some widen the number to a
> long correctly. Options include: widening in all places or simply doing
> better validation on start up — currently only the lower bound of the valid
> range is checked for many of these fields.
> List of Affected {{DatabaseDescriptor}} Methods:
> * {{getColumnIndexSize}}
> * {{getColumnIndexCacheSize}}
> * {{getBatchSizeWarnThreshold}}
> * {{getNativeTransportFrameBlockSize}}
> * {{getRepairSessionSpaceInMegabytes}}
> * {{getNativeTransportMaxFrameSize}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15470) Potential Overflow in DatabaseDescriptor Functions That Convert Between KB/MB & Bytes
[
https://issues.apache.org/jira/browse/CASSANDRA-15470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009403#comment-17009403
]
Jordan West commented on CASSANDRA-15470:
-
Absolutely! I’d be happy to review. For 4.0 I think the validation path makes
is best.
> Potential Overflow in DatabaseDescriptor Functions That Convert Between KB/MB
> & Bytes
> -
>
> Key: CASSANDRA-15470
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15470
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Config
>Reporter: Jordan West
>Assignee: Dinesh Joshi
>Priority: Normal
> Fix For: 4.0-rc
>
>
> {{DatabaseDescriptor}} has several functions that convert between user
> supplied sizes in KB/MB and bytes. These are implemented without much
> consistency and, while unlikely, several have the potential to overflow since
> validation on the input is missing. Meanwhile, some widen the number to a
> long correctly. Options include: widening in all places or simply doing
> better validation on start up — currently only the lower bound of the valid
> range is checked for many of these fields.
> List of Affected {{DatabaseDescriptor}} Methods:
> * {{getColumnIndexSize}}
> * {{getColumnIndexCacheSize}}
> * {{getBatchSizeWarnThreshold}}
> * {{getNativeTransportFrameBlockSize}}
> * {{getRepairSessionSpaceInMegabytes}}
> * {{getNativeTransportMaxFrameSize}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15470) Potential Overflow in DatabaseDescriptor Functions That Convert Between KB/MB & Bytes
[
https://issues.apache.org/jira/browse/CASSANDRA-15470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009403#comment-17009403
]
Jordan West edited comment on CASSANDRA-15470 at 1/7/20 6:50 AM:
-
Absolutely! I’d be happy to review. For 4.0 I think the validation path is
best.
was (Author: jrwest):
Absolutely! I’d be happy to review. For 4.0 I think the validation path makes
is best.
> Potential Overflow in DatabaseDescriptor Functions That Convert Between KB/MB
> & Bytes
> -
>
> Key: CASSANDRA-15470
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15470
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Config
>Reporter: Jordan West
>Assignee: Dinesh Joshi
>Priority: Normal
> Fix For: 4.0-rc
>
>
> {{DatabaseDescriptor}} has several functions that convert between user
> supplied sizes in KB/MB and bytes. These are implemented without much
> consistency and, while unlikely, several have the potential to overflow since
> validation on the input is missing. Meanwhile, some widen the number to a
> long correctly. Options include: widening in all places or simply doing
> better validation on start up — currently only the lower bound of the valid
> range is checked for many of these fields.
> List of Affected {{DatabaseDescriptor}} Methods:
> * {{getColumnIndexSize}}
> * {{getColumnIndexCacheSize}}
> * {{getBatchSizeWarnThreshold}}
> * {{getNativeTransportFrameBlockSize}}
> * {{getRepairSessionSpaceInMegabytes}}
> * {{getNativeTransportMaxFrameSize}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15470) Potential Overflow in DatabaseDescriptor Functions That Convert Between KB/MB & Bytes
[
https://issues.apache.org/jira/browse/CASSANDRA-15470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009399#comment-17009399
]
Mallika Kulkarni commented on CASSANDRA-15470:
--
Could I work on this JIRA?
> Potential Overflow in DatabaseDescriptor Functions That Convert Between KB/MB
> & Bytes
> -
>
> Key: CASSANDRA-15470
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15470
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Config
>Reporter: Jordan West
>Assignee: Dinesh Joshi
>Priority: Normal
> Fix For: 4.0-rc
>
>
> {{DatabaseDescriptor}} has several functions that convert between user
> supplied sizes in KB/MB and bytes. These are implemented without much
> consistency and, while unlikely, several have the potential to overflow since
> validation on the input is missing. Meanwhile, some widen the number to a
> long correctly. Options include: widening in all places or simply doing
> better validation on start up — currently only the lower bound of the valid
> range is checked for many of these fields.
> List of Affected {{DatabaseDescriptor}} Methods:
> * {{getColumnIndexSize}}
> * {{getColumnIndexCacheSize}}
> * {{getBatchSizeWarnThreshold}}
> * {{getNativeTransportFrameBlockSize}}
> * {{getRepairSessionSpaceInMegabytes}}
> * {{getNativeTransportMaxFrameSize}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15487) Reduce LongBTreeTest iteration count
[ https://issues.apache.org/jira/browse/CASSANDRA-15487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009383#comment-17009383 ] Michael Semb Wever edited comment on CASSANDRA-15487 at 1/7/20 5:46 AM: ||branch||circleci||asf jenkins testall|| |[cassandra-2.2_15487|https://github.com/apache/cassandra/compare/cassandra-2.2...thelastpickle:mck/cassandra-2.2_15487]|[circleci|https://circleci.com/gh/thelastpickle/workflows/cassandra/tree/mck%2Fcassandra-2.2_15487]|[!https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/49/badge/icon!|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/49/]| |[cassandra-3.0_15487|https://github.com/apache/cassandra/compare/cassandra-3.0...thelastpickle:mck/cassandra-3.0_15487]|[circleci|https://circleci.com/gh/thelastpickle/workflows/cassandra/tree/mck%2Fcassandra-3.0_15487]|[!https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/50/badge/icon!|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/50/]| |[cassandra-3.11_15487|https://github.com/apache/cassandra/compare/cassandra-3.11...thelastpickle:mck/cassandra-3.11_15487]|[circleci|https://circleci.com/gh/thelastpickle/workflows/cassandra/tree/mck%2Fcassandra-3.11_15487]|[!https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/51/badge/icon!|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/51/]| was (Author: michaelsembwever): ||branch||circleci||asf jenkins testall||asf jenkins dtests|| |[cassandra-2.2_15487|https://github.com/apache/cassandra/compare/cassandra-2.2...thelastpickle:mck/cassandra-2.2_15487]|[circleci|https://circleci.com/gh/thelastpickle/workflows/cassandra/tree/mck%2Fcassandra-2.2_15487]|[!https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/48/badge/icon!|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/48/]| |[cassandra-3.0_15487|https://github.com/apache/cassandra/compare/cassandra-3.0...thelastpickle:mck/cassandra-3.0_15487]|[circleci|https://circleci.com/gh/thelastpickle/workflows/cassandra/tree/mck%2Fcassandra-3.0_15487]|[!https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/48/badge/icon!|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/48/]| |[cassandra-3.11_15487|https://github.com/apache/cassandra/compare/cassandra-3.11...thelastpickle:mck/cassandra-3.11_15487]|[circleci|https://circleci.com/gh/thelastpickle/workflows/cassandra/tree/mck%2Fcassandra-3.11_15487]|[!https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/51/badge/icon!|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/51/]| > Reduce LongBTreeTest iteration count > > > Key: CASSANDRA-15487 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15487 > Project: Cassandra > Issue Type: Task > Components: Test/unit >Reporter: Michael Semb Wever >Priority: Normal > > LongBTreeTest 2.2, 3.0, and 3.11 still takes 8+ hours to run because of the > large iteration counts in it. > In trunk this has already fixed via CASSANDRA-9989 > The iteration count should be reduced to something that is reasonable for > both ASF Jenkins and CircleCI (ie less than an hour). For longer burns one > can just go in at edit the iteration count value. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15487) Reduce LongBTreeTest iteration count
[ https://issues.apache.org/jira/browse/CASSANDRA-15487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009383#comment-17009383 ] Michael Semb Wever edited comment on CASSANDRA-15487 at 1/7/20 5:45 AM: ||branch||circleci||asf jenkins testall||asf jenkins dtests|| |[cassandra-2.2_15487|https://github.com/apache/cassandra/compare/cassandra-2.2...thelastpickle:mck/cassandra-2.2_15487]|[circleci|https://circleci.com/gh/thelastpickle/workflows/cassandra/tree/mck%2Fcassandra-2.2_15487]|[!https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/48/badge/icon!|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/48/]| |[cassandra-3.0_15487|https://github.com/apache/cassandra/compare/cassandra-3.0...thelastpickle:mck/cassandra-3.0_15487]|[circleci|https://circleci.com/gh/thelastpickle/workflows/cassandra/tree/mck%2Fcassandra-3.0_15487]|[!https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/48/badge/icon!|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/48/]| |[cassandra-3.11_15487|https://github.com/apache/cassandra/compare/cassandra-3.11...thelastpickle:mck/cassandra-3.11_15487]|[circleci|https://circleci.com/gh/thelastpickle/workflows/cassandra/tree/mck%2Fcassandra-3.11_15487]|[!https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/51/badge/icon!|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-pipeline/51/]| was (Author: michaelsembwever): Patches at - https://github.com/thelastpickle/cassandra/tree/mck/cassandra-2.2_15487 - https://github.com/thelastpickle/cassandra/tree/mck/cassandra-3.0_15487 - https://github.com/thelastpickle/cassandra/tree/mck/cassandra-3.11_15487 > Reduce LongBTreeTest iteration count > > > Key: CASSANDRA-15487 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15487 > Project: Cassandra > Issue Type: Task > Components: Test/unit >Reporter: Michael Semb Wever >Priority: Normal > > LongBTreeTest 2.2, 3.0, and 3.11 still takes 8+ hours to run because of the > large iteration counts in it. > In trunk this has already fixed via CASSANDRA-9989 > The iteration count should be reduced to something that is reasonable for > both ASF Jenkins and CircleCI (ie less than an hour). For longer burns one > can just go in at edit the iteration count value. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15487) Reduce LongBTreeTest iteration count
[ https://issues.apache.org/jira/browse/CASSANDRA-15487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-15487: --- Change Category: Quality Assurance Complexity: Low Hanging Fruit Status: Open (was: Triage Needed) > Reduce LongBTreeTest iteration count > > > Key: CASSANDRA-15487 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15487 > Project: Cassandra > Issue Type: Task > Components: Test/unit >Reporter: Michael Semb Wever >Priority: Normal > > LongBTreeTest 2.2, 3.0, and 3.11 still takes 8+ hours to run because of the > large iteration counts in it. > In trunk this has already fixed via CASSANDRA-9989 > The iteration count should be reduced to something that is reasonable for > both ASF Jenkins and CircleCI (ie less than an hour). For longer burns one > can just go in at edit the iteration count value. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15487) Reduce LongBTreeTest iteration count
[ https://issues.apache.org/jira/browse/CASSANDRA-15487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-15487: --- Test and Documentation Plan: ASF Jenkins Status: Patch Available (was: Open) > Reduce LongBTreeTest iteration count > > > Key: CASSANDRA-15487 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15487 > Project: Cassandra > Issue Type: Task > Components: Test/unit >Reporter: Michael Semb Wever >Priority: Normal > > LongBTreeTest 2.2, 3.0, and 3.11 still takes 8+ hours to run because of the > large iteration counts in it. > In trunk this has already fixed via CASSANDRA-9989 > The iteration count should be reduced to something that is reasonable for > both ASF Jenkins and CircleCI (ie less than an hour). For longer burns one > can just go in at edit the iteration count value. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15487) Reduce LongBTreeTest iteration count
[ https://issues.apache.org/jira/browse/CASSANDRA-15487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009383#comment-17009383 ] Michael Semb Wever commented on CASSANDRA-15487: Patches at - https://github.com/thelastpickle/cassandra/tree/mck/cassandra-2.2_15487 - https://github.com/thelastpickle/cassandra/tree/mck/cassandra-3.0_15487 - https://github.com/thelastpickle/cassandra/tree/mck/cassandra-3.11_15487 > Reduce LongBTreeTest iteration count > > > Key: CASSANDRA-15487 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15487 > Project: Cassandra > Issue Type: Task > Components: Test/unit >Reporter: Michael Semb Wever >Priority: Normal > > LongBTreeTest 2.2, 3.0, and 3.11 still takes 8+ hours to run because of the > large iteration counts in it. > In trunk this has already fixed via CASSANDRA-9989 > The iteration count should be reduced to something that is reasonable for > both ASF Jenkins and CircleCI (ie less than an hour). For longer burns one > can just go in at edit the iteration count value. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15487) Reduce LongBTreeTest iteration count
[ https://issues.apache.org/jira/browse/CASSANDRA-15487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-15487: --- Test and Documentation Plan: ASF Jenkins burn tests (was: ASF Jenkins) > Reduce LongBTreeTest iteration count > > > Key: CASSANDRA-15487 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15487 > Project: Cassandra > Issue Type: Task > Components: Test/unit >Reporter: Michael Semb Wever >Priority: Normal > > LongBTreeTest 2.2, 3.0, and 3.11 still takes 8+ hours to run because of the > large iteration counts in it. > In trunk this has already fixed via CASSANDRA-9989 > The iteration count should be reduced to something that is reasonable for > both ASF Jenkins and CircleCI (ie less than an hour). For longer burns one > can just go in at edit the iteration count value. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15487) Reduce LongBTreeTest iteration count
Michael Semb Wever created CASSANDRA-15487: -- Summary: Reduce LongBTreeTest iteration count Key: CASSANDRA-15487 URL: https://issues.apache.org/jira/browse/CASSANDRA-15487 Project: Cassandra Issue Type: Task Components: Test/unit Reporter: Michael Semb Wever LongBTreeTest 2.2, 3.0, and 3.11 still takes 8+ hours to run because of the large iteration counts in it. In trunk this has already fixed via CASSANDRA-9989 The iteration count should be reduced to something that is reasonable for both ASF Jenkins and CircleCI (ie less than an hour). For longer burns one can just go in at edit the iteration count value. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15486) Dynamo
DeepakVohra created CASSANDRA-15486: --- Summary: Dynamo Key: CASSANDRA-15486 URL: https://issues.apache.org/jira/browse/CASSANDRA-15486 Project: Cassandra Issue Type: Sub-task Components: Documentation/Website Reporter: DeepakVohra Assignee: Dinesh Joshi Added new sections to Dynamo page. https://github.com/apache/cassandra/pull/415 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15485) Added Full Repair Example
DeepakVohra created CASSANDRA-15485: --- Summary: Added Full Repair Example Key: CASSANDRA-15485 URL: https://issues.apache.org/jira/browse/CASSANDRA-15485 Project: Cassandra Issue Type: Sub-task Components: Documentation/Website Reporter: DeepakVohra Assignee: Blake Eggleston Added full repair example. https://github.com/apache/cassandra/pull/414 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15484) Read Repair
DeepakVohra created CASSANDRA-15484: --- Summary: Read Repair Key: CASSANDRA-15484 URL: https://issues.apache.org/jira/browse/CASSANDRA-15484 Project: Cassandra Issue Type: Sub-task Components: Documentation/Website Reporter: DeepakVohra Assignee: Dinesh Joshi Added page on Read Repair. https://github.com/apache/cassandra/pull/413 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15483) Overview
DeepakVohra created CASSANDRA-15483: --- Summary: Overview Key: CASSANDRA-15483 URL: https://issues.apache.org/jira/browse/CASSANDRA-15483 Project: Cassandra Issue Type: Sub-task Components: Documentation/Website Reporter: DeepakVohra Assignee: Nate McCall Added page on Overview. https://github.com/apache/cassandra/pull/412 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15482) Guarantees
DeepakVohra created CASSANDRA-15482: --- Summary: Guarantees Key: CASSANDRA-15482 URL: https://issues.apache.org/jira/browse/CASSANDRA-15482 Project: Cassandra Issue Type: Sub-task Components: Documentation/Website Reporter: DeepakVohra Assignee: Dinesh Joshi Added a page on Guarantees. https://github.com/apache/cassandra/pull/411 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15481) Data Modeling
DeepakVohra created CASSANDRA-15481: --- Summary: Data Modeling Key: CASSANDRA-15481 URL: https://issues.apache.org/jira/browse/CASSANDRA-15481 Project: Cassandra Issue Type: Sub-task Components: Documentation/Website Reporter: DeepakVohra Assignee: Dinesh Joshi Added a page on data modeling. https://github.com/apache/cassandra/pull/410 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15480) Bulk Loading
DeepakVohra created CASSANDRA-15480: --- Summary: Bulk Loading Key: CASSANDRA-15480 URL: https://issues.apache.org/jira/browse/CASSANDRA-15480 Project: Cassandra Issue Type: Sub-task Components: Documentation/Website Reporter: DeepakVohra Assignee: Nate McCall Added bulk loading page. https://github.com/apache/cassandra/pull/409 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15479) Backups - updated
DeepakVohra created CASSANDRA-15479: --- Summary: Backups - updated Key: CASSANDRA-15479 URL: https://issues.apache.org/jira/browse/CASSANDRA-15479 Project: Cassandra Issue Type: Sub-task Components: Documentation/Website Reporter: DeepakVohra Assignee: Chris Lohfink Added Backups page. https://github.com/apache/cassandra/pull/408 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15478) Improved Messaging
DeepakVohra created CASSANDRA-15478: --- Summary: Improved Messaging Key: CASSANDRA-15478 URL: https://issues.apache.org/jira/browse/CASSANDRA-15478 Project: Cassandra Issue Type: Sub-task Components: Documentation/Website Reporter: DeepakVohra Assignee: Dinesh Joshi Added a page on improved messaging. https://github.com/apache/cassandra/pull/407 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15477) Improved Streaming
DeepakVohra created CASSANDRA-15477: --- Summary: Improved Streaming Key: CASSANDRA-15477 URL: https://issues.apache.org/jira/browse/CASSANDRA-15477 Project: Cassandra Issue Type: Sub-task Components: Documentation/Website Reporter: DeepakVohra Assignee: Dinesh Joshi Added a page on improved streaming. https://github.com/apache/cassandra/pull/406 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15476) Transient Replication - New Feature
DeepakVohra created CASSANDRA-15476: --- Summary: Transient Replication - New Feature Key: CASSANDRA-15476 URL: https://issues.apache.org/jira/browse/CASSANDRA-15476 Project: Cassandra Issue Type: Sub-task Components: Documentation/Website Reporter: DeepakVohra Assignee: Blake Eggleston Added a page on transient replication, a new feature. https://github.com/apache/cassandra/pull/405 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15475) Full Query Logging - New Feature
DeepakVohra created CASSANDRA-15475: --- Summary: Full Query Logging - New Feature Key: CASSANDRA-15475 URL: https://issues.apache.org/jira/browse/CASSANDRA-15475 Project: Cassandra Issue Type: Sub-task Components: Documentation/Website Reporter: DeepakVohra Assignee: Dinesh Joshi Added a page on Full Query logging, a new feature. https://github.com/apache/cassandra/pull/404 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15474) Audit Logging - New Feature
DeepakVohra created CASSANDRA-15474: --- Summary: Audit Logging - New Feature Key: CASSANDRA-15474 URL: https://issues.apache.org/jira/browse/CASSANDRA-15474 Project: Cassandra Issue Type: Sub-task Components: Documentation/Website Reporter: DeepakVohra Assignee: Vinay Chella Added a page on audit logging, a new feature. https://github.com/apache/cassandra/pull/403 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15473) New feature - Virtual Tables
DeepakVohra created CASSANDRA-15473: --- Summary: New feature - Virtual Tables Key: CASSANDRA-15473 URL: https://issues.apache.org/jira/browse/CASSANDRA-15473 Project: Cassandra Issue Type: Sub-task Components: Documentation/Website Reporter: DeepakVohra Assignee: Chris Lohfink Added a page on virtual tables, a new feature. https://github.com/apache/cassandra/pull/402 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15463) Fix in-jvm dtest java 11 compatibility
[
https://issues.apache.org/jira/browse/CASSANDRA-15463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009265#comment-17009265
]
David Capwell commented on CASSANDRA-15463:
---
LGTM. You could allocate less by calling
\{code}.collect(Collectors.counting());\{code} but since this is a test the
current version is fine.
+1
> Fix in-jvm dtest java 11 compatibility
> --
>
> Key: CASSANDRA-15463
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15463
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest
>Reporter: Blake Eggleston
>Assignee: Blake Eggleston
>Priority: Normal
> Fix For: 4.0-alpha
>
>
> The url classloader used by the in jvm dtests is not accessible by default in
> java 11.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-15471) Run Jenkins Cqlsh Tests using the in-tree cassandra-cqlsh-tests.sh
[ https://issues.apache.org/jira/browse/CASSANDRA-15471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Joshi reassigned CASSANDRA-15471: Assignee: Michael Semb Wever > Run Jenkins Cqlsh Tests using the in-tree cassandra-cqlsh-tests.sh > -- > > Key: CASSANDRA-15471 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15471 > Project: Cassandra > Issue Type: Task > Components: Test/dtest >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > > Make the Jenkins Cqlsh test job to use the in-tree cassandra-cqlsh-tests.sh > instead of the same script from the cassandra-builds repo. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-15470) Potential Overflow in DatabaseDescriptor Functions That Convert Between KB/MB & Bytes
[
https://issues.apache.org/jira/browse/CASSANDRA-15470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Joshi reassigned CASSANDRA-15470:
Assignee: Dinesh Joshi
> Potential Overflow in DatabaseDescriptor Functions That Convert Between KB/MB
> & Bytes
> -
>
> Key: CASSANDRA-15470
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15470
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Config
>Reporter: Jordan West
>Assignee: Dinesh Joshi
>Priority: Normal
> Fix For: 4.0-rc
>
>
> {{DatabaseDescriptor}} has several functions that convert between user
> supplied sizes in KB/MB and bytes. These are implemented without much
> consistency and, while unlikely, several have the potential to overflow since
> validation on the input is missing. Meanwhile, some widen the number to a
> long correctly. Options include: widening in all places or simply doing
> better validation on start up — currently only the lower bound of the valid
> range is checked for many of these fields.
> List of Affected {{DatabaseDescriptor}} Methods:
> * {{getColumnIndexSize}}
> * {{getColumnIndexCacheSize}}
> * {{getBatchSizeWarnThreshold}}
> * {{getNativeTransportFrameBlockSize}}
> * {{getRepairSessionSpaceInMegabytes}}
> * {{getNativeTransportMaxFrameSize}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14917) Nodetool netstats displays incorrect information on streaming
[
https://issues.apache.org/jira/browse/CASSANDRA-14917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009253#comment-17009253
]
Dinesh Joshi commented on CASSANDRA-14917:
--
I haven't been able to repro this issue. Can you try with the latest 3.11? I
believe it is 3.11.5?
> Nodetool netstats displays incorrect information on streaming
> -
>
> Key: CASSANDRA-14917
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14917
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Streaming and Messaging
>Reporter: Igor Zubchenok
>Assignee: Dinesh Joshi
>Priority: Low
>
> nodetool netstats command displays 'Sending 0 files' and non-zero 'bytes
> total' during node decommission.
> {code:java}
> Sending 0 files, 198933290919 bytes total. Already sent 0 files, 0 bytes total
> {code}
> Complete notetool netstats response
> {code:java}
> # nodetool netstats | grep -v 100%
> Mode: LEAVING
> Unbootstrap 67096090-f604-11e8--03532290668f
> /X.X.X.X
> Sending 8039 files, 174905861575 bytes total. Already sent 3147
> files, 39883605552 bytes total
>
> /var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100884-big-Data.db
> 1866267759/8275615307 bytes(22%) sent to idx:0/5.9.54.111
> /X.X.X.X
> Sending 5475 files, 167399940563 bytes total. Already sent 2416
> files, 49417386715 bytes total
>
> /var/lib/cassandra/data/app_tracks/tracks-bd8310f086b711e7b6cbfd84ea9f1f78/mc-459374-big-Data.db
> 10192112/17529144 bytes(58%) sent to idx:0/5.9.59.101
> /X.X.X.X
> Sending 5843 files, 181124719187 bytes total. Already sent 2613
> files, 57001466824 bytes total
>
> /var/lib/cassandra/data/app_tracks/tracks-bd8310f086b711e7b6cbfd84ea9f1f78/mc-461873-big-Data.db
> 1439600/93308008 bytes(1%) sent to idx:0/46.4.31.97
> /X.X.X.X
> Sending 7303 files, 213976795121 bytes total. Already sent 1811
> files, 28956350780 bytes total
>
> /var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100465-big-Data.db
> 3719051/37149976 bytes(10%) sent to idx:0/144.76.85.237
> /X.X.X.X
> Sending 7893 files, 204271020294 bytes total. Already sent 2397
> files, 36086600359 bytes total
>
> /var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100197-big-Data.db
> 646314/8291439 bytes(7%) sent to idx:0/144.76.29.39
> /X.X.X.X
> Sending 0 files, 198933290919 bytes total. Already sent 0 files, 0
> bytes total
> /X.X.X.X
> Sending 6159 files, 187102577561 bytes total. Already sent 1526
> files, 26019708822 bytes total
>
> /var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100685-big-Data.db
> 52211410/67213497 bytes(77%) sent to idx:0/144.76.85.182
> /X.X.X.X
> Sending 6534 files, 193239644509 bytes total. Already sent 2367
> files, 48105187871 bytes total
>
> /var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100884-big-Data.db
> 5907583715/10068538729 bytes(58%) sent to idx:0/5.9.48.222
> /X.X.X.X
> Sending 5923 files, 213438389441 bytes total. Already sent 1663
> files, 32469866925 bytes total
> Read Repair Statistics:
> Attempted: 3537331
> Mismatch (Blocking): 2193
> Mismatch (Background): 4326
> Pool NameActive Pending Completed Dropped
> Large messages n/a18 87460 746
> Small messages n/a 8 9837560424 12410
> Gossip messages n/a 87666199 84717
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15428) First of the new features - Support for Java 11
[ https://issues.apache.org/jira/browse/CASSANDRA-15428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Joshi updated CASSANDRA-15428: - Fix Version/s: 4.0 Source Control Link: https://github.com/apache/cassandra/commit/0c4335d6b8b7528b0acef372687e67afb1f16714 Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed, thanks [~dvohra]! > First of the new features - Support for Java 11 > --- > > Key: CASSANDRA-15428 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15428 > Project: Cassandra > Issue Type: Sub-task > Components: Legacy/Documentation and Website >Reporter: DeepakVohra >Assignee: Dinesh Joshi >Priority: Normal > Fix For: 4.0 > > > A pull request for first of the new features in 4.0. > - As 4.0 is a major release created a new folder called "new" > - Added a _index.rst_ to the _new_ folder > - Added _new/index_ to the top-level _index.rst_ > - Added _java11.rst_ to the _new_ folder for the new feature _Support for > Java 11_ > https://github.com/apache/cassandra/pull/383 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated: Add documentation for Java 11 support in Cassandra
This is an automated email from the ASF dual-hosted git repository.
djoshi 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 0c4335d Add documentation for Java 11 support in Cassandra
0c4335d is described below
commit 0c4335d6b8b7528b0acef372687e67afb1f16714
Author: dvohra
AuthorDate: Thu Nov 14 14:05:00 2019 -0800
Add documentation for Java 11 support in Cassandra
Patch by Deepak Vohra; Reviewed by Dinesh Joshi for CASSANDRA-15428
---
CHANGES.txt| 1 +
doc/source/index.rst | 1 +
doc/source/{ => new}/index.rst | 30 ++---
doc/source/new/java11.rst | 274 +
4 files changed, 285 insertions(+), 21 deletions(-)
diff --git a/CHANGES.txt b/CHANGES.txt
index db5e3dc..dc1b592 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -10,6 +10,7 @@
* Make sure all exceptions are propagated in DebuggableThreadPoolExecutor
(CASSANDRA-15332)
* Make it possible to resize concurrent read / write thread pools at runtime
(CASSANDRA-15277)
* Close channels on error (CASSANDRA-15407)
+ * Add documentation for Java 11 support in Cassandra (CASSANDRA-15428)
Merged from 3.11:
* Fix nodetool compactionstats showing extra pending task for TWCS - patch
implemented (CASSANDRA-15409)
* Fix SELECT JSON formatting for the "duration" type (CASSANDRA-15075)
diff --git a/doc/source/index.rst b/doc/source/index.rst
index 9f8016b..d8fffa8 100644
--- a/doc/source/index.rst
+++ b/doc/source/index.rst
@@ -27,6 +27,7 @@ Contents:
:maxdepth: 2
getting_started/index
+ new/index
architecture/index
data_modeling/index
cql/index
diff --git a/doc/source/index.rst b/doc/source/new/index.rst
similarity index 55%
copy from doc/source/index.rst
copy to doc/source/new/index.rst
index 9f8016b..18a4b5b 100644
--- a/doc/source/index.rst
+++ b/doc/source/new/index.rst
@@ -14,29 +14,17 @@
.. See the License for the specific language governing permissions and
.. limitations under the License.
-Welcome to Apache Cassandra's documentation!
-
+New Features in Apache Cassandra 4.0
+
-This is the official documentation for `Apache Cassandra
`__ |version|. If you would like
-to contribute to this documentation, you are welcome to do so by submitting
your contribution like any other patch
-following `these instructions
`__.
-
-Contents:
+This section covers the new features in Apache Cassandra 4.0.
.. toctree::
:maxdepth: 2
- getting_started/index
- architecture/index
- data_modeling/index
- cql/index
- configuration/index
- operating/index
- tools/index
- troubleshooting/index
- development/index
- faq/index
- plugins/index
-
- bugs
- contactus
+ java11
+ virtualtables
+ auditlogging
+ fqllogging
+ transientreplication
+
diff --git a/doc/source/new/java11.rst b/doc/source/new/java11.rst
new file mode 100644
index 000..df906d4
--- /dev/null
+++ b/doc/source/new/java11.rst
@@ -0,0 +1,274 @@
+.. Licensed to the Apache Software Foundation (ASF) under one
+.. or more contributor license agreements. See the NOTICE file
+.. distributed with this work for additional information
+.. regarding copyright ownership. The ASF licenses this file
+.. to you under the Apache License, Version 2.0 (the
+.. "License"); you may not use this file except in compliance
+.. with the License. You may obtain a copy of the License at
+..
+.. http://www.apache.org/licenses/LICENSE-2.0
+..
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS,
+.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+.. See the License for the specific language governing permissions and
+.. limitations under the License.
+
+Support for Java 11
+---
+
+In the new Java release cadence a new Java version is made available every six
months. The more frequent release cycle
+is favored as it brings new Java features to the developers as and when they
are developed without the wait that the
+earlier 3 year release model incurred. Not every Java version is a Long Term
Support (LTS) version. After Java 8 the
+next LTS version is Java 11. Java 9, 10, 12 and 13 are all non-LTS versions.
+
+One of the objectives of the Apache Cassandra 4.0 version is to support the
recent LTS Java versions 8 and 11 (`CASSANDRA-9608
+`_). Java 8 and
+Java 11 may be used to build and run Apache Cassandra 4.0.
+
+**Note**: Support for JDK 11 in Apache Cassandra 4.0 is an experimental
feature, and not recommended for production use.
+
+Support Matrix
+^^
+
+The support
[jira] [Updated] (CASSANDRA-15428) First of the new features - Support for Java 11
[ https://issues.apache.org/jira/browse/CASSANDRA-15428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Joshi updated CASSANDRA-15428: - Status: Ready to Commit (was: Review In Progress) +1. Looks great [~dvohra]. > First of the new features - Support for Java 11 > --- > > Key: CASSANDRA-15428 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15428 > Project: Cassandra > Issue Type: Sub-task > Components: Legacy/Documentation and Website >Reporter: DeepakVohra >Assignee: Dinesh Joshi >Priority: Normal > > A pull request for first of the new features in 4.0. > - As 4.0 is a major release created a new folder called "new" > - Added a _index.rst_ to the _new_ folder > - Added _new/index_ to the top-level _index.rst_ > - Added _java11.rst_ to the _new_ folder for the new feature _Support for > Java 11_ > https://github.com/apache/cassandra/pull/383 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15428) First of the new features - Support for Java 11
[ https://issues.apache.org/jira/browse/CASSANDRA-15428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Joshi updated CASSANDRA-15428: - Reviewers: Dinesh Joshi, Dinesh Joshi (was: Dinesh Joshi) Dinesh Joshi, Dinesh Joshi (was: Dinesh Joshi) Status: Review In Progress (was: Patch Available) > First of the new features - Support for Java 11 > --- > > Key: CASSANDRA-15428 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15428 > Project: Cassandra > Issue Type: Sub-task > Components: Legacy/Documentation and Website >Reporter: DeepakVohra >Assignee: Dinesh Joshi >Priority: Normal > > A pull request for first of the new features in 4.0. > - As 4.0 is a major release created a new folder called "new" > - Added a _index.rst_ to the _new_ folder > - Added _new/index_ to the top-level _index.rst_ > - Added _java11.rst_ to the _new_ folder for the new feature _Support for > Java 11_ > https://github.com/apache/cassandra/pull/383 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15463) Fix in-jvm dtest java 11 compatibility
[ https://issues.apache.org/jira/browse/CASSANDRA-15463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15463: -- Reviewers: Alex Petrov, David Capwell, David Capwell (was: Alex Petrov, David Capwell) Alex Petrov, David Capwell, David Capwell (was: Alex Petrov) Status: Review In Progress (was: Patch Available) Started testing this now. org.apache.cassandra.distributed.test.MessageForwardingTest#mutationsForwardedToAllReplicasTest is failing since the logic in the stream doesn't seem to be executing anymore. In speaking with [~bdeggleston] seems that streams is able to avoid calling the map logic to compute count, so map gets skipped (which causes the test to fail). I have yet to replicate the issue that the build change is trying to solve > Fix in-jvm dtest java 11 compatibility > -- > > Key: CASSANDRA-15463 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15463 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest >Reporter: Blake Eggleston >Assignee: Blake Eggleston >Priority: Normal > Fix For: 4.0-alpha > > > The url classloader used by the in jvm dtests is not accessible by default in > java 11. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15428) First of the new features - Support for Java 11
[ https://issues.apache.org/jira/browse/CASSANDRA-15428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Joshi updated CASSANDRA-15428: - Authors: DeepakVohra Impacts: Docs (was: None) Test and Documentation Plan: This is a documentation task. Status: Patch Available (was: Open) > First of the new features - Support for Java 11 > --- > > Key: CASSANDRA-15428 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15428 > Project: Cassandra > Issue Type: Sub-task > Components: Legacy/Documentation and Website >Reporter: DeepakVohra >Assignee: Dinesh Joshi >Priority: Normal > > A pull request for first of the new features in 4.0. > - As 4.0 is a major release created a new folder called "new" > - Added a _index.rst_ to the _new_ folder > - Added _new/index_ to the top-level _index.rst_ > - Added _java11.rst_ to the _new_ folder for the new feature _Support for > Java 11_ > https://github.com/apache/cassandra/pull/383 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-14781) Log message when mutation passed to CommitLog#add(Mutation) is too large is not descriptive enough
[
https://issues.apache.org/jira/browse/CASSANDRA-14781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009182#comment-17009182
]
Jordan West edited comment on CASSANDRA-14781 at 1/6/20 9:29 PM:
-
Thanks for picking this up [~n.v.harikrishna]. Comments below.
General:
* Since this change logs keys which in some use cases may contain PII that
users may not want logged, should we add a flag to gate this feature?
* I don’t believe this address [~aleksey]'s concern that the exception be
propagated to the client vs. timing out. At a minimum, we should add an in-jvm
dtest to show it does (I’m happy to help contribute this unless you’d like to).
Its possible to split the patch into two parts (one that changes the logging
and one that propagates the exception), however, in prod I’ve seen the lack of
this logging and the timeouts be an issue so they are definitely both worth
addressing.
CommitLog:
* With your change to validate the size using serializedSize, it looks like
its no longer be necessary to use the scratch buffer (which seems to be used
primarily to get the length w/o calculating serialized size). However, I wonder
if the original approach is better performance wise since we are already
serializing the mutation. It would be good to benchmark workloads with all
mutations exceeding max size, no mutations exceeding max size, and mixed to
check because I can imagine how what I said is wrong as well. We should check
if there is any difference or if its negligible.
SizeHolder:
* Since the only call to {{#getSize()}} currently is
{{IMutation#validateSize}} which is only called once from CommitLog.java.
Consider removing the memoization.
* If the memoization is still desired, I don’t think its necessary to have
fields for each version since a mutation is executed within a single version of
Cassandra (it may cross network boundaries and thus versions but at this point
we have a new SizeHolder). Using a single variable would cleanup {{#getSize}}
considerably. Further, it would be cleaner/less error prone to memoize the size
in the mutation since nothing maps the object passed to {{#getSize}} to the
stored value.
MutationExceededMaxSizeException:
* {{prepareMessage}} recalculates the mutation size. While this is an
exceptional case it is still common. Perhaps a place where the memoization
could be helpful?
* Spelling error: maxMutaionSize
* I almost always prefer a configurable limit to something hardcoded and
requiring recompilation to change
Other:
* I don’t think {{IMutation.getMaxMutationSize()}} is necessary. Use
{{DatabaseDescriptor}} instead. This is more typical of Cassandra config code.
Further, the original code only called
{{DatabaseDescriptor.getMaxMutationSize()}} once instead of for every write.
Unless we are going to make it a hot-prop its worth putting back to how it was.
* We have a few {{Serializer}} interfaces in C* already, consider renaming
{{SizeHolder.Serializer}} if its kept
was (Author: jrwest):
Thanks for picking this up [~n.v.harikrishna]. Comments below.
* General:
* Since this change logs keys which in some use cases may contain PII that
users may not want logged, should we add a flag to gate this feature?
* I don’t believe this address [~aleksey]'s concern that the exception be
propagated to the client vs. timing out. At a minimum, we should add an in-jvm
dtest to show it does (I’m happy to help contribute this unless you’d like to).
Its possible to split the patch into two parts (one that changes the logging
and one that propagates the exception), however, in prod I’ve seen the lack of
this logging and the timeouts be an issue so they are definitely both worth
addressing.
* CommitLog:
* With your change to validate the size using serializedSize, it looks like
its no longer be necessary to use the scratch buffer (which seems to be used
primarily to get the length w/o calculating serialized size). However, I wonder
if the original approach is better performance wise since we are already
serializing the mutation. It would be good to benchmark workloads with all
mutations exceeding max size, no mutations exceeding max size, and mixed to
check because I can imagine how what I said is wrong as well. We should check
if there is any difference or if its negligible.
* SizeHolder:
* Since the only call to \{{#getSize()}} currently is
\{{IMutation#validateSize}} which is only called once from CommitLog.java.
Consider removing the memoization.
* If the memoization is still desired, I don’t think its necessary to have
fields for each version since a mutation is executed within a single version of
Cassandra (it may cross network boundaries and thus versions but at this point
we have a new SizeHolder). Using a single variable would cleanup \{{#getSize}}
considerably. Further, it would be cleaner/less
[jira] [Updated] (CASSANDRA-14781) Log message when mutation passed to CommitLog#add(Mutation) is too large is not descriptive enough
[ https://issues.apache.org/jira/browse/CASSANDRA-14781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan West updated CASSANDRA-14781: Status: Changes Suggested (was: Review In Progress) > Log message when mutation passed to CommitLog#add(Mutation) is too large is > not descriptive enough > -- > > Key: CASSANDRA-14781 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14781 > Project: Cassandra > Issue Type: Bug > Components: Consistency/Hints, Local/Commit Log, Messaging/Client >Reporter: Jordan West >Assignee: Tom Petracca >Priority: Normal > Labels: protocolv5 > Fix For: 4.0-beta > > Attachments: CASSANDRA-14781.patch, CASSANDRA-14781_3.0.patch, > CASSANDRA-14781_3.11.patch > > > When hitting > [https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/db/commitlog/CommitLog.java#L256-L257], > the log message produced does not help the operator track down what data is > being written. At a minimum the keyspace and cfIds involved would be useful > (and are available) – more detail might not be reasonable to include. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14781) Log message when mutation passed to CommitLog#add(Mutation) is too large is not descriptive enough
[
https://issues.apache.org/jira/browse/CASSANDRA-14781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jordan West updated CASSANDRA-14781:
Reviewers: Chris Lohfink, Jordan West, Jordan West (was: Chris Lohfink,
Jordan West)
Chris Lohfink, Jordan West, Jordan West (was: Chris Lohfink)
Status: Review In Progress (was: Patch Available)
Thanks for picking this up [~n.v.harikrishna]. Comments below.
* General:
* Since this change logs keys which in some use cases may contain PII that
users may not want logged, should we add a flag to gate this feature?
* I don’t believe this address [~aleksey]'s concern that the exception be
propagated to the client vs. timing out. At a minimum, we should add an in-jvm
dtest to show it does (I’m happy to help contribute this unless you’d like to).
Its possible to split the patch into two parts (one that changes the logging
and one that propagates the exception), however, in prod I’ve seen the lack of
this logging and the timeouts be an issue so they are definitely both worth
addressing.
* CommitLog:
* With your change to validate the size using serializedSize, it looks like
its no longer be necessary to use the scratch buffer (which seems to be used
primarily to get the length w/o calculating serialized size). However, I wonder
if the original approach is better performance wise since we are already
serializing the mutation. It would be good to benchmark workloads with all
mutations exceeding max size, no mutations exceeding max size, and mixed to
check because I can imagine how what I said is wrong as well. We should check
if there is any difference or if its negligible.
* SizeHolder:
* Since the only call to \{{#getSize()}} currently is
\{{IMutation#validateSize}} which is only called once from CommitLog.java.
Consider removing the memoization.
* If the memoization is still desired, I don’t think its necessary to have
fields for each version since a mutation is executed within a single version of
Cassandra (it may cross network boundaries and thus versions but at this point
we have a new SizeHolder). Using a single variable would cleanup \{{#getSize}}
considerably. Further, it would be cleaner/less error prone to memoize the size
in the mutation since nothing maps the object passed to \{{#getSize}} to the
stored value.
* MutationExceededMaxSizeException:
* {\{prepareMessage}} recalculates the mutation size. While this is an
exceptional case it is still common. Perhaps a place where the memoization
could be helpful?
* Spelling error: maxMutaionSize
* I almost always prefer a configurable limit to something hardcoded and
requiring recompilation to change
* I don’t think \{{IMutation.getMaxMutationSize()}} is necessary. Use
\{{DatabaseDescriptor}} instead. This is more typical of Cassandra config code.
Further, the original code only called
\{{DatabaseDescriptor.getMaxMutationSize()}} once instead of for every write.
Unless we are going to make it a hot-prop its worth putting back to how it was.
* We have a few \{{Serializer}} interfaces in C* already, consider renaming
\{{SizeHolder.Serializer}} if its kept
> Log message when mutation passed to CommitLog#add(Mutation) is too large is
> not descriptive enough
> --
>
> Key: CASSANDRA-14781
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14781
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Hints, Local/Commit Log, Messaging/Client
>Reporter: Jordan West
>Assignee: Tom Petracca
>Priority: Normal
> Labels: protocolv5
> Fix For: 4.0-beta
>
> Attachments: CASSANDRA-14781.patch, CASSANDRA-14781_3.0.patch,
> CASSANDRA-14781_3.11.patch
>
>
> When hitting
> [https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/db/commitlog/CommitLog.java#L256-L257],
> the log message produced does not help the operator track down what data is
> being written. At a minimum the keyspace and cfIds involved would be useful
> (and are available) – more detail might not be reasonable to include.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15472) Read failure due to exception from metrics-core dependency
[
https://issues.apache.org/jira/browse/CASSANDRA-15472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumanth Pasupuleti updated CASSANDRA-15472:
---
Description:
Stacktrace
{code:java}
Uncaught exception on thread Thread[SharedPool-Worker-27,5,main]: {}
java.util.NoSuchElementException: null
at
java.util.concurrent.ConcurrentSkipListMap.firstKey(ConcurrentSkipListMap.java:2053)
~[na:1.8.0_222]
at
com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:102)
~[metrics-core-2.2.0.jar:na]
at
com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:81)
~[metrics-core-2.2.0.jar:na]
at com.yammer.metrics.core.Histogram.update(Histogram.java:110)
~[metrics-core-2.2.0.jar:na]
at com.yammer.metrics.core.Timer.update(Timer.java:198)
~[metrics-core-2.2.0.jar:na]
at com.yammer.metrics.core.Timer.update(Timer.java:76)
~[metrics-core-2.2.0.jar:na]
at
org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:108)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:114)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1897)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at org.apache.cassandra.db.Keyspace.getRow(Keyspace.java:353)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.db.SliceFromReadCommand.getRow(SliceFromReadCommand.java:85)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.db.ReadVerbHandler.doVerb(ReadVerbHandler.java:47)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:64)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
~[na:1.8.0_222]
at
org.apache.cassandra.concurrent.AbstractTracingAwareExecutorService$FutureTask.run(AbstractTracingAwareExecutorService.java:164)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105)
[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_222]
{code}
This [issue|https://github.com/dropwizard/metrics/issues/1278] has been
[fixed|https://github.com/dropwizard/metrics/pull/1436] in
[v4.0.6|https://github.com/dropwizard/metrics/releases/tag/v4.0.6].
This is observed on a 2.1.19 cluster, but this would impact pretty much any
version of C* since we depend on lower versions of metrics-core that do not
have the fix.
was:
Stacktrace
{code:java}
Uncaught exception on thread Thread[SharedPool-Worker-27,5,main]: {}
java.util.NoSuchElementException: null
at
java.util.concurrent.ConcurrentSkipListMap.firstKey(ConcurrentSkipListMap.java:2053)
~[na:1.8.0_222]
at
com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:102)
~[metrics-core-2.2.0.jar:na]
at
com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:81)
~[metrics-core-2.2.0.jar:na]
at com.yammer.metrics.core.Histogram.update(Histogram.java:110)
~[metrics-core-2.2.0.jar:na]
at com.yammer.metrics.core.Timer.update(Timer.java:198)
~[metrics-core-2.2.0.jar:na]
at com.yammer.metrics.core.Timer.update(Timer.java:76)
~[metrics-core-2.2.0.jar:na]
at
org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:108)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:114)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1897)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at org.apache.cassandra.db.Keyspace.getRow(Keyspace.java:353)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.db.SliceFromReadCommand.getRow(SliceFromReadCommand.java:85)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.db.ReadVerbHandler.doVerb(ReadVerbHandler.java:47)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:64)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
~[na:1.8.0_222]
at
org.apache.cassandra.concurrent.AbstractTracingAwareExecutorService$FutureTask.run(AbstractTracingAwareExecutorService.java:164)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105)
[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_222]
{code}
This
[jira] [Updated] (CASSANDRA-15472) Read failure due to exception from metrics-core dependency
[
https://issues.apache.org/jira/browse/CASSANDRA-15472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumanth Pasupuleti updated CASSANDRA-15472:
---
Description:
Stacktrace
{code:java}
Uncaught exception on thread Thread[SharedPool-Worker-27,5,main]: {}
java.util.NoSuchElementException: null
at
java.util.concurrent.ConcurrentSkipListMap.firstKey(ConcurrentSkipListMap.java:2053)
~[na:1.8.0_222]
at
com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:102)
~[metrics-core-2.2.0.jar:na]
at
com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:81)
~[metrics-core-2.2.0.jar:na]
at com.yammer.metrics.core.Histogram.update(Histogram.java:110)
~[metrics-core-2.2.0.jar:na]
at com.yammer.metrics.core.Timer.update(Timer.java:198)
~[metrics-core-2.2.0.jar:na]
at com.yammer.metrics.core.Timer.update(Timer.java:76)
~[metrics-core-2.2.0.jar:na]
at
org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:108)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:114)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1897)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at org.apache.cassandra.db.Keyspace.getRow(Keyspace.java:353)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.db.SliceFromReadCommand.getRow(SliceFromReadCommand.java:85)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.db.ReadVerbHandler.doVerb(ReadVerbHandler.java:47)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:64)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
~[na:1.8.0_222]
at
org.apache.cassandra.concurrent.AbstractTracingAwareExecutorService$FutureTask.run(AbstractTracingAwareExecutorService.java:164)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105)
[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_222]
{code}
This [issue|https://github.com/dropwizard/metrics/issues/1278] has been
[fixed|https://github.com/dropwizard/metrics/pull/1436] in
[v4.0.6|https://github.com/dropwizard/metrics/releases/tag/v4.0.6].
This is observed on a 2.1.19 cluster, but this would impact pretty much any
version of C* since we depend on a lower versions of metrics-core that do not
have the fix.
was:
Stacktrace
{code:java}
Uncaught exception on thread Thread[SharedPool-Worker-27,5,main]: {}
java.util.NoSuchElementException: null
at
java.util.concurrent.ConcurrentSkipListMap.firstKey(ConcurrentSkipListMap.java:2053)
~[na:1.8.0_222]
at
com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:102)
~[metrics-core-2.2.0.jar:na]
at
com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:81)
~[metrics-core-2.2.0.jar:na]
at com.yammer.metrics.core.Histogram.update(Histogram.java:110)
~[metrics-core-2.2.0.jar:na]
at com.yammer.metrics.core.Timer.update(Timer.java:198)
~[metrics-core-2.2.0.jar:na]
at com.yammer.metrics.core.Timer.update(Timer.java:76)
~[metrics-core-2.2.0.jar:na]
at
org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:108)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:114)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1897)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at org.apache.cassandra.db.Keyspace.getRow(Keyspace.java:353)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.db.SliceFromReadCommand.getRow(SliceFromReadCommand.java:85)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.db.ReadVerbHandler.doVerb(ReadVerbHandler.java:47)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:64)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
~[na:1.8.0_222]
at
org.apache.cassandra.concurrent.AbstractTracingAwareExecutorService$FutureTask.run(AbstractTracingAwareExecutorService.java:164)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105)
[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_222]
{code}
This
[jira] [Commented] (CASSANDRA-15472) Read failure due to exception from metrics-core dependency
[
https://issues.apache.org/jira/browse/CASSANDRA-15472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009174#comment-17009174
]
Sumanth Pasupuleti commented on CASSANDRA-15472:
I propose we upgrade the metrics dependency version to the one that has the fix
(or better yet latest). Will check if there are any compatibility issues with
the latest release.
> Read failure due to exception from metrics-core dependency
> --
>
> Key: CASSANDRA-15472
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15472
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Sumanth Pasupuleti
>Assignee: Sumanth Pasupuleti
>Priority: Normal
> Fix For: 4.0, 3.0.x, 3.11.x
>
>
> Stacktrace
> {code:java}
> Uncaught exception on thread Thread[SharedPool-Worker-27,5,main]: {}
> java.util.NoSuchElementException: null
> at
> java.util.concurrent.ConcurrentSkipListMap.firstKey(ConcurrentSkipListMap.java:2053)
> ~[na:1.8.0_222]
> at
> com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:102)
> ~[metrics-core-2.2.0.jar:na]
> at
> com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:81)
> ~[metrics-core-2.2.0.jar:na]
> at com.yammer.metrics.core.Histogram.update(Histogram.java:110)
> ~[metrics-core-2.2.0.jar:na]
> at com.yammer.metrics.core.Timer.update(Timer.java:198)
> ~[metrics-core-2.2.0.jar:na]
> at com.yammer.metrics.core.Timer.update(Timer.java:76)
> ~[metrics-core-2.2.0.jar:na]
> at
> org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:108)
> ~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
> at
> org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:114)
> ~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
> at
> org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1897)
> ~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
> at org.apache.cassandra.db.Keyspace.getRow(Keyspace.java:353)
> ~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
> at
> org.apache.cassandra.db.SliceFromReadCommand.getRow(SliceFromReadCommand.java:85)
> ~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
> at
> org.apache.cassandra.db.ReadVerbHandler.doVerb(ReadVerbHandler.java:47)
> ~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
> at
> org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:64)
> ~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> ~[na:1.8.0_222]
> at
> org.apache.cassandra.concurrent.AbstractTracingAwareExecutorService$FutureTask.run(AbstractTracingAwareExecutorService.java:164)
> ~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
> at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105)
> [nf-cassandra-2.1.19.10.jar:2.1.19.10]
> at java.lang.Thread.run(Thread.java:748) [na:1.8.0_222]
> {code}
> This [issue|https://github.com/dropwizard/metrics/issues/1278] has been
> [fixed|https://github.com/dropwizard/metrics/pull/1436] in
> [v4.0.6|https://github.com/dropwizard/metrics/releases/tag/v4.0.6].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15472) Read failure due to exception from metrics-core dependency
[
https://issues.apache.org/jira/browse/CASSANDRA-15472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumanth Pasupuleti updated CASSANDRA-15472:
---
Fix Version/s: 3.11.x
3.0.x
4.0
> Read failure due to exception from metrics-core dependency
> --
>
> Key: CASSANDRA-15472
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15472
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Sumanth Pasupuleti
>Assignee: Sumanth Pasupuleti
>Priority: Normal
> Fix For: 4.0, 3.0.x, 3.11.x
>
>
> Stacktrace
> {code:java}
> Uncaught exception on thread Thread[SharedPool-Worker-27,5,main]: {}
> java.util.NoSuchElementException: null
> at
> java.util.concurrent.ConcurrentSkipListMap.firstKey(ConcurrentSkipListMap.java:2053)
> ~[na:1.8.0_222]
> at
> com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:102)
> ~[metrics-core-2.2.0.jar:na]
> at
> com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:81)
> ~[metrics-core-2.2.0.jar:na]
> at com.yammer.metrics.core.Histogram.update(Histogram.java:110)
> ~[metrics-core-2.2.0.jar:na]
> at com.yammer.metrics.core.Timer.update(Timer.java:198)
> ~[metrics-core-2.2.0.jar:na]
> at com.yammer.metrics.core.Timer.update(Timer.java:76)
> ~[metrics-core-2.2.0.jar:na]
> at
> org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:108)
> ~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
> at
> org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:114)
> ~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
> at
> org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1897)
> ~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
> at org.apache.cassandra.db.Keyspace.getRow(Keyspace.java:353)
> ~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
> at
> org.apache.cassandra.db.SliceFromReadCommand.getRow(SliceFromReadCommand.java:85)
> ~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
> at
> org.apache.cassandra.db.ReadVerbHandler.doVerb(ReadVerbHandler.java:47)
> ~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
> at
> org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:64)
> ~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> ~[na:1.8.0_222]
> at
> org.apache.cassandra.concurrent.AbstractTracingAwareExecutorService$FutureTask.run(AbstractTracingAwareExecutorService.java:164)
> ~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
> at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105)
> [nf-cassandra-2.1.19.10.jar:2.1.19.10]
> at java.lang.Thread.run(Thread.java:748) [na:1.8.0_222]
> {code}
> This [issue|https://github.com/dropwizard/metrics/issues/1278] has been
> [fixed|https://github.com/dropwizard/metrics/pull/1436] in
> [v4.0.6|https://github.com/dropwizard/metrics/releases/tag/v4.0.6].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15472) Read failure due to exception from metrics-core dependency
[
https://issues.apache.org/jira/browse/CASSANDRA-15472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumanth Pasupuleti updated CASSANDRA-15472:
---
Description:
Stacktrace
{code:java}
Uncaught exception on thread Thread[SharedPool-Worker-27,5,main]: {}
java.util.NoSuchElementException: null
at
java.util.concurrent.ConcurrentSkipListMap.firstKey(ConcurrentSkipListMap.java:2053)
~[na:1.8.0_222]
at
com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:102)
~[metrics-core-2.2.0.jar:na]
at
com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:81)
~[metrics-core-2.2.0.jar:na]
at com.yammer.metrics.core.Histogram.update(Histogram.java:110)
~[metrics-core-2.2.0.jar:na]
at com.yammer.metrics.core.Timer.update(Timer.java:198)
~[metrics-core-2.2.0.jar:na]
at com.yammer.metrics.core.Timer.update(Timer.java:76)
~[metrics-core-2.2.0.jar:na]
at
org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:108)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:114)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1897)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at org.apache.cassandra.db.Keyspace.getRow(Keyspace.java:353)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.db.SliceFromReadCommand.getRow(SliceFromReadCommand.java:85)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.db.ReadVerbHandler.doVerb(ReadVerbHandler.java:47)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:64)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
~[na:1.8.0_222]
at
org.apache.cassandra.concurrent.AbstractTracingAwareExecutorService$FutureTask.run(AbstractTracingAwareExecutorService.java:164)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105)
[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_222]
{code}
This [issue|https://github.com/dropwizard/metrics/issues/1278] has been
[fixed|https://github.com/dropwizard/metrics/pull/1436] in
[v4.0.6|https://github.com/dropwizard/metrics/releases/tag/v4.0.6].
was:
Stacktrace
{code:java}
Uncaught exception on thread Thread[SharedPool-Worker-27,5,main]: {}
java.util.NoSuchElementException: null
at
java.util.concurrent.ConcurrentSkipListMap.firstKey(ConcurrentSkipListMap.java:2053)
~[na:1.8.0_222]
at
com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:102)
~[metrics-core-2.2.0.jar:na]
at
com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:81)
~[metrics-core-2.2.0.jar:na]
at com.yammer.metrics.core.Histogram.update(Histogram.java:110)
~[metrics-core-2.2.0.jar:na]
at com.yammer.metrics.core.Timer.update(Timer.java:198)
~[metrics-core-2.2.0.jar:na]
at com.yammer.metrics.core.Timer.update(Timer.java:76)
~[metrics-core-2.2.0.jar:na]
at
org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:108)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:114)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1897)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at org.apache.cassandra.db.Keyspace.getRow(Keyspace.java:353)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.db.SliceFromReadCommand.getRow(SliceFromReadCommand.java:85)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.db.ReadVerbHandler.doVerb(ReadVerbHandler.java:47)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:64)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
~[na:1.8.0_222]
at
org.apache.cassandra.concurrent.AbstractTracingAwareExecutorService$FutureTask.run(AbstractTracingAwareExecutorService.java:164)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105)
[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_222]
{code}
This [issue|https://github.com/dropwizard/metrics/issues/1278] has been
([fixed|https://github.com/dropwizard/metrics/pull/1436] in
[jira] [Created] (CASSANDRA-15472) Read failure due to exception from metrics-core dependency
Sumanth Pasupuleti created CASSANDRA-15472:
--
Summary: Read failure due to exception from metrics-core dependency
Key: CASSANDRA-15472
URL: https://issues.apache.org/jira/browse/CASSANDRA-15472
Project: Cassandra
Issue Type: Bug
Components: Dependencies
Reporter: Sumanth Pasupuleti
Assignee: Sumanth Pasupuleti
Stacktrace
{code:java}
Uncaught exception on thread Thread[SharedPool-Worker-27,5,main]: {}
java.util.NoSuchElementException: null
at
java.util.concurrent.ConcurrentSkipListMap.firstKey(ConcurrentSkipListMap.java:2053)
~[na:1.8.0_222]
at
com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:102)
~[metrics-core-2.2.0.jar:na]
at
com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:81)
~[metrics-core-2.2.0.jar:na]
at com.yammer.metrics.core.Histogram.update(Histogram.java:110)
~[metrics-core-2.2.0.jar:na]
at com.yammer.metrics.core.Timer.update(Timer.java:198)
~[metrics-core-2.2.0.jar:na]
at com.yammer.metrics.core.Timer.update(Timer.java:76)
~[metrics-core-2.2.0.jar:na]
at
org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:108)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:114)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1897)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at org.apache.cassandra.db.Keyspace.getRow(Keyspace.java:353)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.db.SliceFromReadCommand.getRow(SliceFromReadCommand.java:85)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.db.ReadVerbHandler.doVerb(ReadVerbHandler.java:47)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:64)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
~[na:1.8.0_222]
at
org.apache.cassandra.concurrent.AbstractTracingAwareExecutorService$FutureTask.run(AbstractTracingAwareExecutorService.java:164)
~[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105)
[nf-cassandra-2.1.19.10.jar:2.1.19.10]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_222]
{code}
This [issue|https://github.com/dropwizard/metrics/issues/1278] has been
([fixed|https://github.com/dropwizard/metrics/pull/1436] in
[v4.0.6|https://github.com/dropwizard/metrics/releases/tag/v4.0.6]).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15428) First of the new features - Support for Java 11
[ https://issues.apache.org/jira/browse/CASSANDRA-15428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Joshi updated CASSANDRA-15428: - Authors: (was: Dinesh Joshi) > First of the new features - Support for Java 11 > --- > > Key: CASSANDRA-15428 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15428 > Project: Cassandra > Issue Type: Sub-task > Components: Legacy/Documentation and Website >Reporter: DeepakVohra >Assignee: Dinesh Joshi >Priority: Normal > > A pull request for first of the new features in 4.0. > - As 4.0 is a major release created a new folder called "new" > - Added a _index.rst_ to the _new_ folder > - Added _new/index_ to the top-level _index.rst_ > - Added _java11.rst_ to the _new_ folder for the new feature _Support for > Java 11_ > https://github.com/apache/cassandra/pull/383 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15428) First of the new features - Support for Java 11
[ https://issues.apache.org/jira/browse/CASSANDRA-15428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Joshi updated CASSANDRA-15428: - Change Category: Code Clarity Complexity: Low Hanging Fruit Reviewers: Dinesh Joshi Status: Open (was: Triage Needed) > First of the new features - Support for Java 11 > --- > > Key: CASSANDRA-15428 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15428 > Project: Cassandra > Issue Type: Sub-task > Components: Legacy/Documentation and Website >Reporter: DeepakVohra >Assignee: Dinesh Joshi >Priority: Normal > > A pull request for first of the new features in 4.0. > - As 4.0 is a major release created a new folder called "new" > - Added a _index.rst_ to the _new_ folder > - Added _new/index_ to the top-level _index.rst_ > - Added _java11.rst_ to the _new_ folder for the new feature _Support for > Java 11_ > https://github.com/apache/cassandra/pull/383 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15353) Documentation Preview - Cassandra 4.0
[ https://issues.apache.org/jira/browse/CASSANDRA-15353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Joshi updated CASSANDRA-15353: - Authors: (was: Deepak Vohra) > Documentation Preview - Cassandra 4.0 > - > > Key: CASSANDRA-15353 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15353 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: DeepakVohra >Assignee: Deepak Vohra >Priority: Normal > > Please review, and add comments to, some of the documentation preview for > Apache Cassandra 4.0. > New Features > --- > *Audit Logging* > https://docs.google.com/document/d/1WsQYjDQ9UZ7f8P3eAATht6Vz5oNibTmhsH8cu9viLTk/edit?usp=sharing > *Full Query Logging* > https://docs.google.com/document/d/1ZNfs68ZNJXqDc_2XGM6W-tpvnejUfSh8HmkbG8u35Es/edit?usp=sharing > *Support for Java 11* > https://docs.google.com/document/d/1v7ffccqk_5Son4iwfuwZae8YUam41quewKi_6Z_PQGw/edit?usp=sharing > *Transient Replication and Cheap Quorums* > https://docs.google.com/document/d/1GyJVCmwoMb7OO9NkbGdk26YxHi9fWtfzuTBTiIEpli8/edit?usp=sharing > *Virtual Tables* > https://docs.google.com/document/d/1U8qAzQnA2HcoIzTg5IXFUySUZXD1tEIl2bam-514we8/edit?usp=sharing > Improvements > > *Improved Streaming* > https://docs.google.com/document/d/1zd6AuHBgC82v598cuDtVIkxJVDV9c0A2rrMEVFHyB4Y/edit?usp=sharing > *Improved Internode Messaging* > https://docs.google.com/document/d/1ub2DBHE7hNEKe4tuCOpdbCZ7qGqCdMAYvSTC-YamuMA/edit?usp=sharing -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15353) Documentation Preview - Cassandra 4.0
[ https://issues.apache.org/jira/browse/CASSANDRA-15353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Joshi updated CASSANDRA-15353: - Reviewers: Dinesh Joshi > Documentation Preview - Cassandra 4.0 > - > > Key: CASSANDRA-15353 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15353 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: DeepakVohra >Assignee: Deepak Vohra >Priority: Normal > > Please review, and add comments to, some of the documentation preview for > Apache Cassandra 4.0. > New Features > --- > *Audit Logging* > https://docs.google.com/document/d/1WsQYjDQ9UZ7f8P3eAATht6Vz5oNibTmhsH8cu9viLTk/edit?usp=sharing > *Full Query Logging* > https://docs.google.com/document/d/1ZNfs68ZNJXqDc_2XGM6W-tpvnejUfSh8HmkbG8u35Es/edit?usp=sharing > *Support for Java 11* > https://docs.google.com/document/d/1v7ffccqk_5Son4iwfuwZae8YUam41quewKi_6Z_PQGw/edit?usp=sharing > *Transient Replication and Cheap Quorums* > https://docs.google.com/document/d/1GyJVCmwoMb7OO9NkbGdk26YxHi9fWtfzuTBTiIEpli8/edit?usp=sharing > *Virtual Tables* > https://docs.google.com/document/d/1U8qAzQnA2HcoIzTg5IXFUySUZXD1tEIl2bam-514we8/edit?usp=sharing > Improvements > > *Improved Streaming* > https://docs.google.com/document/d/1zd6AuHBgC82v598cuDtVIkxJVDV9c0A2rrMEVFHyB4Y/edit?usp=sharing > *Improved Internode Messaging* > https://docs.google.com/document/d/1ub2DBHE7hNEKe4tuCOpdbCZ7qGqCdMAYvSTC-YamuMA/edit?usp=sharing -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-15353) Documentation Preview - Cassandra 4.0
[ https://issues.apache.org/jira/browse/CASSANDRA-15353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Joshi reassigned CASSANDRA-15353: Assignee: Deepak Vohra (was: Dinesh Joshi) > Documentation Preview - Cassandra 4.0 > - > > Key: CASSANDRA-15353 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15353 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: DeepakVohra >Assignee: Deepak Vohra >Priority: Normal > > Please review, and add comments to, some of the documentation preview for > Apache Cassandra 4.0. > New Features > --- > *Audit Logging* > https://docs.google.com/document/d/1WsQYjDQ9UZ7f8P3eAATht6Vz5oNibTmhsH8cu9viLTk/edit?usp=sharing > *Full Query Logging* > https://docs.google.com/document/d/1ZNfs68ZNJXqDc_2XGM6W-tpvnejUfSh8HmkbG8u35Es/edit?usp=sharing > *Support for Java 11* > https://docs.google.com/document/d/1v7ffccqk_5Son4iwfuwZae8YUam41quewKi_6Z_PQGw/edit?usp=sharing > *Transient Replication and Cheap Quorums* > https://docs.google.com/document/d/1GyJVCmwoMb7OO9NkbGdk26YxHi9fWtfzuTBTiIEpli8/edit?usp=sharing > *Virtual Tables* > https://docs.google.com/document/d/1U8qAzQnA2HcoIzTg5IXFUySUZXD1tEIl2bam-514we8/edit?usp=sharing > Improvements > > *Improved Streaming* > https://docs.google.com/document/d/1zd6AuHBgC82v598cuDtVIkxJVDV9c0A2rrMEVFHyB4Y/edit?usp=sharing > *Improved Internode Messaging* > https://docs.google.com/document/d/1ub2DBHE7hNEKe4tuCOpdbCZ7qGqCdMAYvSTC-YamuMA/edit?usp=sharing -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-13938) Default repair is broken, crashes other nodes participating in repair (in trunk)
[
https://issues.apache.org/jira/browse/CASSANDRA-13938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Joshi updated CASSANDRA-13938:
-
Reviewers: Dinesh Joshi, Dinesh Joshi (was: Dinesh Joshi)
Dinesh Joshi, Dinesh Joshi (was: Dinesh Joshi)
Status: Review In Progress (was: Patch Available)
> Default repair is broken, crashes other nodes participating in repair (in
> trunk)
>
>
> Key: CASSANDRA-13938
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13938
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair
>Reporter: Nate McCall
>Assignee: Aleksey Yeschenko
>Priority: Urgent
> Fix For: 4.0-alpha
>
> Attachments: 13938.yaml, test.sh
>
>
> Running through a simple scenario to test some of the new repair features, I
> was not able to make a repair command work. Further, the exception seemed to
> trigger a nasty failure state that basically shuts down the netty connections
> for messaging *and* CQL on the nodes transferring back data to the node being
> repaired. The following steps reproduce this issue consistently.
> Cassandra stress profile (probably not necessary, but this one provides a
> really simple schema and consistent data shape):
> {noformat}
> keyspace: standard_long
> keyspace_definition: |
> CREATE KEYSPACE standard_long WITH replication = {'class':'SimpleStrategy',
> 'replication_factor':3};
> table: test_data
> table_definition: |
> CREATE TABLE test_data (
> key text,
> ts bigint,
> val text,
> PRIMARY KEY (key, ts)
> ) WITH COMPACT STORAGE AND
> CLUSTERING ORDER BY (ts DESC) AND
> bloom_filter_fp_chance=0.01 AND
> caching={'keys':'ALL', 'rows_per_partition':'NONE'} AND
> comment='' AND
> dclocal_read_repair_chance=0.00 AND
> gc_grace_seconds=864000 AND
> read_repair_chance=0.00 AND
> compaction={'class': 'SizeTieredCompactionStrategy'} AND
> compression={'sstable_compression': 'LZ4Compressor'};
> columnspec:
> - name: key
> population: uniform(1..5000) # 50 million records available
> - name: ts
> cluster: gaussian(1..50) # Up to 50 inserts per record
> - name: val
> population: gaussian(128..1024) # varrying size of value data
> insert:
> partitions: fixed(1) # only one insert per batch for individual partitions
> select: fixed(1)/1 # each insert comes in one at a time
> batchtype: UNLOGGED
> queries:
> single:
> cql: select * from test_data where key = ? and ts = ? limit 1;
> series:
> cql: select key,ts,val from test_data where key = ? limit 10;
> {noformat}
> The commands to build and run:
> {noformat}
> ccm create 4_0_test -v git:trunk -n 3 -s
> ccm stress user profile=./histo-test-schema.yml
> ops\(insert=20,single=1,series=1\) duration=15s -rate threads=4
> # flush the memtable just to get everything on disk
> ccm node1 nodetool flush
> ccm node2 nodetool flush
> ccm node3 nodetool flush
> # disable hints for nodes 2 and 3
> ccm node2 nodetool disablehandoff
> ccm node3 nodetool disablehandoff
> # stop node1
> ccm node1 stop
> ccm stress user profile=./histo-test-schema.yml
> ops\(insert=20,single=1,series=1\) duration=45s -rate threads=4
> # wait 10 seconds
> ccm node1 start
> # Note that we are local to ccm's nodetool install 'cause repair preview is
> not reported yet
> node1/bin/nodetool repair --preview
> node1/bin/nodetool repair standard_long test_data
> {noformat}
> The error outputs from the last repair command follow. First, this is stdout
> from node1:
> {noformat}
> $ node1/bin/nodetool repair standard_long test_data
> objc[47876]: Class JavaLaunchHelper is implemented in both
> /Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/bin/java
> (0x10274d4c0) and
> /Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/lib/libinstrument.dylib
> (0x1047b64e0). One of the two will be used. Which one is undefined.
> [2017-10-05 14:31:52,425] Starting repair command #4
> (7e1a9150-a98e-11e7-ad86-cbd2801b8de2), repairing keyspace standard_long with
> repair options (parallelism: parallel, primary range: false, incremental:
> true, job threads: 1, ColumnFamilies: [test_data], dataCenters: [], hosts:
> [], previewKind: NONE, # of ranges: 3, pull repair: false, force repair:
> false)
> [2017-10-05 14:32:07,045] Repair session 7e2e8e80-a98e-11e7-ad86-cbd2801b8de2
> for range [(3074457345618258602,-9223372036854775808],
> (-9223372036854775808,-3074457345618258603],
> (-3074457345618258603,3074457345618258602]] failed with error Stream failed
> [2017-10-05 14:32:07,048] null
> [2017-10-05 14:32:07,050] Repair command #4 finished in 14 seconds
> error: Repair job has failed with the error message: [2017-10-05
> 14:32:07,048] null
>
[jira] [Updated] (CASSANDRA-15469) IndexInfo/ColumnIndex Refactors & Cleanup
[ https://issues.apache.org/jira/browse/CASSANDRA-15469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Joshi updated CASSANDRA-15469: - Reviewers: Dinesh Joshi, Dinesh Joshi (was: Dinesh Joshi) Dinesh Joshi, Dinesh Joshi Status: Review In Progress (was: Patch Available) > IndexInfo/ColumnIndex Refactors & Cleanup > - > > Key: CASSANDRA-15469 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15469 > Project: Cassandra > Issue Type: Improvement > Components: Local/SSTable >Reporter: Jordan West >Assignee: Jordan West >Priority: Normal > Fix For: 4.0-beta > > > Changes determined by audit of IndexInfo and ColumnIndex changes for > Cassandra 4.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15401) nodetool stop help is missing "ANTICOMPACTION"
[
https://issues.apache.org/jira/browse/CASSANDRA-15401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17008928#comment-17008928
]
Ekaterina Dimitrova commented on CASSANDRA-15401:
-
[~marcuse] I hope there is nothing else I am missing here? Thanks for your help!
> nodetool stop help is missing "ANTICOMPACTION"
> --
>
> Key: CASSANDRA-15401
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15401
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
>
> The {{nodetool stop}} command can be used to stop certain activities
> including anti-compaction. While we can run {{nodetool stop ANTICOMPACTION}}
> on a given node the help menu does not list it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15469) IndexInfo/ColumnIndex Refactors & Cleanup
[ https://issues.apache.org/jira/browse/CASSANDRA-15469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan West updated CASSANDRA-15469: Test and Documentation Plan: Relies on existing tests since this is a refactor & cleanup Status: Patch Available (was: Open) [branch|https://github.com/jrwest/cassandra/tree/jwest/15469] [test|https://circleci.com/gh/jrwest/cassandra/tree/jwest%2F15469] > IndexInfo/ColumnIndex Refactors & Cleanup > - > > Key: CASSANDRA-15469 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15469 > Project: Cassandra > Issue Type: Improvement > Components: Local/SSTable >Reporter: Jordan West >Assignee: Jordan West >Priority: Normal > Fix For: 4.0-beta > > > Changes determined by audit of IndexInfo and ColumnIndex changes for > Cassandra 4.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15471) Run Jenkins Cqlsh Tests using the in-tree cassandra-cqlsh-tests.sh
[ https://issues.apache.org/jira/browse/CASSANDRA-15471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-15471: --- Test and Documentation Plan: Jenkins DSL build Status: Patch Available (was: Open) > Run Jenkins Cqlsh Tests using the in-tree cassandra-cqlsh-tests.sh > -- > > Key: CASSANDRA-15471 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15471 > Project: Cassandra > Issue Type: Task > Components: Test/dtest >Reporter: Michael Semb Wever >Priority: Normal > > Make the Jenkins Cqlsh test job to use the in-tree cassandra-cqlsh-tests.sh > instead of the same script from the cassandra-builds repo. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15471) Run Jenkins Cqlsh Tests using the in-tree cassandra-cqlsh-tests.sh
[ https://issues.apache.org/jira/browse/CASSANDRA-15471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-15471: --- Change Category: Quality Assurance Complexity: Low Hanging Fruit Status: Open (was: Triage Needed) > Run Jenkins Cqlsh Tests using the in-tree cassandra-cqlsh-tests.sh > -- > > Key: CASSANDRA-15471 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15471 > Project: Cassandra > Issue Type: Task > Components: Test/dtest >Reporter: Michael Semb Wever >Priority: Normal > > Make the Jenkins Cqlsh test job to use the in-tree cassandra-cqlsh-tests.sh > instead of the same script from the cassandra-builds repo. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15470) Potential Overflow in DatabaseDescriptor Functions That Convert Between KB/MB & Bytes
[
https://issues.apache.org/jira/browse/CASSANDRA-15470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jordan West updated CASSANDRA-15470:
Bug Category: Parent values: Code(13163)Level 1 values: Bug - Unclear
Impact(13164)
Complexity: Low Hanging Fruit
Discovered By: Code Inspection
Fix Version/s: 4.0-rc
Severity: Low
Status: Open (was: Triage Needed)
> Potential Overflow in DatabaseDescriptor Functions That Convert Between KB/MB
> & Bytes
> -
>
> Key: CASSANDRA-15470
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15470
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Config
>Reporter: Jordan West
>Priority: Normal
> Fix For: 4.0-rc
>
>
> {{DatabaseDescriptor}} has several functions that convert between user
> supplied sizes in KB/MB and bytes. These are implemented without much
> consistency and, while unlikely, several have the potential to overflow since
> validation on the input is missing. Meanwhile, some widen the number to a
> long correctly. Options include: widening in all places or simply doing
> better validation on start up — currently only the lower bound of the valid
> range is checked for many of these fields.
> List of Affected {{DatabaseDescriptor}} Methods:
> * {{getColumnIndexSize}}
> * {{getColumnIndexCacheSize}}
> * {{getBatchSizeWarnThreshold}}
> * {{getNativeTransportFrameBlockSize}}
> * {{getRepairSessionSpaceInMegabytes}}
> * {{getNativeTransportMaxFrameSize}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15471) Run Jenkins Cqlsh Tests using the in-tree cassandra-cqlsh-tests.sh
[ https://issues.apache.org/jira/browse/CASSANDRA-15471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17008791#comment-17008791 ] Michael Semb Wever commented on CASSANDRA-15471: Patch at https://github.com/apache/cassandra-builds/commit/89d5a727314d71f7c372aebdc4449832f73a26e4 On my local jenkins installation this fixes the cqlsh tests. The pgrep command is also fixed (bc job name here contains spaces). Note it removes the cqlsh tests against Cassandra-2.2, as 14951 was only committed to 3.0 onwards. > Run Jenkins Cqlsh Tests using the in-tree cassandra-cqlsh-tests.sh > -- > > Key: CASSANDRA-15471 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15471 > Project: Cassandra > Issue Type: Task > Components: Test/dtest >Reporter: Michael Semb Wever >Priority: Normal > > Make the Jenkins Cqlsh test job to use the in-tree cassandra-cqlsh-tests.sh > instead of the same script from the cassandra-builds repo. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15469) IndexInfo/ColumnIndex Refactors & Cleanup
[ https://issues.apache.org/jira/browse/CASSANDRA-15469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan West updated CASSANDRA-15469: Change Category: Code Clarity Complexity: Low Hanging Fruit Fix Version/s: 4.0-beta Status: Open (was: Triage Needed) > IndexInfo/ColumnIndex Refactors & Cleanup > - > > Key: CASSANDRA-15469 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15469 > Project: Cassandra > Issue Type: Improvement > Components: Local/SSTable >Reporter: Jordan West >Assignee: Jordan West >Priority: Normal > Fix For: 4.0-beta > > > Changes determined by audit of IndexInfo and ColumnIndex changes for > Cassandra 4.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15471) Run Jenkins Cqlsh Tests using the in-tree cassandra-cqlsh-tests.sh
Michael Semb Wever created CASSANDRA-15471: -- Summary: Run Jenkins Cqlsh Tests using the in-tree cassandra-cqlsh-tests.sh Key: CASSANDRA-15471 URL: https://issues.apache.org/jira/browse/CASSANDRA-15471 Project: Cassandra Issue Type: Task Components: Test/dtest Reporter: Michael Semb Wever Make the Jenkins Cqlsh test job to use the in-tree cassandra-cqlsh-tests.sh instead of the same script from the cassandra-builds repo. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15470) Potential Overflow in DatabaseDescriptor Functions That Convert Between KB/MB & Bytes
Jordan West created CASSANDRA-15470:
---
Summary: Potential Overflow in DatabaseDescriptor Functions That
Convert Between KB/MB & Bytes
Key: CASSANDRA-15470
URL: https://issues.apache.org/jira/browse/CASSANDRA-15470
Project: Cassandra
Issue Type: Bug
Components: Local/Config
Reporter: Jordan West
{{DatabaseDescriptor}} has several functions that convert between user supplied
sizes in KB/MB and bytes. These are implemented without much consistency and,
while unlikely, several have the potential to overflow since validation on the
input is missing. Meanwhile, some widen the number to a long correctly. Options
include: widening in all places or simply doing better validation on start up —
currently only the lower bound of the valid range is checked for many of these
fields.
List of Affected {{DatabaseDescriptor}} Methods:
* {{getColumnIndexSize}}
* {{getColumnIndexCacheSize}}
* {{getBatchSizeWarnThreshold}}
* {{getNativeTransportFrameBlockSize}}
* {{getRepairSessionSpaceInMegabytes}}
* {{getNativeTransportMaxFrameSize}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15469) IndexInfo/ColumnIndex Refactors & Cleanup
Jordan West created CASSANDRA-15469: --- Summary: IndexInfo/ColumnIndex Refactors & Cleanup Key: CASSANDRA-15469 URL: https://issues.apache.org/jira/browse/CASSANDRA-15469 Project: Cassandra Issue Type: Improvement Components: Local/SSTable Reporter: Jordan West Assignee: Jordan West Changes determined by audit of IndexInfo and ColumnIndex changes for Cassandra 4.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15468) Unable to start embedded cassandra on JDK 11
[
https://issues.apache.org/jira/browse/CASSANDRA-15468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-15468:
Resolution: Not A Problem
Status: Resolved (was: Triage Needed)
As you've seen from CASSANDRA-9608, these options are required due to the use
of internal jdk classes and compounded by the cross compilation requirement
while we maintain support for java 8. I very much doubt that neither these
requirements nor support for {{--add-exports}} in the jdk are going to be
removed any time soon. So you're right that this is a somewhat temporary
solution, but it will be addressed when it becomes necessary to do so.
Regarding the log message, I'm not sure I agree that the messaging is ambiguous
here given that the message is logged at {{ERROR}} level and prefixed
{{FATAL}}. To me, that indicates pretty clearly that a failure is imminent.
> Unable to start embedded cassandra on JDK 11
>
>
> Key: CASSANDRA-15468
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15468
> Project: Cassandra
> Issue Type: Bug
>Reporter: Gus Heck
>Priority: Normal
>
> Cassandra fails to start without the following jvm options from
> jvm-11-server.options:
> {code:java}
> -Djdk.attach.allowAttachSelf=true
> --add-exports java.base/jdk.internal.misc=ALL-UNNAMED
> --add-exports java.base/jdk.internal.ref=ALL-UNNAMED
> --add-exports java.base/sun.nio.ch=ALL-UNNAMED
> --add-exports java.management.rmi/com.sun.jmx.remote.internal.rmi=ALL-UNNAMED
> --add-exports java.rmi/sun.rmi.registry=ALL-UNNAMED
> --add-exports java.rmi/sun.rmi.server=ALL-UNNAMED
> --add-exports java.sql/java.sql=ALL-UNNAMED
> --add-opens java.base/java.lang.module=ALL-UNNAMED
> --add-opens java.base/jdk.internal.loader=ALL-UNNAMED
> --add-opens java.base/jdk.internal.ref=ALL-UNNAMED
> --add-opens java.base/jdk.internal.reflect=ALL-UNNAMED
> --add-opens java.base/jdk.internal.math=ALL-UNNAMED
> --add-opens java.base/jdk.internal.module=ALL-UNNAMED
> --add-opens java.base/jdk.internal.util.jar=ALL-UNNAMED
> --add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED
> {code}
> Without these options the following stack trace appears and prevents startup
> {code:java}
> 2020-01-05T17:42:15,009 ERROR main
> org.apache.cassandra.service.CassandraDaemon Exception encountered during
> startup java.lang.ExceptionInInitializerError
> at
> org.apache.cassandra.config.DatabaseDescriptor.guessFileStore(DatabaseDescriptor.java:1127)
> at
> org.apache.cassandra.config.DatabaseDescriptor.applySimpleConfig(DatabaseDescriptor.java:541)
> at
> org.apache.cassandra.config.DatabaseDescriptor.applyAll(DatabaseDescriptor.java:340)
> at
> org.apache.cassandra.config.DatabaseDescriptor.daemonInitialization(DatabaseDescriptor.java:168)
> at
> org.apache.cassandra.config.DatabaseDescriptor.daemonInitialization(DatabaseDescriptor.java:152)
> at
> org.apache.cassandra.service.CassandraDaemon.applyConfig(CassandraDaemon.java:665)
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:609)
> at org.jesterj.ingest.persistence.Cassandra.start(Cassandra.java:135)
> at
> org.jesterj.ingest.scanners.SimpleFileScannerImplFTITest.testScanWithMemory(SimpleFileScannerImplFTITest.java:63)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
> at
[jira] [Updated] (CASSANDRA-15467) Add missing jenkins executor requirements to CI documentation
[ https://issues.apache.org/jira/browse/CASSANDRA-15467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-15467: --- Fix Version/s: 4.0-alpha Source Control Link: https://github.com/apache/cassandra/commit/bf54f753a0466375e9be5f44873f97161e00fe38 Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed as bf54f753a0466375e9be5f44873f97161e00fe38 > Add missing jenkins executor requirements to CI documentation > - > > Key: CASSANDRA-15467 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15467 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Website >Reporter: Michael Semb Wever >Priority: Low > Fix For: 4.0-alpha > > > The following provides information on how to set up Jenkins CI to test > Cassandra the same as the ASF Jenkins does: > http://cassandra.apache.org/doc/latest/development/ci.html > The setup is remarkably easy, thanks [~spod]. > The only hurdle I hit was the JDK and virtualenv needs to be installed on the > executors. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated: Update CI docs to mention JDK and virtualenv needs to be installed on the executors.
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.git The following commit(s) were added to refs/heads/trunk by this push: new bf54f75 Update CI docs to mention JDK and virtualenv needs to be installed on the executors. bf54f75 is described below commit bf54f753a0466375e9be5f44873f97161e00fe38 Author: Mick Semb Wever AuthorDate: Fri Jan 3 21:31:04 2020 +0100 Update CI docs to mention JDK and virtualenv needs to be installed on the executors. patch by Mick Semb Wever; reviewed by Stefan Podkowinski for CASSANDRA-15467 --- doc/source/development/ci.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/development/ci.rst b/doc/source/development/ci.rst index 192b188..77360ae 100644 --- a/doc/source/development/ci.rst +++ b/doc/source/development/ci.rst @@ -68,5 +68,5 @@ You should now find a new entry with the given name in your project list. Howeve Jobs are triggered by either changes in Git or are scheduled to execute periodically, e.g. on daily basis. Jenkins will use any available executor with the label "cassandra", once the job is to be run. Please make sure to make any executors available by selecting ``Build Executor Status`` -> ``Configure`` -> Add "``cassandra``" as label and save. - +Executors need to have "JDK 1.8 (latest)" installed. This is done under ``Manage Jenkins -> Global Tool Configuration -> JDK Installations…``. Executors also need to have the virtualenv package installed on their system. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14781) Log message when mutation passed to CommitLog#add(Mutation) is too large is not descriptive enough
[
https://issues.apache.org/jira/browse/CASSANDRA-14781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17008622#comment-17008622
]
Venkata Harikrishna Nukala commented on CASSANDRA-14781:
[~jrwest] Made a patch with the changes. [~tpetracca] apologies if I am
overtaking you.
Here is the
[patch|https://github.com/nvharikrishna/cassandra/commit/5b3af390ce64860505dfeb3a3549cc9897987771]
and [CI|https://app.circleci.com/jobs/github/nvharikrishna/cassandra/95].
I have a small question though. In
[CommitLog.java|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/commitlog/CommitLog.java#L274],
it considers commit log entry overhead with mutation size to compare with max
mutation size. Shouldn't it consider only the mutation size? I made changes to
be compatible with overhead (I can change based on your comments).
{{SizeHolder}} introduced in this patch can be used in {{Message}} as well. I
can make this change too if it is okay to mixup.
> Log message when mutation passed to CommitLog#add(Mutation) is too large is
> not descriptive enough
> --
>
> Key: CASSANDRA-14781
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14781
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Hints, Local/Commit Log, Messaging/Client
>Reporter: Jordan West
>Assignee: Tom Petracca
>Priority: Normal
> Labels: protocolv5
> Fix For: 4.0-beta
>
> Attachments: CASSANDRA-14781.patch, CASSANDRA-14781_3.0.patch,
> CASSANDRA-14781_3.11.patch
>
>
> When hitting
> [https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/db/commitlog/CommitLog.java#L256-L257],
> the log message produced does not help the operator track down what data is
> being written. At a minimum the keyspace and cfIds involved would be useful
> (and are available) – more detail might not be reasonable to include.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
