[jira] [Updated] (CASSANDRA-19746) Update CQLSH documentation to remove Python 2.7 reference
[ https://issues.apache.org/jira/browse/CASSANDRA-19746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19746: --- Change Category: Code Clarity Complexity: Low Hanging Fruit Status: Open (was: Triage Needed) > Update CQLSH documentation to remove Python 2.7 reference > - > > Key: CASSANDRA-19746 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19746 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Low > > The CQLSH > [Compatibility|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] > section mentions Python 2.7 but this should be Python 3.x now. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19746) Update CQLSH website documentation to remove Python 2.7 reference
[ https://issues.apache.org/jira/browse/CASSANDRA-19746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19746: --- Summary: Update CQLSH website documentation to remove Python 2.7 reference (was: Update CQLSH documentation to remove Python 2.7 reference) > Update CQLSH website documentation to remove Python 2.7 reference > - > > Key: CASSANDRA-19746 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19746 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Low > > The CQLSH > [Compatibility|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] > section mentions Python 2.7 but this should be Python 3.x now. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-19746) Update CQLSH documentation to remove Python 2.7 reference
[ https://issues.apache.org/jira/browse/CASSANDRA-19746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening reassigned CASSANDRA-19746: -- Assignee: Brad Schoening > Update CQLSH documentation to remove Python 2.7 reference > - > > Key: CASSANDRA-19746 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19746 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Low > > The CQLSH > [Compatibility|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] > section mentions Python 2.7 but this should be Python 3.x now. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19746) Update CQLSH documentation to remove Python 2.7 reference
[ https://issues.apache.org/jira/browse/CASSANDRA-19746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19746: --- Priority: Low (was: Normal) > Update CQLSH documentation to remove Python 2.7 reference > - > > Key: CASSANDRA-19746 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19746 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: Brad Schoening >Priority: Low > > The CQLSH > [Compatibility|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] > section mentions Python 2.7 but this should be Python 3.x now. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19746) Update CQLSH documentation to remove Python 2.7 reference
[ https://issues.apache.org/jira/browse/CASSANDRA-19746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19746: --- Impacts: Docs (was: None) > Update CQLSH documentation to remove Python 2.7 reference > - > > Key: CASSANDRA-19746 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19746 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: Brad Schoening >Priority: Low > > The CQLSH > [Compatibility|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] > section mentions Python 2.7 but this should be Python 3.x now. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19746) Update CQLSH documentation to remove Python 2.7 reference
Brad Schoening created CASSANDRA-19746: -- Summary: Update CQLSH documentation to remove Python 2.7 reference Key: CASSANDRA-19746 URL: https://issues.apache.org/jira/browse/CASSANDRA-19746 Project: Cassandra Issue Type: Task Components: Documentation Reporter: Brad Schoening The CQLSH [Compatibility|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] section mentions Python 2.7 but this should be Python 3.x now. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19665) Add download link for Java drivers from download page
[ https://issues.apache.org/jira/browse/CASSANDRA-19665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-19665: --- Labels: pull-request-available (was: ) > Add download link for Java drivers from download page > - > > Key: CASSANDRA-19665 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19665 > Project: Cassandra > Issue Type: Task > Components: Client/java-driver, Documentation/Website >Reporter: Bret McGuire >Assignee: Brad Schoening >Priority: Normal > Labels: pull-request-available > > Seems like we should have a link to download Java drivers from the [download > page|https://cassandra.apache.org/_/download.html] on the Website -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19665) Add download link for Java drivers from download page
[ https://issues.apache.org/jira/browse/CASSANDRA-19665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19665: --- Test and Documentation Plan: Text only change, ran 'website build' (was: Doc only change, ran 'website build') > Add download link for Java drivers from download page > - > > Key: CASSANDRA-19665 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19665 > Project: Cassandra > Issue Type: Task > Components: Client/java-driver, Documentation/Website >Reporter: Bret McGuire >Assignee: Brad Schoening >Priority: Normal > > Seems like we should have a link to download Java drivers from the [download > page|https://cassandra.apache.org/_/download.html] on the Website -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17445) Library airlift/airline has been deprecated
[ https://issues.apache.org/jira/browse/CASSANDRA-17445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Rackliffe updated CASSANDRA-17445: Reviewers: Caleb Rackliffe > Library airlift/airline has been deprecated > --- > > Key: CASSANDRA-17445 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17445 > Project: Cassandra > Issue Type: Task > Components: Dependencies >Reporter: Tibor Repasi >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.x > > Time Spent: 10m > Remaining Estimate: 0h > > The [airlift/airline|https://github.com/airlift/airline] library has been > deprecated and is not maintained since [8 Jun > 2021|https://github.com/airlift/airline/commit/ae3d7e103bdc140969bde944d4ba09345d663a61]. > It is used in many tools and some tests of Cassandra which should be > reviewed. > Tools using that library: > * org.apache.cassandra.tools.JMXTool > * org.apache.cassandra.tools.NodeTool > * org.apache.cassandra.stress.Compaction > * org.apache.cassandra.fqltool.FullQueryLogTool > Tests using it: > * org.apache.cassandra.simulator.SimulationRunner > Alternatives (as suggested in the depreciation notice): > * [Airline 2|https://rvesse.github.io/airline/] > * [picocli|https://picocli.info] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-13428) Security: provide keystore_password_file and truststore_password_file options
[
https://issues.apache.org/jira/browse/CASSANDRA-13428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862600#comment-17862600
]
Maulin Vasavada edited comment on CASSANDRA-13428 at 7/2/24 9:31 PM:
-
Can this be addressed with a similar approach mentioned in
https://issues.apache.org/jira/browse/CASSANDRA-18508 ? I think having a
pluggable credentials provider (parameterized class) make sense to provide a
unified solution to multiple passwords/credentials we have today in config
files. This will help in either fetching the credentials from a file, env
variables (e.g. K8s env vars) etc vs just files.
However by 'unified' I don't mean a 'single class'. Just a single interface and
a mechanism and have ability to write providers if needed. We must also provide
implementation to address the tickets in the concern as well.
was (Author: maulin.vasavada):
Can this be addressed with a similar approach mentioned in
https://issues.apache.org/jira/browse/CASSANDRA-18508 ? I think having a
pluggable credentials provider (parameterized class) make sense to provide a
unified solution to multiple passwords/credentials we have today in config
files. This will help in either fetching the credentials from a file, env
variables (e.g. K8s env vars) etc vs just files.
However by 'unified' I don't mean a 'single class'. Just a single interface and
a mechanism and have ability to write providers if needed.
> Security: provide keystore_password_file and truststore_password_file options
> -
>
> Key: CASSANDRA-13428
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13428
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Config
>Reporter: Bas van Dijk
>Priority: Normal
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> Currently passwords are stored in plaintext in the configuration file as in:
> {code}
> server_encryption_options:
> keystore_password: secret
> truststore_password: secret
> client_encryption_options:
> keystore_password: secret
> {code}
> This has the disadvantage that, in order to protect the secrets, the whole
> configuration file needs to have restricted ownership and permissions. This
> is problematic in operating systems like NixOS where configuration files are
> usually stored in world-readable locations.
> A secure option would be to store secrets in files (with restricted ownership
> and permissions) and reference those files from the unrestricted
> configuration file as in for example:
> {code}
> server_encryption_options:
> keystore_password_file: /run/keys/keystore-password
> truststore_password_file: /run/keys/truststore-password
> client_encryption_options:
> keystore_password_file: /run/keys/keystore-password
> {code}
> This is trivial to implement and provides a big gain in security.
> So in summary I'm proposing to add the {{keystore_password_file}} and
> {{truststore_password_file}} options besides the existing
> {{keystore_password}} and {{truststore_password options}}. The former will
> take precedence over the latter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-13428) Security: provide keystore_password_file and truststore_password_file options
[
https://issues.apache.org/jira/browse/CASSANDRA-13428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862600#comment-17862600
]
Maulin Vasavada edited comment on CASSANDRA-13428 at 7/2/24 9:30 PM:
-
Can this be addressed with a similar approach mentioned in
https://issues.apache.org/jira/browse/CASSANDRA-18508 ? I think having a
pluggable credentials provider (parameterized class) make sense to provide a
unified solution to multiple passwords/credentials we have today in config
files. This will help in either fetching the credentials from a file, env
variables (e.g. K8s env vars) etc vs just files.
However by 'unified' I don't mean a 'single class'. Just a single interface and
a mechanism and have ability to write providers if needed.
was (Author: maulin.vasavada):
Can this be addressed with a similar approach mentioned in
https://issues.apache.org/jira/browse/CASSANDRA-18508 ? I think having a
pluggable credentials provider (parameterized class) make sense to provide a
unified solution to multiple passwords/credentials we have today in config
files. This will help in either fetching the credentials from a file, env
variables (e.g. K8s env vars) etc vs just files.
> Security: provide keystore_password_file and truststore_password_file options
> -
>
> Key: CASSANDRA-13428
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13428
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Config
>Reporter: Bas van Dijk
>Priority: Normal
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> Currently passwords are stored in plaintext in the configuration file as in:
> {code}
> server_encryption_options:
> keystore_password: secret
> truststore_password: secret
> client_encryption_options:
> keystore_password: secret
> {code}
> This has the disadvantage that, in order to protect the secrets, the whole
> configuration file needs to have restricted ownership and permissions. This
> is problematic in operating systems like NixOS where configuration files are
> usually stored in world-readable locations.
> A secure option would be to store secrets in files (with restricted ownership
> and permissions) and reference those files from the unrestricted
> configuration file as in for example:
> {code}
> server_encryption_options:
> keystore_password_file: /run/keys/keystore-password
> truststore_password_file: /run/keys/truststore-password
> client_encryption_options:
> keystore_password_file: /run/keys/keystore-password
> {code}
> This is trivial to implement and provides a big gain in security.
> So in summary I'm proposing to add the {{keystore_password_file}} and
> {{truststore_password_file}} options besides the existing
> {{keystore_password}} and {{truststore_password options}}. The former will
> take precedence over the latter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13428) Security: provide keystore_password_file and truststore_password_file options
[
https://issues.apache.org/jira/browse/CASSANDRA-13428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862602#comment-17862602
]
Maulin Vasavada commented on CASSANDRA-13428:
-
cc: [~smiklosovic] [~brandon.williams]
> Security: provide keystore_password_file and truststore_password_file options
> -
>
> Key: CASSANDRA-13428
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13428
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Config
>Reporter: Bas van Dijk
>Priority: Normal
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> Currently passwords are stored in plaintext in the configuration file as in:
> {code}
> server_encryption_options:
> keystore_password: secret
> truststore_password: secret
> client_encryption_options:
> keystore_password: secret
> {code}
> This has the disadvantage that, in order to protect the secrets, the whole
> configuration file needs to have restricted ownership and permissions. This
> is problematic in operating systems like NixOS where configuration files are
> usually stored in world-readable locations.
> A secure option would be to store secrets in files (with restricted ownership
> and permissions) and reference those files from the unrestricted
> configuration file as in for example:
> {code}
> server_encryption_options:
> keystore_password_file: /run/keys/keystore-password
> truststore_password_file: /run/keys/truststore-password
> client_encryption_options:
> keystore_password_file: /run/keys/keystore-password
> {code}
> This is trivial to implement and provides a big gain in security.
> So in summary I'm proposing to add the {{keystore_password_file}} and
> {{truststore_password_file}} options besides the existing
> {{keystore_password}} and {{truststore_password options}}. The former will
> take precedence over the latter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13428) Security: provide keystore_password_file and truststore_password_file options
[
https://issues.apache.org/jira/browse/CASSANDRA-13428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862601#comment-17862601
]
Maulin Vasavada commented on CASSANDRA-13428:
-
It has been a while I touched this code :( (bumps ahead :) ) but I can try to
work out a solution in next few weeks/months.
> Security: provide keystore_password_file and truststore_password_file options
> -
>
> Key: CASSANDRA-13428
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13428
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Config
>Reporter: Bas van Dijk
>Priority: Normal
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> Currently passwords are stored in plaintext in the configuration file as in:
> {code}
> server_encryption_options:
> keystore_password: secret
> truststore_password: secret
> client_encryption_options:
> keystore_password: secret
> {code}
> This has the disadvantage that, in order to protect the secrets, the whole
> configuration file needs to have restricted ownership and permissions. This
> is problematic in operating systems like NixOS where configuration files are
> usually stored in world-readable locations.
> A secure option would be to store secrets in files (with restricted ownership
> and permissions) and reference those files from the unrestricted
> configuration file as in for example:
> {code}
> server_encryption_options:
> keystore_password_file: /run/keys/keystore-password
> truststore_password_file: /run/keys/truststore-password
> client_encryption_options:
> keystore_password_file: /run/keys/keystore-password
> {code}
> This is trivial to implement and provides a big gain in security.
> So in summary I'm proposing to add the {{keystore_password_file}} and
> {{truststore_password_file}} options besides the existing
> {{keystore_password}} and {{truststore_password options}}. The former will
> take precedence over the latter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-13428) Security: provide keystore_password_file and truststore_password_file options
[
https://issues.apache.org/jira/browse/CASSANDRA-13428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862601#comment-17862601
]
Maulin Vasavada edited comment on CASSANDRA-13428 at 7/2/24 9:27 PM:
-
It has been a while since I touched this code :( (bumps ahead :) ) but I can
try to work out a solution in next few weeks/months.
was (Author: maulin.vasavada):
It has been a while I touched this code :( (bumps ahead :) ) but I can try to
work out a solution in next few weeks/months.
> Security: provide keystore_password_file and truststore_password_file options
> -
>
> Key: CASSANDRA-13428
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13428
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Config
>Reporter: Bas van Dijk
>Priority: Normal
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> Currently passwords are stored in plaintext in the configuration file as in:
> {code}
> server_encryption_options:
> keystore_password: secret
> truststore_password: secret
> client_encryption_options:
> keystore_password: secret
> {code}
> This has the disadvantage that, in order to protect the secrets, the whole
> configuration file needs to have restricted ownership and permissions. This
> is problematic in operating systems like NixOS where configuration files are
> usually stored in world-readable locations.
> A secure option would be to store secrets in files (with restricted ownership
> and permissions) and reference those files from the unrestricted
> configuration file as in for example:
> {code}
> server_encryption_options:
> keystore_password_file: /run/keys/keystore-password
> truststore_password_file: /run/keys/truststore-password
> client_encryption_options:
> keystore_password_file: /run/keys/keystore-password
> {code}
> This is trivial to implement and provides a big gain in security.
> So in summary I'm proposing to add the {{keystore_password_file}} and
> {{truststore_password_file}} options besides the existing
> {{keystore_password}} and {{truststore_password options}}. The former will
> take precedence over the latter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13428) Security: provide keystore_password_file and truststore_password_file options
[
https://issues.apache.org/jira/browse/CASSANDRA-13428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862600#comment-17862600
]
Maulin Vasavada commented on CASSANDRA-13428:
-
Can this be addressed with a similar approach mentioned in
https://issues.apache.org/jira/browse/CASSANDRA-18508 ? I think having a
pluggable credentials provider (parameterized class) make sense to provide a
unified solution to multiple passwords/credentials we have today in config
files. This will help in either fetching the credentials from a file, env
variables (e.g. K8s env vars) etc vs just files.
> Security: provide keystore_password_file and truststore_password_file options
> -
>
> Key: CASSANDRA-13428
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13428
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Config
>Reporter: Bas van Dijk
>Priority: Normal
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> Currently passwords are stored in plaintext in the configuration file as in:
> {code}
> server_encryption_options:
> keystore_password: secret
> truststore_password: secret
> client_encryption_options:
> keystore_password: secret
> {code}
> This has the disadvantage that, in order to protect the secrets, the whole
> configuration file needs to have restricted ownership and permissions. This
> is problematic in operating systems like NixOS where configuration files are
> usually stored in world-readable locations.
> A secure option would be to store secrets in files (with restricted ownership
> and permissions) and reference those files from the unrestricted
> configuration file as in for example:
> {code}
> server_encryption_options:
> keystore_password_file: /run/keys/keystore-password
> truststore_password_file: /run/keys/truststore-password
> client_encryption_options:
> keystore_password_file: /run/keys/keystore-password
> {code}
> This is trivial to implement and provides a big gain in security.
> So in summary I'm proposing to add the {{keystore_password_file}} and
> {{truststore_password_file}} options besides the existing
> {{keystore_password}} and {{truststore_password options}}. The former will
> take precedence over the latter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19739) Move bcprov-jdk18on-1.76.jar to build deps
[ https://issues.apache.org/jira/browse/CASSANDRA-19739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862594#comment-17862594 ] Brandon Williams commented on CASSANDRA-19739: -- +1 > Move bcprov-jdk18on-1.76.jar to build deps > -- > > Key: CASSANDRA-19739 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19739 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.x > > > This came up after I bumped dependency-check version to 10.0.0 as suggested > in CASSANDRA-19738. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19739) Move bcprov-jdk18on-1.76.jar to build deps
[ https://issues.apache.org/jira/browse/CASSANDRA-19739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-19739: -- Fix Version/s: 5.0-beta2 > Move bcprov-jdk18on-1.76.jar to build deps > -- > > Key: CASSANDRA-19739 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19739 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.0-beta2, 5.x > > > This came up after I bumped dependency-check version to 10.0.0 as suggested > in CASSANDRA-19738. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19739) Move bcprov-jdk18on-1.76.jar to build deps
[
https://issues.apache.org/jira/browse/CASSANDRA-19739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862593#comment-17862593
]
Stefan Miklosovic commented on CASSANDRA-19739:
---
[CASSANDRA-19739-5.0|https://github.com/instaclustr/cassandra/tree/CASSANDRA-19739-5.0]
{noformat}
java11_pre-commit_tests
✓ j11_build8m 25s
✓ j11_cqlsh_dtests_py311 9m 58s
✓ j11_cqlsh_dtests_py311_vnode 8m 2s
✓ j11_cqlsh_dtests_py388m 47s
✓ j11_cqlsh_dtests_py38_vnode 10m 50s
✓ j11_cqlshlib_cython_tests11m 1s
✓ j11_cqlshlib_tests 9m 56s
✓ j11_dtests 38m 43s
✓ j11_dtests_latest 37m 44s
✓ j11_dtests_vnode37m 50s
✓ j11_jvm_dtests 29m 29s
✓ j11_jvm_dtests_latest_vnode 20m 4s
✓ j11_simulator_dtests 7m 2s
✓ j11_unit_tests 15m 26s
✓ j11_utests_latest 16m 50s
✓ j11_utests_oa 18m 36s
✓ j11_utests_system_keyspace_directory17m 32s
✓ j17_cqlsh_dtests_py311 6m 39s
✓ j17_cqlsh_dtests_py311_vnode 6m 32s
✓ j17_cqlsh_dtests_py386m 22s
✓ j17_cqlsh_dtests_py38_vnode 6m 14s
✓ j17_cqlshlib_cython_tests 7m 5s
✓ j17_cqlshlib_tests 8m 43s
✓ j17_dtests 33m 11s
✓ j17_dtests_latest 34m 20s
✓ j17_dtests_vnode32m 27s
✓ j17_jvm_dtests 25m 58s
✓ j17_jvm_dtests_latest_vnode 15m 4s
✓ j17_unit_tests 14m 19s
✓ j17_utests_latest 13m 34s
✓ j17_utests_oa 14m 40s
java11_separate_tests
{noformat}
[java11_pre-commit_tests|https://app.circleci.com/pipelines/github/instaclustr/cassandra/4445/workflows/2964649a-e712-4684-84b5-8d8cd20cd945]
> Move bcprov-jdk18on-1.76.jar to build deps
> --
>
> Key: CASSANDRA-19739
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19739
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 5.x
>
>
> This came up after I bumped dependency-check version to 10.0.0 as suggested
> in CASSANDRA-19738.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19739) Move bcprov-jdk18on-1.76.jar to build deps
[ https://issues.apache.org/jira/browse/CASSANDRA-19739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-19739: -- Status: Needs Committer (was: Patch Available) > Move bcprov-jdk18on-1.76.jar to build deps > -- > > Key: CASSANDRA-19739 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19739 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.x > > > This came up after I bumped dependency-check version to 10.0.0 as suggested > in CASSANDRA-19738. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19704) UnsupportedOperationException is thrown when no space for LCS
[
https://issues.apache.org/jira/browse/CASSANDRA-19704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-19704:
Fix Version/s: 4.0.14
4.1.6
5.0
5.1
(was: 5.x)
(was: 4.0.x)
(was: 4.1.x)
(was: 5.0.x)
Since Version: 4.0
Source Control Link:
https://github.com/apache/cassandra/commit/d54646e40957ffc18f651753941fac3068b79f8e
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed as
https://github.com/apache/cassandra/commit/d54646e40957ffc18f651753941fac3068b79f8e
> UnsupportedOperationException is thrown when no space for LCS
> -
>
> Key: CASSANDRA-19704
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19704
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction/LCS
>Reporter: Zhao Yang
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 4.0.14, 4.1.6, 5.0, 5.1
>
> Attachments: ci_summary-1.html, ci_summary-2.html, ci_summary-3.html,
> ci_summary.html
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In {{CompactionTask#buildCompactionCandidatesForAvailableDiskSpace}} with
> LCS, if node has limited disk space and can't remove any sstable from L0 or
> L1 in {{{}LeveledCompactionTask#reduceScopeForLimitedSpace{}}},
> {{LeveledCompactionTask#partialCompactionsAcceptable}} will throw
> {{UnsupportedOperationException}}.
> We should handle {{LeveledCompactionTask#partialCompactionsAcceptable}} more
> gracefully with {{return level <= 1}} or simply {{true}} since
> {{reduceScopeForLimitedSpace}} only removes sstable from L0 or L1.
> Related https://issues.apache.org/jira/browse/CASSANDRA-17272
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19745) Schema change failed in Cassandra Dtest after node restart and upgrade but success in setup
ConfX created CASSANDRA-19745:
-
Summary: Schema change failed in Cassandra Dtest after node
restart and upgrade but success in setup
Key: CASSANDRA-19745
URL: https://issues.apache.org/jira/browse/CASSANDRA-19745
Project: Cassandra
Issue Type: Bug
Components: Test/dtest/java
Reporter: ConfX
h2. What happened
Cassandra dtest {{schemaChange}} behaves differently in {{setup}} and
{{{}runAfterNodeUpgrade{}}}.
h2. How to reproduce:
Put the following test under
{{{}cassandra/test/distributed/org/apache/cassandra/distributed/upgrade/{}}},
and build dtest jars.
{code:java}
package org.apache.cassandra.distributed.upgrade;
public class demoUpgradeTest extends UpgradeTestBase {
@Test
public void firstDemoTest() throws Throwable {
new TestCase()
.nodes(2)
.nodesToUpgrade(1)
.withConfig((cfg) -> cfg.with(Feature.NETWORK, Feature.GOSSIP))
.upgradesToCurrentFrom(v3X)
.setup((cluster) -> {
cluster.schemaChange(withKeyspace("CREATE TABLE %s.tbl (pk int, ck
int, v1 int, PRIMARY KEY (pk, ck))"));
})
.runAfterNodeUpgrade((cluster, node) -> {
// let's do nothing here.
}).run();
}
@Test
public void secondDemoTest() throws Throwable {
new TestCase()
.nodes(2)
.nodesToUpgrade(1)
.withConfig((cfg) -> cfg.with(Feature.NETWORK, Feature.GOSSIP))
.upgradesToCurrentFrom(v3X)
.setup((cluster) -> {
// let's do nothing here.
})
.runAfterNodeUpgrade((cluster, node) -> {
cluster.schemaChange(withKeyspace("CREATE TABLE %s.tbl (pk int, ck
int, v1 int, PRIMARY KEY (pk, ck))"));
}).run();
}
} {code}
Run the test with:
{code:java}
$ ant test-jvm-dtest-some-Duse.jdk11=true
-Dtest.name=org.apache.cassandra.distributed.upgrade.demoUpgradeTest {code}
firstDemoTest passes, but secondDemoTest fails with the following output:
{code:java}
java.lang.AssertionError: Error in test '5.0-beta2 -> [5.1]' while upgrading to
'5.1'; successful upgrades []
at
org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:396)
at
org.apache.cassandra.distributed.upgrade.demoUpgradeTest.secondDemoTest(demoUpgradeTest.java:56)
Caused by: java.lang.IllegalStateException: Can't commit transformations when
running in gossip mode. Enable the ClusterMetadataService with `nodetool
addtocms`.
at
org.apache.cassandra.tcm.migration.GossipProcessor.commit(GossipProcessor.java:34)
at
org.apache.cassandra.tcm.ClusterMetadataService$SwitchableProcessor.commit(ClusterMetadataService.java:836)
at org.apache.cassandra.tcm.Processor.commit(Processor.java:45)
at
org.apache.cassandra.tcm.ClusterMetadataService.commit(ClusterMetadataService.java:511)
at org.apache.cassandra.schema.Schema.submit(Schema.java:292) {code}
As a previous issue suggested, {{schemaChange}} would fail to execute when
gossip mode is disabled. However, even with gossip mode enabled,
{{schemaChange}} behaves differently in {{setup}} and
{{{}runAfterNodeUpgrade{}}}. Executing {{schemaChange}} in
{{runAfterNodeUpgrade}} would call the {{commit}} function in
[{{org.apache.cassandra.tcm.migration.GossipProcessor.java}}|https://github.com/apache/cassandra/blob/cbe07fd57e3d94a1f2512fced3f38e69ad4b3eb2/src/java/org/apache/cassandra/tcm/migration/GossipProcessor.java#L32]:
{code:java}
public Commit.Result commit(Entry.Id entryId, Transformation transform, Epoch
lastKnown, Retry.Deadline retryPolicy)
{
throw new IllegalStateException("Can't commit transformations when running
in gossip mode. Enable the ClusterMetadataService with `nodetool addtocms`.");
} {code}
which directly throws an exception.
The expected behavior should be that {{schemaChange}} consistently in {{setup}}
and {{{}runAfterNodeUpgrade{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra) branch cassandra-4.1 updated (875793bc19 -> f378f92030)
This is an automated email from the ASF dual-hosted git repository. maedhroz pushed a change to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 875793bc19 Merge branch 'cassandra-4.0' into cassandra-4.1 new d54646e409 UnsupportedOperationException when reducing scope for LCS compactions new f378f92030 Merge branch 'cassandra-4.0' into cassandra-4.1 The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: CHANGES.txt| 1 + .../db/compaction/LeveledCompactionTask.java | 2 +- .../test/LeveledCompactionTaskTest.java| 92 ++ 3 files changed, 94 insertions(+), 1 deletion(-) create mode 100644 test/distributed/org/apache/cassandra/distributed/test/LeveledCompactionTaskTest.java - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra) branch cassandra-5.0 updated (37f6a5de20 -> 1bec8b99ca)
This is an automated email from the ASF dual-hosted git repository. maedhroz pushed a change to branch cassandra-5.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 37f6a5de20 Merge branch 'cassandra-4.1' into cassandra-5.0 new d54646e409 UnsupportedOperationException when reducing scope for LCS compactions new f378f92030 Merge branch 'cassandra-4.0' into cassandra-4.1 new 1bec8b99ca Merge branch 'cassandra-4.1' into cassandra-5.0 The 3 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: CHANGES.txt| 1 + .../db/compaction/LeveledCompactionTask.java | 2 +- .../test/LeveledCompactionTaskTest.java| 94 ++ 3 files changed, 96 insertions(+), 1 deletion(-) create mode 100644 test/distributed/org/apache/cassandra/distributed/test/LeveledCompactionTaskTest.java - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra) branch trunk updated (cbe07fd57e -> b25995fc44)
This is an automated email from the ASF dual-hosted git repository. maedhroz pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from cbe07fd57e Reconfigure CMS after replacement, bootstrap and move operations new d54646e409 UnsupportedOperationException when reducing scope for LCS compactions new f378f92030 Merge branch 'cassandra-4.0' into cassandra-4.1 new 1bec8b99ca Merge branch 'cassandra-4.1' into cassandra-5.0 new b25995fc44 Merge branch 'cassandra-5.0' into trunk The 4 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: CHANGES.txt| 1 + .../db/compaction/LeveledCompactionTask.java | 2 +- .../test/LeveledCompactionTaskTest.java| 94 ++ 3 files changed, 96 insertions(+), 1 deletion(-) create mode 100644 test/distributed/org/apache/cassandra/distributed/test/LeveledCompactionTaskTest.java - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra) 01/01: Merge branch 'cassandra-5.0' into trunk
This is an automated email from the ASF dual-hosted git repository. maedhroz pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit b25995fc44dd676f3e6e69a44331d5c9b0c0b293 Merge: cbe07fd57e 1bec8b99ca Author: Caleb Rackliffe AuthorDate: Tue Jul 2 14:41:01 2024 -0500 Merge branch 'cassandra-5.0' into trunk * cassandra-5.0: UnsupportedOperationException when reducing scope for LCS compactions CHANGES.txt| 1 + .../db/compaction/LeveledCompactionTask.java | 2 +- .../test/LeveledCompactionTaskTest.java| 94 ++ 3 files changed, 96 insertions(+), 1 deletion(-) diff --cc CHANGES.txt index e37528d201,56e6cbd4a5..fd8561af1a --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -99,11 -48,14 +99,12 @@@ Merged from 4.1 * Fix hints delivery for a node going down repeatedly (CASSANDRA-19495) * Do not go to disk for reading hints file sizes (CASSANDRA-19477) * Fix system_views.settings to handle array types (CASSANDRA-19475) - * Memoize Cassandra verion and add a backoff interval for failed schema pulls (CASSANDRA-18902) * Fix StackOverflowError on ALTER after many previous schema changes (CASSANDRA-19166) + * Memoize Cassandra verion (CASSANDRA-18902) Merged from 4.0: + * UnsupportedOperationException when reducing scope for LCS compactions (CASSANDRA-19704) * Make LWT conditions behavior on frozen and non-frozen columns consistent for null column values (CASSANDRA-19637) - * Add timeout specifically for bootstrapping nodes (CASSANDRA-15439) - * Bring Redhat packge dirs/ownership/perms in line with Debian package (CASSANDRA-19565) + * Bring Redhat package dirs/ownership/perms in line with Debian package (CASSANDRA-19565) * Make nodetool import congruent with the documentation by not relying on the folder structure of the imported SSTable files (CASSANDRA-19401) * IR may leak SSTables with pending repair when coming from streaming (CASSANDRA-19182) * Streaming exception race creates corrupt transaction log files that prevent restart (CASSANDRA-18736) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra) 01/01: Merge branch 'cassandra-4.1' into cassandra-5.0
This is an automated email from the ASF dual-hosted git repository.
maedhroz pushed a commit to branch cassandra-5.0
in repository https://gitbox.apache.org/repos/asf/cassandra.git
commit 1bec8b99ca0810f90851d7a95bac2dbbf0bbea80
Merge: 37f6a5de20 f378f92030
Author: Caleb Rackliffe
AuthorDate: Tue Jul 2 14:18:57 2024 -0500
Merge branch 'cassandra-4.1' into cassandra-5.0
* cassandra-4.1:
UnsupportedOperationException when reducing scope for LCS compactions
CHANGES.txt| 1 +
.../db/compaction/LeveledCompactionTask.java | 2 +-
.../test/LeveledCompactionTaskTest.java| 94 ++
3 files changed, 96 insertions(+), 1 deletion(-)
diff --cc CHANGES.txt
index 71dd1ab1ab,cdceaa802d..56e6cbd4a5
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -49,12 -17,8 +49,13 @@@ Merged from 4.1
* Fix hints delivery for a node going down repeatedly (CASSANDRA-19495)
* Do not go to disk for reading hints file sizes (CASSANDRA-19477)
* Fix system_views.settings to handle array types (CASSANDRA-19475)
+ * Memoize Cassandra verion and add a backoff interval for failed schema
pulls (CASSANDRA-18902)
+ * Fix StackOverflowError on ALTER after many previous schema changes
(CASSANDRA-19166)
Merged from 4.0:
+ * UnsupportedOperationException when reducing scope for LCS compactions
(CASSANDRA-19704)
+ * Make LWT conditions behavior on frozen and non-frozen columns consistent
for null column values (CASSANDRA-19637)
+ * Add timeout specifically for bootstrapping nodes (CASSANDRA-15439)
+ * Bring Redhat packge dirs/ownership/perms in line with Debian package
(CASSANDRA-19565)
* Make nodetool import congruent with the documentation by not relying on
the folder structure of the imported SSTable files (CASSANDRA-19401)
* IR may leak SSTables with pending repair when coming from streaming
(CASSANDRA-19182)
* Streaming exception race creates corrupt transaction log files that
prevent restart (CASSANDRA-18736)
diff --cc
test/distributed/org/apache/cassandra/distributed/test/LeveledCompactionTaskTest.java
index 00,dccad716e2..d89f3c0079
mode 00,100644..100644
---
a/test/distributed/org/apache/cassandra/distributed/test/LeveledCompactionTaskTest.java
+++
b/test/distributed/org/apache/cassandra/distributed/test/LeveledCompactionTaskTest.java
@@@ -1,0 -1,92 +1,94 @@@
+ /*
+ * 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.
+ */
+
+ package org.apache.cassandra.distributed.test;
+
+ import java.io.IOException;
++import java.nio.file.FileStore;
++import java.util.Map;
+
+ import org.junit.Test;
+
+ import net.bytebuddy.ByteBuddy;
+ import net.bytebuddy.dynamic.loading.ClassLoadingStrategy;
+ import net.bytebuddy.implementation.MethodDelegation;
+ import org.apache.cassandra.db.Directories;
+ import org.apache.cassandra.db.Keyspace;
+ import org.apache.cassandra.distributed.Cluster;
+ import org.apache.cassandra.distributed.api.ConsistencyLevel;
+
+ import static net.bytebuddy.matcher.ElementMatchers.named;
+ import static net.bytebuddy.matcher.ElementMatchers.takesArguments;
+ import static org.junit.Assert.fail;
+
+ public class LeveledCompactionTaskTest extends TestBaseImpl
+ {
+ @Test
+ public void testBuildCompactionCandidatesForAvailableDiskSpace() throws
IOException
+ {
+ try (Cluster cluster = init(builder().withNodes(1)
+ .withConfig(config ->
config.set("autocompaction_on_startup_enabled", false))
+
.withInstanceInitializer(BB::install).start()))
+ {
+ cluster.schemaChange(withKeyspace("CREATE TABLE %s.tbl (id int
primary key) WITH compaction = {'class':'LeveledCompactionStrategy',
'enabled':'false'}"));
+ for (int i = 0; i < 100; i++)
+ {
+ cluster.coordinator(1).execute(withKeyspace("INSERT INTO
%s.tbl (id) VALUES (?)"), ConsistencyLevel.ALL, i);
+ if (i % 10 == 0)
+ cluster.get(1).flush(KEYSPACE);
+ }
+ cluster.get(1).flush(KEYSPACE);
+ cluster.setUncaughtExceptionsFilter((exception) ->
exce
(cassandra) 01/01: Merge branch 'cassandra-4.0' into cassandra-4.1
This is an automated email from the ASF dual-hosted git repository.
maedhroz pushed a commit to branch cassandra-4.1
in repository https://gitbox.apache.org/repos/asf/cassandra.git
commit f378f92030f3813ebcff7be155f526500af7ac21
Merge: 875793bc19 d54646e409
Author: Caleb Rackliffe
AuthorDate: Tue Jul 2 14:05:23 2024 -0500
Merge branch 'cassandra-4.0' into cassandra-4.1
* cassandra-4.0:
UnsupportedOperationException when reducing scope for LCS compactions
CHANGES.txt| 1 +
.../db/compaction/LeveledCompactionTask.java | 2 +-
.../test/LeveledCompactionTaskTest.java| 92 ++
3 files changed, 94 insertions(+), 1 deletion(-)
diff --cc CHANGES.txt
index 4028f905ef,52ec8bc211..cdceaa802d
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -11,13 -7,7 +11,14 @@@ Merged from 3.0
* Upgrade OWASP to 10.0.0 (CASSANDRA-19738)
-4.0.13
+4.1.5
+ * Make queries visible to the "system_views.queries" virtual table at the
coordinator level (CASSANDRA-19577)
+ * Concurrent equivalent schema updates lead to unresolved disagreement
(CASSANDRA-19578)
+ * Fix hints delivery for a node going down repeatedly (CASSANDRA-19495)
+ * Do not go to disk for reading hints file sizes (CASSANDRA-19477)
+ * Fix system_views.settings to handle array types (CASSANDRA-19475)
+Merged from 4.0:
++ * UnsupportedOperationException when reducing scope for LCS compactions
(CASSANDRA-19704)
* Make nodetool import congruent with the documentation by not relying on
the folder structure of the imported SSTable files (CASSANDRA-19401)
* IR may leak SSTables with pending repair when coming from streaming
(CASSANDRA-19182)
* Streaming exception race creates corrupt transaction log files that
prevent restart (CASSANDRA-18736)
diff --cc
test/distributed/org/apache/cassandra/distributed/test/LeveledCompactionTaskTest.java
index 00,f1051e6109..dccad716e2
mode 00,100644..100644
---
a/test/distributed/org/apache/cassandra/distributed/test/LeveledCompactionTaskTest.java
+++
b/test/distributed/org/apache/cassandra/distributed/test/LeveledCompactionTaskTest.java
@@@ -1,0 -1,88 +1,92 @@@
+ /*
+ * 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.
+ */
+
+ package org.apache.cassandra.distributed.test;
+
+ import java.io.IOException;
+
+ import org.junit.Test;
+
+ import net.bytebuddy.ByteBuddy;
+ import net.bytebuddy.dynamic.loading.ClassLoadingStrategy;
+ import net.bytebuddy.implementation.MethodDelegation;
+ import org.apache.cassandra.db.Directories;
+ import org.apache.cassandra.db.Keyspace;
+ import org.apache.cassandra.distributed.Cluster;
+ import org.apache.cassandra.distributed.api.ConsistencyLevel;
+
+ import static net.bytebuddy.matcher.ElementMatchers.named;
+ import static net.bytebuddy.matcher.ElementMatchers.takesArguments;
+ import static org.junit.Assert.fail;
+
+ public class LeveledCompactionTaskTest extends TestBaseImpl
+ {
+ @Test
+ public void testBuildCompactionCandidatesForAvailableDiskSpace() throws
IOException
+ {
-try (Cluster cluster =
init(builder().withNodes(1).withInstanceInitializer(BB::install).start()))
++try (Cluster cluster = init(builder().withNodes(1)
++ .withConfig(config ->
config.set("autocompaction_on_startup_enabled", false))
++
.withInstanceInitializer(BB::install).start()))
+ {
+ cluster.schemaChange(withKeyspace("CREATE TABLE %s.tbl (id int
primary key) WITH compaction = {'class':'LeveledCompactionStrategy',
'enabled':'false'}"));
+ for (int i = 0; i < 100; i++)
+ {
+ cluster.coordinator(1).execute(withKeyspace("INSERT INTO
%s.tbl (id) VALUES (?)"), ConsistencyLevel.ALL, i);
+ if (i % 10 == 0)
+ cluster.get(1).flush(KEYSPACE);
+ }
+ cluster.get(1).flush(KEYSPACE);
+ cluster.setUncaughtExceptionsFilter((exception) ->
exception.getMessage() != null && exception.getMessage().contains("Not enough
space for compaction"));
+
+ cluster.get(1).runOnInstance(()
(cassandra) branch cassandra-4.0 updated: UnsupportedOperationException when reducing scope for LCS compactions
This is an automated email from the ASF dual-hosted git repository.
maedhroz pushed a commit to branch cassandra-4.0
in repository https://gitbox.apache.org/repos/asf/cassandra.git
The following commit(s) were added to refs/heads/cassandra-4.0 by this push:
new d54646e409 UnsupportedOperationException when reducing scope for LCS
compactions
d54646e409 is described below
commit d54646e40957ffc18f651753941fac3068b79f8e
Author: Marcus Eriksson
AuthorDate: Fri May 27 00:40:44 2022 +0200
UnsupportedOperationException when reducing scope for LCS compactions
patch by Caleb Rackliffe; reviewed by Zhao Yang, Brandon Williams, and
Marcus Eriksson for CASSANDRA-19704
Co-authored-by: Marcus Eriksson
Co-authored-by: Caleb Rackliffe
---
CHANGES.txt| 1 +
.../db/compaction/LeveledCompactionTask.java | 2 +-
.../test/LeveledCompactionTaskTest.java| 88 ++
3 files changed, 90 insertions(+), 1 deletion(-)
diff --git a/CHANGES.txt b/CHANGES.txt
index 9ac326d3e2..52ec8bc211 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
4.0.14
+ * UnsupportedOperationException when reducing scope for LCS compactions
(CASSANDRA-19704)
* Make LWT conditions behavior on frozen and non-frozen columns consistent
for null column values (CASSANDRA-19637)
* Add timeout specifically for bootstrapping nodes (CASSANDRA-15439)
* Bring Redhat package dirs/ownership/perms in line with Debian package
(CASSANDRA-19565)
diff --git
a/src/java/org/apache/cassandra/db/compaction/LeveledCompactionTask.java
b/src/java/org/apache/cassandra/db/compaction/LeveledCompactionTask.java
index 5b94c545fe..ae9f15491b 100644
--- a/src/java/org/apache/cassandra/db/compaction/LeveledCompactionTask.java
+++ b/src/java/org/apache/cassandra/db/compaction/LeveledCompactionTask.java
@@ -56,7 +56,7 @@ public class LeveledCompactionTask extends CompactionTask
@Override
protected boolean partialCompactionsAcceptable()
{
-throw new UnsupportedOperationException("This is now handled in
reduceScopeForLimitedSpace");
+return level == 0;
}
protected int getLevel()
diff --git
a/test/distributed/org/apache/cassandra/distributed/test/LeveledCompactionTaskTest.java
b/test/distributed/org/apache/cassandra/distributed/test/LeveledCompactionTaskTest.java
new file mode 100644
index 00..f1051e6109
--- /dev/null
+++
b/test/distributed/org/apache/cassandra/distributed/test/LeveledCompactionTaskTest.java
@@ -0,0 +1,88 @@
+/*
+ * 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.
+ */
+
+package org.apache.cassandra.distributed.test;
+
+import java.io.IOException;
+
+import org.junit.Test;
+
+import net.bytebuddy.ByteBuddy;
+import net.bytebuddy.dynamic.loading.ClassLoadingStrategy;
+import net.bytebuddy.implementation.MethodDelegation;
+import org.apache.cassandra.db.Directories;
+import org.apache.cassandra.db.Keyspace;
+import org.apache.cassandra.distributed.Cluster;
+import org.apache.cassandra.distributed.api.ConsistencyLevel;
+
+import static net.bytebuddy.matcher.ElementMatchers.named;
+import static net.bytebuddy.matcher.ElementMatchers.takesArguments;
+import static org.junit.Assert.fail;
+
+public class LeveledCompactionTaskTest extends TestBaseImpl
+{
+@Test
+public void testBuildCompactionCandidatesForAvailableDiskSpace() throws
IOException
+{
+try (Cluster cluster =
init(builder().withNodes(1).withInstanceInitializer(BB::install).start()))
+{
+cluster.schemaChange(withKeyspace("CREATE TABLE %s.tbl (id int
primary key) WITH compaction = {'class':'LeveledCompactionStrategy',
'enabled':'false'}"));
+for (int i = 0; i < 100; i++)
+{
+cluster.coordinator(1).execute(withKeyspace("INSERT INTO
%s.tbl (id) VALUES (?)"), ConsistencyLevel.ALL, i);
+if (i % 10 == 0)
+cluster.get(1).flush(KEYSPACE);
+}
+cluster.get(1).flush(KEYSPACE);
+cluster.setUncaughtExceptionsFilter((exception) ->
exception.getMessage() != null && exception.getMessage().contains("Not enough
space for compaction"));
+
+
[jira] [Commented] (CASSANDRA-19545) Null pointer when running Upgrade Tests
[
https://issues.apache.org/jira/browse/CASSANDRA-19545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862570#comment-17862570
]
ConfX commented on CASSANDRA-19545:
---
[~mck] There is a logic to find all the local "build/dtest-*.jar" and set those
jars as target versions. Should we just include all the existing versions
(through the local jars) instead of also having non-existing versions?
> Null pointer when running Upgrade Tests
> ---
>
> Key: CASSANDRA-19545
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19545
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: ConfX
>Priority: Normal
>
> h2. What happened
> The `UpgradeTestBase.java` may throw null pointer exception when creating the
> version upgrade pairs in `upgradesTo()` method.
> The problem happens in the for loop shown below. The `upgradesTo()` calls
> `versions.getLatest(Semver version)` method to create the `Version` class.
> {code:java}
> for (Semver start : vertices.subSet(lowerBound, true, to, false))
> {
> // only include pairs that are allowed, and start or end on CURRENT
> if (SUPPORTED_UPGRADE_PATHS.hasEdge(start, to) &&
> edgeTouchesTarget(start, to, CURRENT))
> upgrade.add(new TestVersions(versions.getLatest(start),
> Collections.singletonList(versions.getLatest(to;
> } {code}
> However, in the `Version.java`, `getLatest()` function never checks whether
> the `first(version)` is in the `versions` map or not. When the version is not
> there, a null pointer exception will be thrown and crash all the upgrade
> tests.
> {code:java}
> public Version getLatest(Semver version)
> {
> return versions.get(first(version)) // <--- Here might cause NPE
> .stream()
> .findFirst()
> .orElseThrow(() -> new RuntimeException("No " +
> version + " versions found"));
> }
> {code}
> h2. How to reproduce
> To reproduce this bug, I'm running Cassandra with commit SHA
> `310d790ce4734727f943225eb951ab0d889c0a5b`; and dtest API with
> `dtest-api-0.0.16.jar`.
> The versions I put under `build/` directory are:
> dtest-4.0.9.jar, dtest-4.0.13.jar, dtest-4.1.4.jar, and dtest-5.1.jar.
> The command I'm running is:
> {code:java}
> $ ant test-jvm-dtest-some -Duse.jdk11=true
> -Dtest.name=org.apache.cassandra.distributed.upgrade.UpgradeTest {code}
> The error message I got was:
> {code:java}
> [junit-timeout] INFO [main] 2024-04-08 17:34:23,936 Versions.java:136
> - Looking for dtest jars in /Users/xxx/Documents/xxx/cassandra/build
> [junit-timeout] Found 4.0.13, 4.0.9
> [junit-timeout] Found 4.1.4
> [junit-timeout] Found 5.1
> [junit-timeout] - ---
> [junit-timeout] Testcase:
> simpleUpgradeWithNetworkAndGossipTest(org.apache.cassandra.distributed.upgrade.UpgradeTest)-_jdk11:
> Caused an ERROR
> [junit-timeout] null
> [junit-timeout] java.lang.NullPointerException
> [junit-timeout] at
> org.apache.cassandra.distributed.shared.Versions.getLatest(Versions.java:127)
> [junit-timeout] at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.upgradesTo(UpgradeTestBase.java:218)
> [junit-timeout] at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.upgradesToCurrentFrom(UpgradeTestBase.java:203)
> [junit-timeout] at
> org.apache.cassandra.distributed.upgrade.UpgradeTest.simpleUpgradeWithNetworkAndGossipTest(UpgradeTest.java:37)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [junit-timeout]
> [junit-timeout]
> [junit-timeout] Test org.apache.cassandra.distributed.upgrade.UpgradeTest
> FAILED
> {code}
> With some debugging, the version causing the null pointer is `5.0-alpha1`,
> but this version is not shown in `build/` directory and should not be tested
> if I understand correctly.
> h2. How to fix.
> There are two ways to fix this problem. One is to add a null pointer checker
> in `UpgradeTestBase#upgradesTo()`, and the other approach is to add the null
> pointer in `Versions#getLatest()`.
> I would love to provide a PR to fix this issue if you can tell me which fix
> looks better to you.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-19735) Cannot correctly create keyspace statement with replication during schemaChange
[
https://issues.apache.org/jira/browse/CASSANDRA-19735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862555#comment-17862555
]
ConfX edited comment on CASSANDRA-19735 at 7/2/24 6:29 PM:
---
Thank you for the clarification [~samt]
was (Author: JIRAUSER296392):
Thank you for the clarification [~samt]
> Cannot correctly create keyspace statement with replication during
> schemaChange
> ---
>
> Key: CASSANDRA-19735
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19735
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
>Reporter: ConfX
>Priority: Normal
> Fix For: 4.1.x, 5.0.x, 5.x
>
>
> h3. What happened
> A specific schema change for creating keyspace with replications failed
> during Cassandra upgrade testing, but can pass under Cassandra distributed
> testing (non-upgrade).
> h3. How to reproduce:
> Put the following test under
> {{{}cassandra/test/distributed/org/apache/cassandra/distributed/upgrade/{}}},
> and build dtest jars for any versions within [4.1.3, 5.0-alpha2].
> {code:java}
> package org.apache.cassandra.distributed.upgrade;
> public class demoUpgradeTest extends UpgradeTestBase
> @Test
> public void demoTest() throws Throwable {
> new TestCase()
> .nodes(1)
> .nodesToUpgrade(1)
> .withConfig(config -> config.with(NETWORK, GOSSIP,
> NATIVE_PROTOCOL))
> .upgradesToCurrentFrom(v41)
> .setup((cluster) -> {
> cluster.schemaChange(withKeyspace("CREATE KEYSPACE %s
> WITH replication = {'class': 'SimpleStrategy', 'replication_factor': 2}"));
> }).runAfterNodeUpgrade((cluster, node) -> {
> // let's do nothing here.
> }).run();
> }
> } {code}
> Run the test with
> {code:java}
> $ ant test-jvm-dtest-some-Duse.jdk11=true
> -Dtest.name=org.apache.cassandra.distributed.upgrade.demoUpgradeTest {code}
> You will see the following failure:
> {code:java}
> [junit-timeout] Testcase:
> demoTest(org.apache.cassandra.distributed.upgrade.demoUpgradeTest)-_jdk11:
> Caused an ERROR
> [junit-timeout] Cannot add existing keyspace "distributed_test_keyspace"
> [junit-timeout] org.apache.cassandra.exceptions.AlreadyExistsException:
> Cannot add existing keyspace "distributed_test_keyspace"
> [junit-timeout] at
> org.apache.cassandra.cql3.statements.schema.CreateKeyspaceStatement.apply(CreateKeyspaceStatement.java:78)
> [junit-timeout] at
> org.apache.cassandra.schema.DefaultSchemaUpdateHandler.apply(DefaultSchemaUpdateHandler.java:230)
> [junit-timeout] at
> org.apache.cassandra.schema.Schema.transform(Schema.java:597)
> [junit-timeout] at
> org.apache.cassandra.cql3.statements.schema.AlterSchemaStatement.execute(AlterSchemaStatement.java:114)
> [junit-timeout] at
> org.apache.cassandra.cql3.statements.schema.AlterSchemaStatement.execute(AlterSchemaStatement.java:60)
> [junit-timeout] at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:122)
> [junit-timeout] at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:103)
> [junit-timeout] at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:66)
> [junit-timeout] at
> org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61)
> [junit-timeout] at
> org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71)
> [junit-timeout] at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> [junit-timeout] at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> [junit-timeout] at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> [junit-timeout] at java.base/java.lang.Thread.run(Thread.java:829) {code}
> I have tested version pairs 4.1.3_4.1.4, 4.1.4_4.1.5, 4.1.5_5.0-alpha1, and
> 5.0-alpha1_5.0-alpha2. All of them have the same issue.
> I wrote a very similar test with Cassandra distributed test framework
> (non-upgrade test) as below:
> {code:java}
> package org.apache.cassandra.distributed.test.streaming;public class
> LCSStreamingKeepLevelTest extends TestBaseImpl
> {
> @Test
> public void demoTest() throws IOException
> {
> try (Cluster cluster = builder().withNodes(1)
> .withConfig(config -> config.with(NETWORK, GOSSIP,
> NATIVE_PROTOCOL))
> .start())
> {
> cluster.schemaChange(withKeyspace("CREATE KEYSPACE %s WITH
> replication = {'class': 'SimpleStrategy', 'replication_factor': 2}"))
[jira] [Commented] (CASSANDRA-19735) Cannot correctly create keyspace statement with replication during schemaChange
[
https://issues.apache.org/jira/browse/CASSANDRA-19735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862555#comment-17862555
]
ConfX commented on CASSANDRA-19735:
---
Thank you for the clarification [~samt]
> Cannot correctly create keyspace statement with replication during
> schemaChange
> ---
>
> Key: CASSANDRA-19735
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19735
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
>Reporter: ConfX
>Priority: Normal
> Fix For: 4.1.x, 5.0.x, 5.x
>
>
> h3. What happened
> A specific schema change for creating keyspace with replications failed
> during Cassandra upgrade testing, but can pass under Cassandra distributed
> testing (non-upgrade).
> h3. How to reproduce:
> Put the following test under
> {{{}cassandra/test/distributed/org/apache/cassandra/distributed/upgrade/{}}},
> and build dtest jars for any versions within [4.1.3, 5.0-alpha2].
> {code:java}
> package org.apache.cassandra.distributed.upgrade;
> public class demoUpgradeTest extends UpgradeTestBase
> @Test
> public void demoTest() throws Throwable {
> new TestCase()
> .nodes(1)
> .nodesToUpgrade(1)
> .withConfig(config -> config.with(NETWORK, GOSSIP,
> NATIVE_PROTOCOL))
> .upgradesToCurrentFrom(v41)
> .setup((cluster) -> {
> cluster.schemaChange(withKeyspace("CREATE KEYSPACE %s
> WITH replication = {'class': 'SimpleStrategy', 'replication_factor': 2}"));
> }).runAfterNodeUpgrade((cluster, node) -> {
> // let's do nothing here.
> }).run();
> }
> } {code}
> Run the test with
> {code:java}
> $ ant test-jvm-dtest-some-Duse.jdk11=true
> -Dtest.name=org.apache.cassandra.distributed.upgrade.demoUpgradeTest {code}
> You will see the following failure:
> {code:java}
> [junit-timeout] Testcase:
> demoTest(org.apache.cassandra.distributed.upgrade.demoUpgradeTest)-_jdk11:
> Caused an ERROR
> [junit-timeout] Cannot add existing keyspace "distributed_test_keyspace"
> [junit-timeout] org.apache.cassandra.exceptions.AlreadyExistsException:
> Cannot add existing keyspace "distributed_test_keyspace"
> [junit-timeout] at
> org.apache.cassandra.cql3.statements.schema.CreateKeyspaceStatement.apply(CreateKeyspaceStatement.java:78)
> [junit-timeout] at
> org.apache.cassandra.schema.DefaultSchemaUpdateHandler.apply(DefaultSchemaUpdateHandler.java:230)
> [junit-timeout] at
> org.apache.cassandra.schema.Schema.transform(Schema.java:597)
> [junit-timeout] at
> org.apache.cassandra.cql3.statements.schema.AlterSchemaStatement.execute(AlterSchemaStatement.java:114)
> [junit-timeout] at
> org.apache.cassandra.cql3.statements.schema.AlterSchemaStatement.execute(AlterSchemaStatement.java:60)
> [junit-timeout] at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:122)
> [junit-timeout] at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:103)
> [junit-timeout] at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:66)
> [junit-timeout] at
> org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61)
> [junit-timeout] at
> org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71)
> [junit-timeout] at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> [junit-timeout] at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> [junit-timeout] at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> [junit-timeout] at java.base/java.lang.Thread.run(Thread.java:829) {code}
> I have tested version pairs 4.1.3_4.1.4, 4.1.4_4.1.5, 4.1.5_5.0-alpha1, and
> 5.0-alpha1_5.0-alpha2. All of them have the same issue.
> I wrote a very similar test with Cassandra distributed test framework
> (non-upgrade test) as below:
> {code:java}
> package org.apache.cassandra.distributed.test.streaming;public class
> LCSStreamingKeepLevelTest extends TestBaseImpl
> {
> @Test
> public void demoTest() throws IOException
> {
> try (Cluster cluster = builder().withNodes(1)
> .withConfig(config -> config.with(NETWORK, GOSSIP,
> NATIVE_PROTOCOL))
> .start())
> {
> cluster.schemaChange(withKeyspace("CREATE KEYSPACE %s WITH
> replication = {'class': 'SimpleStrategy', 'replication_factor': 2}"));
> }
> }
> } {code}
> This distributed test would pass successfully without any issues.
>
> The expected
[jira] [Updated] (CASSANDRA-19739) Move bcprov-jdk18on-1.76.jar to build deps
[ https://issues.apache.org/jira/browse/CASSANDRA-19739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-19739: -- Test and Documentation Plan: ci Status: Patch Available (was: In Progress) > Move bcprov-jdk18on-1.76.jar to build deps > -- > > Key: CASSANDRA-19739 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19739 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.x > > > This came up after I bumped dependency-check version to 10.0.0 as suggested > in CASSANDRA-19738. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19744) Accord migration and interop correctness
[ https://issues.apache.org/jira/browse/CASSANDRA-19744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-19744: --- Labels: pull-request-available (was: ) > Accord migration and interop correctness > > > Key: CASSANDRA-19744 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19744 > Project: Cassandra > Issue Type: Bug > Components: Accord >Reporter: Ariel Weisberg >Assignee: Ariel Weisberg >Priority: Normal > Labels: pull-request-available > > There are several issues around splitting and retrying mutations, using the > original timestamp for batchlog/hints, batchlog/hint support in general, > running Accord barriers only against the ranges actually owned by Accord. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19739) Move bcprov-jdk18on-1.76.jar to build deps
[
https://issues.apache.org/jira/browse/CASSANDRA-19739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862532#comment-17862532
]
Stefan Miklosovic commented on CASSANDRA-19739:
---
[CASSANDRA-19739-5.0|https://github.com/instaclustr/cassandra/tree/CASSANDRA-19739-5.0]
{noformat}
java17_pre-commit_tests
✓ j17_build 4m 5s
✓ j17_cqlsh_dtests_py311 6m 26s
✓ j17_cqlsh_dtests_py311_vnode 6m 11s
✓ j17_cqlsh_dtests_py385m 57s
✓ j17_cqlsh_dtests_py38_vnode 6m 15s
✓ j17_cqlshlib_cython_tests9m 36s
✓ j17_cqlshlib_tests 6m 38s
✓ j17_dtests 34m 56s
✓ j17_dtests_latest 32m 43s
✓ j17_dtests_vnode32m 54s
✓ j17_jvm_dtests 26m 18s
✓ j17_jvm_dtests_latest_vnode 15m 30s
✓ j17_unit_tests 14m 19s
✓ j17_utests_latest 14m 55s
✓ j17_utests_oa 14m 13s
{noformat}
[java17_pre-commit_tests|https://app.circleci.com/pipelines/github/instaclustr/cassandra/4445/workflows/59b77b46-5da0-40e7-bd81-5ec23c853a6d]
> Move bcprov-jdk18on-1.76.jar to build deps
> --
>
> Key: CASSANDRA-19739
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19739
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 5.x
>
>
> This came up after I bumped dependency-check version to 10.0.0 as suggested
> in CASSANDRA-19738.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19739) Move bcprov-jdk18on-1.76.jar to build deps
[ https://issues.apache.org/jira/browse/CASSANDRA-19739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-19739: -- Summary: Move bcprov-jdk18on-1.76.jar to build deps (was: Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171, CVE-2024-29857, CVE-2024-34447) > Move bcprov-jdk18on-1.76.jar to build deps > -- > > Key: CASSANDRA-19739 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19739 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.x > > > This came up after I bumped dependency-check version to 10.0.0 as suggested > in CASSANDRA-19738. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
Re: [PR] Fix tests failing on Jenkins [cassandra-java-driver]
absurdfarce commented on code in PR #1939:
URL:
https://github.com/apache/cassandra-java-driver/pull/1939#discussion_r1662902550
##
integration-tests/src/test/java/com/datastax/oss/driver/mapper/DeleteIT.java:
##
@@ -56,8 +56,8 @@
// Do not run LWT tests in parallel because they may interfere. Tests operate
on the same row.
@BackendRequirement(
type = BackendType.CASSANDRA,
-minInclusive = "3.0",
-description = ">= in WHERE clause not supported in legacy versions")
+minInclusive = "3.4",
+description = ">= in WHERE clause, and SASI indexes are not supported in
legacy versions")
Review Comment:
I'd say make it even easier: just overload createStatements() with
requiresSasiIndex as false in the default case:
```java
protected static List createStatements(BaseCcmRule ccmRule) {
return createStatements(ccmRule, false);
}
```
Unless I'm missing something that means you only need to modify
SelectCustomWhereClauseIT since it's the only one that actually passes in
"true" for the SASI create argument.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19400) IndexStatusManager needs to prioritize SUCCESS over UNKNOWN states to maximize availability
[
https://issues.apache.org/jira/browse/CASSANDRA-19400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862516#comment-17862516
]
Caleb Rackliffe commented on CASSANDRA-19400:
-
[~arkn98] Hi there! Just checking in on this. Let me know if you need any
further help or to reassign...
> IndexStatusManager needs to prioritize SUCCESS over UNKNOWN states to
> maximize availability
> ---
>
> Key: CASSANDRA-19400
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19400
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/SAI
>Reporter: Caleb Rackliffe
>Assignee: Arun Ganesh
>Priority: Low
> Fix For: 5.0.x, 5.x
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {{IndexStatusManager}} is responsible for knowing what SAI indexes are
> queryable across the ring, endpoint by endpoint. There are two statuses that
> SAI treats as queryable, but it should not treat them equally.
> {{BUILD_SUCCEEDED}} means the index is definitely available and should be
> able to serve queries without issue. {{UNKNOWN}} indicates that the status of
> the index hasn’t propagated yet to this coordinator. It may be just fine, or
> it may not be. If it isn’t a query will not return incorrect results, but it
> will fail. If there are enough {{BUILD_SUCCEEDED}} replicas, we should ignore
> {{UNKNOWN}} replicas and maximize availability. If the UNKNOWN replica is
> going to become {{BUILD_SUCCEEDED}} shortly, it will happily start taking
> requests at that point and spread the load. If not, we’ll avoid futile
> attempts to query it too early.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-137) Bump AWS SDK v2 version to the latest
[ https://issues.apache.org/jira/browse/CASSANDRASC-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-137: --- Labels: pull-request-available (was: ) > Bump AWS SDK v2 version to the latest > - > > Key: CASSANDRASC-137 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-137 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Labels: pull-request-available > Fix For: 1.0 > > > The latest AWS SDK v2 version is now 2.26.10, whereas the version used in > sidecar is 2.20.43. There are many improvement and bug fixes between the > version. See changes log > https://github.com/aws/aws-sdk-java-v2/tree/master/changelogs -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[PR] Fix tests failing on Jenkins [cassandra-java-driver]
lukasz-antoniak opened a new pull request, #1939: URL: https://github.com/apache/cassandra-java-driver/pull/1939 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
Re: [PR] Add ExecutionInfo to RequestTracker methods [cassandra-java-driver]
lukasz-antoniak commented on PR #1640: URL: https://github.com/apache/cassandra-java-driver/pull/1640#issuecomment-2191509703 @ajweave, @tolbertam, I have tried to solve my [comments](https://github.com/apache/cassandra-java-driver/pull/1640#issuecomment-2135352720) and submitted PR to Andrew's fork: https://github.com/ajweave/java-driver/pull/1. Could you please review the changes and comment? I am not enforcing any of those, just trying cleanup already existing code a little. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19704) UnsupportedOperationException is thrown when no space for LCS
[
https://issues.apache.org/jira/browse/CASSANDRA-19704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-19704:
Status: Ready to Commit (was: Review In Progress)
[~jasonstack] Partly because I'm going to be out until next Monday, I'm going
to just move forward to commit the {{level == 0}} version of the fix. We may
miss an opportunity to compact some expired SSTables, but that can be improved
later.
> UnsupportedOperationException is thrown when no space for LCS
> -
>
> Key: CASSANDRA-19704
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19704
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction/LCS
>Reporter: Zhao Yang
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
> Attachments: ci_summary-1.html, ci_summary-2.html, ci_summary-3.html,
> ci_summary.html
>
>
> In {{CompactionTask#buildCompactionCandidatesForAvailableDiskSpace}} with
> LCS, if node has limited disk space and can't remove any sstable from L0 or
> L1 in {{{}LeveledCompactionTask#reduceScopeForLimitedSpace{}}},
> {{LeveledCompactionTask#partialCompactionsAcceptable}} will throw
> {{UnsupportedOperationException}}.
> We should handle {{LeveledCompactionTask#partialCompactionsAcceptable}} more
> gracefully with {{return level <= 1}} or simply {{true}} since
> {{reduceScopeForLimitedSpace}} only removes sstable from L0 or L1.
> Related https://issues.apache.org/jira/browse/CASSANDRA-17272
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19704) UnsupportedOperationException is thrown when no space for LCS
[
https://issues.apache.org/jira/browse/CASSANDRA-19704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-19704:
Reviewers: Marcus Eriksson, Zhao Yang (was: Zhao Yang)
> UnsupportedOperationException is thrown when no space for LCS
> -
>
> Key: CASSANDRA-19704
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19704
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction/LCS
>Reporter: Zhao Yang
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
> Attachments: ci_summary-1.html, ci_summary-2.html, ci_summary-3.html,
> ci_summary.html
>
>
> In {{CompactionTask#buildCompactionCandidatesForAvailableDiskSpace}} with
> LCS, if node has limited disk space and can't remove any sstable from L0 or
> L1 in {{{}LeveledCompactionTask#reduceScopeForLimitedSpace{}}},
> {{LeveledCompactionTask#partialCompactionsAcceptable}} will throw
> {{UnsupportedOperationException}}.
> We should handle {{LeveledCompactionTask#partialCompactionsAcceptable}} more
> gracefully with {{return level <= 1}} or simply {{true}} since
> {{reduceScopeForLimitedSpace}} only removes sstable from L0 or L1.
> Related https://issues.apache.org/jira/browse/CASSANDRA-17272
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19668) SIGSEGV originating in Paxos V2 Scheduled Task
[
https://issues.apache.org/jira/browse/CASSANDRA-19668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862494#comment-17862494
]
Jeremiah Jordan commented on CASSANDRA-19668:
-
Thanks for finding and fixing this. Should we add an in tree test to ensure
this can’t regress?
> SIGSEGV originating in Paxos V2 Scheduled Task
> --
>
> Key: CASSANDRA-19668
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19668
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Lightweight Transactions
>Reporter: Jon Haddad
>Assignee: Jon Haddad
>Priority: Urgent
> Fix For: 4.1.6, 5.0-beta2, 5.0, 5.1
>
> Attachments: ci_summar-5.0.html, ci_summary-4.1.html,
> ci_summary-trunk.html
>
>
> I haven't gotten to the root cause of this yet. Several 4.1 nodes have
> crashed in in production. I'm not sure if this is related to Paxos v2 or
> not, but it is enabled. offheap_objects also enabled.
> I'm not sure if this affects 5.0, yet.
> Most of the crashes don't have a stacktrace - they only reference this
> {noformat}
> Stack: [0x7fabf4c34000,0x7fabf4d34000], sp=0x7fabf4d31f00, free
> space=1015k
> Native frames: (J=compiled Java code, A=aot compiled Java code,
> j=interpreted, Vv=VM code, C=native code)
> v ~StubRoutines::jint_disjoint_arraycopy
> {noformat}
> They all are in the {{ScheduledTasks}} thread.
> However, one node does have this in the crash log:
> {noformat}
> --- T H R E A D ---
> Current thread (0x78b375eac800): JavaThread "ScheduledTasks:1" daemon
> [_thread_in_Java, id=151791, stack(0x78b34b78,0x78b34b88)]
> Stack: [0x78b34b78,0x78b34b88], sp=0x78b34b87c350, free
> space=1008k
> Native frames: (J=compiled Java code, A=aot compiled Java code,
> j=interpreted, Vv=VM code, C=native code)
> J 29467 c2
> org.apache.cassandra.db.rows.AbstractCell.clone(Lorg/apache/cassandra/utils/memory/ByteBufferCloner;)Lorg/apache/cassandra/db/rows/Cell;
> (50 bytes) @ 0x78b3dd40a42f [0x78b3dd409de0+0x064f]
> J 17669 c2
> org.apache.cassandra.db.rows.Cell.clone(Lorg/apache/cassandra/utils/memory/Cloner;)Lorg/apache/cassandra/db/rows/ColumnData;
> (6 bytes) @ 0x78b3dc54edc0 [0x78b3dc54ed40+0x0080]
> J 17816 c2
> org.apache.cassandra.db.rows.BTreeRow$$Lambda$845.apply(Ljava/lang/Object;)Ljava/lang/Object;
> (12 bytes) @ 0x78b3dbed01a4 [0x78b3dbed0120+0x0084]
> J 17828 c2
> org.apache.cassandra.utils.btree.BTree.transform([Ljava/lang/Object;Ljava/util/function/Function;)[Ljava/lang/Object;
> (194 bytes) @ 0x78b3dc5f35f0 [0x78b3dc5f34a0+0x0150]
> J 35096 c2
> org.apache.cassandra.db.rows.BTreeRow.clone(Lorg/apache/cassandra/utils/memory/Cloner;)Lorg/apache/cassandra/db/rows/Row;
> (37 bytes) @ 0x78b3dda9111c [0x78b3dda90fe0+0x013c]
> J 30500 c2
> org.apache.cassandra.utils.memory.EnsureOnHeap$CloneToHeap.applyToRow(Lorg/apache/cassandra/db/rows/Row;)Lorg/apache/cassandra/db/rows/Row;
> (16 bytes) @ 0x78b3dd59b91c [0x78b3dd59b8c0+0x005c]
> J 26498 c2 org.apache.cassandra.db.transform.BaseRows.hasNext()Z (215 bytes)
> @ 0x78b3dcf1c454 [0x78b3dcf1c180+0x02d4]
> J 30775 c2
> org.apache.cassandra.utils.MergeIterator$OneToOne.computeNext()Ljava/lang/Object;
> (49 bytes) @ 0x78b3dc789020 [0x78b3dc788fc0+0x0060]
> J 9082 c2 org.apache.cassandra.utils.AbstractIterator.hasNext()Z (80 bytes) @
> 0x78b3dbb3c544 [0x78b3dbb3c440+0x0104]
> J 35593 c2
> org.apache.cassandra.service.paxos.uncommitted.PaxosRows$PaxosMemtableToKeyStateIterator.computeNext()Lorg/apache/cassandra/service/paxos/uncommitted/PaxosKeyState;
> (126 bytes) @ 0x78b3dc7ceeec [0x78b3dc7cee20+0x00cc]
> J 35591 c2
> org.apache.cassandra.service.paxos.uncommitted.PaxosRows$PaxosMemtableToKeyStateIterator.computeNext()Ljava/lang/Object;
> (5 bytes) @ 0x78b3dc7d09e4 [0x78b3dc7d09a0+0x0044]
> J 9082 c2 org.apache.cassandra.utils.AbstractIterator.hasNext()Z (80 bytes) @
> 0x78b3dbb3c544 [0x78b3dbb3c440+0x0104]
> J 34146 c2
> com.google.common.collect.Iterators.addAll(Ljava/util/Collection;Ljava/util/Iterator;)Z
> (41 bytes) @ 0x78b3dd9197e8 [0x78b3dd919680+0x0168]
> J 38256 c1
> org.apache.cassandra.service.paxos.uncommitted.PaxosRows.toIterator(Lorg/apache/cassandra/db/partitions/UnfilteredPartitionIterator;Lorg/apache/cassandra/schema/TableId;Z)Lorg/apache/cassandra/utils/CloseableIterator;
> (49 bytes) @ 0x78b3d6b677ac [0x78b3d6b672e0+0x04cc]
> J 34823 c1
> org.apache.cassandra.service.paxos.uncommitted.PaxosUncommittedIndex.repair
(cassandra-java-driver) branch 4.x updated (6d7b1950a -> d0a1e44a4)
This is an automated email from the ASF dual-hosted git repository. absurdfarce pushed a change to branch 4.x in repository https://gitbox.apache.org/repos/asf/cassandra-java-driver.git omit 6d7b1950a Limit calls to Conversions.resolveExecutionProfile new d0a1e44a4 Limit calls to Conversions.resolveExecutionProfile This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (6d7b1950a) \ N -- N -- N refs/heads/4.x (d0a1e44a4) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra-java-driver) 01/01: Limit calls to Conversions.resolveExecutionProfile
This is an automated email from the ASF dual-hosted git repository.
absurdfarce pushed a commit to branch 4.x
in repository https://gitbox.apache.org/repos/asf/cassandra-java-driver.git
commit d0a1e44a4415c7a0489f8c35ee9ce49e20d7bc61
Author: Benoit Tellier
AuthorDate: Sun Jan 22 13:58:19 2023 +0700
Limit calls to Conversions.resolveExecutionProfile
Those repeated calls account for a non-negligible portion of my application
CPU (0.6%) and can definitly be a final field so that it gets resolved only
once per CqlRequestHandler.
patch by Benoit Tellier; reviewed by Andy Tolbert, and Bret McGuire
reference: https://github.com/apache/cassandra-java-driver/pull/1623
---
.../continuous/ContinuousRequestHandlerBase.java | 15 +++---
.../internal/core/graph/GraphRequestHandler.java | 15 +++---
.../oss/driver/internal/core/cql/Conversions.java | 38 +--
.../internal/core/cql/CqlPrepareHandler.java | 11 +++--
.../internal/core/cql/CqlRequestHandler.java | 54 --
5 files changed, 75 insertions(+), 58 deletions(-)
diff --git
a/core/src/main/java/com/datastax/dse/driver/internal/core/cql/continuous/ContinuousRequestHandlerBase.java
b/core/src/main/java/com/datastax/dse/driver/internal/core/cql/continuous/ContinuousRequestHandlerBase.java
index 44df3b3a0..9a7be3447 100644
---
a/core/src/main/java/com/datastax/dse/driver/internal/core/cql/continuous/ContinuousRequestHandlerBase.java
+++
b/core/src/main/java/com/datastax/dse/driver/internal/core/cql/continuous/ContinuousRequestHandlerBase.java
@@ -648,12 +648,13 @@ public abstract class
ContinuousRequestHandlerBase= 0) {
scheduleSpeculativeExecution(nextExecution, nextDelay);
@@ -787,12 +788,12 @@ public abstract class
ContinuousRequestHandlerBase statement, Throwable error, Node
node, int execution) {
-DriverExecutionProfile executionProfile =
-Conversions.resolveExecutionProfile(statement, context);
if (error instanceof DriverException) {
((DriverException) error)
.setExecutionInfo(
@@ -475,7 +460,6 @@ public class CqlRequestHandler implements Throttled {
private final long nodeStartTimeNanos = System.nanoTime();
private final Statement statement;
-private final DriverExecutionProfile executionProfile;
private final Node node;
private final Queue queryPlan;
private final DriverChannel channel;
@@ -505,7 +489,6 @@ public class CqlRequestHandler implements Throttled {
this.retryCount = retryCount;
this.scheduleNextExecution = scheduleNextExecution;
this.logPrefix = logPrefix + "|" + execution;
- this.executionProfile = Conversions.resolveExecutionProfile(statement,
context);
}
// this gets invoked once the write completes.
@@ -544,12 +527,13 @@ public class CqlRequestHandler implements Throttled {
cancel();
} else {
inFlightCallbacks.add(this);
- if (scheduleNextExecution &&
Conversions.resolveIdempotence(statement, context)) {
+ if (scheduleNextExecution
+ && Conversions.resolveIdempotence(statement, executionProfile)) {
int nextExecution = execution + 1;
long nextDelay;
try {
nextDelay =
- Conversions.resolveSpeculativeExecutionPolicy(statement,
context)
+ Conversions.resolveSpeculativeExecutionPolicy(context,
executionProfile)
.nextExecution(node, keyspace, statement, nextExecution);
} catch (Throwable cause) {
// This is a bug in the policy, but not fatal since we have at
least one other
@@ -697,7 +681,7 @@ public class CqlRequestHandler implements Throttled {
true,
reprepareMessage,
repreparePayload.customPayload,
-Conversions.resolveRequestTimeout(statement, context),
+Conversions.resolveRequestTimeout(statement, executionProfile),
throttler,
sessionMetricUpdater,
logPrefix);
@@ -767,7 +751,7 @@ public class CqlRequestHandler implements Throttled {
trackNodeError(node, error, NANOTIME_NOT_MEASURED_YET);
setFinalError(statement, error, node, execution);
} else {
-RetryPolicy retryPolicy = Conversions.resolveRetryPolicy(statement,
context);
+RetryPolicy retryPolicy = Conversions.resolveRetryPolicy(context,
executionProfile);
RetryVerdict verdict;
if (error instanceof ReadTimeoutException) {
ReadTimeoutException readTimeout = (ReadTimeoutException) error;
@@ -788,7 +772,7 @@ public class CqlRequestHandler implements Throttled {
} else if (error instanceof WriteTimeoutException) {
WriteTimeoutException writeTimeout = (WriteTimeoutException) error;
verdict =
- Conversions.resolveIdempotence(statement, context)
+
(cassandra-java-driver) branch 4.x updated: Limit calls to Conversions.resolveExecutionProfile
This is an automated email from the ASF dual-hosted git repository.
absurdfarce pushed a commit to branch 4.x
in repository https://gitbox.apache.org/repos/asf/cassandra-java-driver.git
The following commit(s) were added to refs/heads/4.x by this push:
new 6d7b1950a Limit calls to Conversions.resolveExecutionProfile
6d7b1950a is described below
commit 6d7b1950a5430a73ff0662056b9e9a7e2b3701a9
Author: Benoit Tellier
AuthorDate: Sun Jan 22 13:58:19 2023 +0700
Limit calls to Conversions.resolveExecutionProfile
Those repeated calls account for a non-negligible portion of my application
CPU (0.6%) and can definitly be a final field so that it gets resolved only
once per CqlRequestHandler.
---
.../continuous/ContinuousRequestHandlerBase.java | 15 +++---
.../internal/core/graph/GraphRequestHandler.java | 15 +++---
.../oss/driver/internal/core/cql/Conversions.java | 38 +--
.../internal/core/cql/CqlPrepareHandler.java | 11 +++--
.../internal/core/cql/CqlRequestHandler.java | 54 --
5 files changed, 75 insertions(+), 58 deletions(-)
diff --git
a/core/src/main/java/com/datastax/dse/driver/internal/core/cql/continuous/ContinuousRequestHandlerBase.java
b/core/src/main/java/com/datastax/dse/driver/internal/core/cql/continuous/ContinuousRequestHandlerBase.java
index 44df3b3a0..9a7be3447 100644
---
a/core/src/main/java/com/datastax/dse/driver/internal/core/cql/continuous/ContinuousRequestHandlerBase.java
+++
b/core/src/main/java/com/datastax/dse/driver/internal/core/cql/continuous/ContinuousRequestHandlerBase.java
@@ -648,12 +648,13 @@ public abstract class
ContinuousRequestHandlerBase= 0) {
scheduleSpeculativeExecution(nextExecution, nextDelay);
@@ -787,12 +788,12 @@ public abstract class
ContinuousRequestHandlerBase statement, Throwable error, Node
node, int execution) {
-DriverExecutionProfile executionProfile =
-Conversions.resolveExecutionProfile(statement, context);
if (error instanceof DriverException) {
((DriverException) error)
.setExecutionInfo(
@@ -475,7 +460,6 @@ public class CqlRequestHandler implements Throttled {
private final long nodeStartTimeNanos = System.nanoTime();
private final Statement statement;
-private final DriverExecutionProfile executionProfile;
private final Node node;
private final Queue queryPlan;
private final DriverChannel channel;
@@ -505,7 +489,6 @@ public class CqlRequestHandler implements Throttled {
this.retryCount = retryCount;
this.scheduleNextExecution = scheduleNextExecution;
this.logPrefix = logPrefix + "|" + execution;
- this.executionProfile = Conversions.resolveExecutionProfile(statement,
context);
}
// this gets invoked once the write completes.
@@ -544,12 +527,13 @@ public class CqlRequestHandler implements Throttled {
cancel();
} else {
inFlightCallbacks.add(this);
- if (scheduleNextExecution &&
Conversions.resolveIdempotence(statement, context)) {
+ if (scheduleNextExecution
+ && Conversions.resolveIdempotence(statement, executionProfile)) {
int nextExecution = execution + 1;
long nextDelay;
try {
nextDelay =
- Conversions.resolveSpeculativeExecutionPolicy(statement,
context)
+ Conversions.resolveSpeculativeExecutionPolicy(context,
executionProfile)
.nextExecution(node, keyspace, statement, nextExecution);
} catch (Throwable cause) {
// This is a bug in the policy, but not fatal since we have at
least one other
@@ -697,7 +681,7 @@ public class CqlRequestHandler implements Throttled {
true,
reprepareMessage,
repreparePayload.customPayload,
-Conversions.resolveRequestTimeout(statement, context),
+Conversions.resolveRequestTimeout(statement, executionProfile),
throttler,
sessionMetricUpdater,
logPrefix);
@@ -767,7 +751,7 @@ public class CqlRequestHandler implements Throttled {
trackNodeError(node, error, NANOTIME_NOT_MEASURED_YET);
setFinalError(statement, error, node, execution);
} else {
-RetryPolicy retryPolicy = Conversions.resolveRetryPolicy(statement,
context);
+RetryPolicy retryPolicy = Conversions.resolveRetryPolicy(context,
executionProfile);
RetryVerdict verdict;
if (error instanceof ReadTimeoutException) {
ReadTimeoutException readTimeout = (ReadTimeoutException) error;
@@ -788,7 +772,7 @@ public class CqlRequestHandler implements Throttled {
} else if (error instanceof WriteTimeoutException) {
WriteTimeoutException writeTimeout = (WriteTimeoutException) error;
verdict =
- Conversions.resolveIdempotence(state
[jira] [Updated] (CASSANDRA-19419) Non-transactional schema updates can interfere with Accord transaction execution
[ https://issues.apache.org/jira/browse/CASSANDRA-19419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ariel Weisberg updated CASSANDRA-19419: --- Summary: Non-transactional schema updates can interfere with Accord transaction execution (was: Non-transactional schema updates can interfere with Accord transaction execuion) > Non-transactional schema updates can interfere with Accord transaction > execution > > > Key: CASSANDRA-19419 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19419 > Project: Cassandra > Issue Type: Bug >Reporter: Ariel Weisberg >Priority: Normal > > While Accord can handle topology changes correctly it can’t handle > non-transaction schema updates because those execute outside of Accord. When > Accord tries to execute a transaction against the schema in the epoch the > transaction is supposed to execute in then it is possible for different nodes > to see different schemas when reading or writing data as part of a > transaction. > Dropping a needed a column or table is the most likely issue as we don't > support altering column types. > Because commit is async it is possible for a table or to be dropped before > the writes can be propagated after it was acknowledged instead of signaling > an error. While the table was dropped it's possible the client needed the > error to know that the request was processed improperly or that it needed to > take some other action client side. > Or add table where the original coordinator can't read the table, but the > recovery coordinator can and might apply different results to different > replicas. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19744) Accord migration and interop correctness
Ariel Weisberg created CASSANDRA-19744: -- Summary: Accord migration and interop correctness Key: CASSANDRA-19744 URL: https://issues.apache.org/jira/browse/CASSANDRA-19744 Project: Cassandra Issue Type: Bug Components: Accord Reporter: Ariel Weisberg Assignee: Ariel Weisberg There are several issues around splitting and retrying mutations, using the original timestamp for batchlog/hints, batchlog/hint support in general, running Accord barriers only against the ranges actually owned by Accord. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19743) add keyspace name to exception message in StorageService#getEffectiveOwnership for better debugging
[
https://issues.apache.org/jira/browse/CASSANDRA-19743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ling Mao updated CASSANDRA-19743:
-
Description:
{code:java}
➜ bin ./nodetool status
Datacenter: datacenter1
===
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens Owns Host ID Rack
UN 127.0.0.2 235.8 KiB 16 ? f581f6fa-7192-40ab-8665-8ff270fa3fd3 rack2
UN 127.0.0.1 198.32 KiB 16 ? 00b387d8-f269-4780-878d-17648be2f218 rack1
UN 127.0.0.3 198.59 KiB 16 ? a2398380-951a-464c-a8bb-6418831715ad rack3
Datacenter: datacenter2
===
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens Owns Host ID Rack
UN 127.0.0.11 148.47 KiB 16 ? 661da11a-08e4-4082-81e0-c33328669e8d rack1
UN 127.0.0.12 187.26 KiB 16 ? a12fe27b-fc98-4a23-9d8c-843f58562b8b rack1
Note: Non-system keyspaces don't have the same replication settings, effective
ownership information is meaningless
{code}
I have 5 nodes and over 20 keyspaces. It's difficult for me to identify which
one has different replication settings without going through each one
individually, as stated in the warning note.
was:getEffectiveOwnership
> add keyspace name to exception message in
> StorageService#getEffectiveOwnership for better debugging
> ---
>
> Key: CASSANDRA-19743
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19743
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Ling Mao
>Assignee: Ling Mao
>Priority: Low
> Fix For: 5.1
>
>
>
>
> {code:java}
> ➜ bin ./nodetool status
> Datacenter: datacenter1
> ===
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> -- Address Load Tokens Owns Host ID Rack
> UN 127.0.0.2 235.8 KiB 16 ? f581f6fa-7192-40ab-8665-8ff270fa3fd3 rack2
> UN 127.0.0.1 198.32 KiB 16 ? 00b387d8-f269-4780-878d-17648be2f218 rack1
> UN 127.0.0.3 198.59 KiB 16 ? a2398380-951a-464c-a8bb-6418831715ad rack3
>
> Datacenter: datacenter2
> ===
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> -- Address Load Tokens Owns Host ID Rack
> UN 127.0.0.11 148.47 KiB 16 ? 661da11a-08e4-4082-81e0-c33328669e8d rack1
> UN 127.0.0.12 187.26 KiB 16 ? a12fe27b-fc98-4a23-9d8c-843f58562b8b rack1
>
> Note: Non-system keyspaces don't have the same replication settings,
> effective ownership information is meaningless
> {code}
> I have 5 nodes and over 20 keyspaces. It's difficult for me to identify which
> one has different replication settings without going through each one
> individually, as stated in the warning note.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19743) add keyspace name to exception message in StorageService#getEffectiveOwnership for better debugging
[ https://issues.apache.org/jira/browse/CASSANDRA-19743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ling Mao updated CASSANDRA-19743: - Fix Version/s: 5.1 > add keyspace name to exception message in > StorageService#getEffectiveOwnership for better debugging > --- > > Key: CASSANDRA-19743 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19743 > Project: Cassandra > Issue Type: Improvement >Reporter: Ling Mao >Priority: Normal > Fix For: 5.1 > > > getEffectiveOwnership -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19743) add keyspace name to exception message in StorageService#getEffectiveOwnership for better debugging
[ https://issues.apache.org/jira/browse/CASSANDRA-19743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ling Mao updated CASSANDRA-19743: - Summary: add keyspace name to exception message in StorageService#getEffectiveOwnership for better debugging (was: getEffectiveOwnership) > add keyspace name to exception message in > StorageService#getEffectiveOwnership for better debugging > --- > > Key: CASSANDRA-19743 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19743 > Project: Cassandra > Issue Type: Improvement >Reporter: Ling Mao >Priority: Normal > > getEffectiveOwnership -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19743) getEffectiveOwnership
Ling Mao created CASSANDRA-19743: Summary: getEffectiveOwnership Key: CASSANDRA-19743 URL: https://issues.apache.org/jira/browse/CASSANDRA-19743 Project: Cassandra Issue Type: Improvement Reporter: Ling Mao getEffectiveOwnership -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19739) Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171, CVE-2024-29857, CVE-2024-34447
[ https://issues.apache.org/jira/browse/CASSANDRA-19739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-19739: -- Fix Version/s: (was: 5.0-rc) > Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171, > CVE-2024-29857, CVE-2024-34447 > --- > > Key: CASSANDRA-19739 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19739 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.x > > > This came up after I bumped dependency-check version to 10.0.0 as suggested > in CASSANDRA-19738. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19739) Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171, CVE-2024-29857, CVE-2024-34447
[ https://issues.apache.org/jira/browse/CASSANDRA-19739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862429#comment-17862429 ] Stefan Miklosovic commented on CASSANDRA-19739: --- I do not think we need this in prod, it just fails on in SSLFactoryTest static block. "No provider succeeded to generate a self-signed certificate. See debug log for the root cause." > Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171, > CVE-2024-29857, CVE-2024-34447 > --- > > Key: CASSANDRA-19739 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19739 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.0-rc, 5.x > > > This came up after I bumped dependency-check version to 10.0.0 as suggested > in CASSANDRA-19738. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-19739) Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171, CVE-2024-29857, CVE-2024-34447
[ https://issues.apache.org/jira/browse/CASSANDRA-19739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862409#comment-17862409 ] Stefan Miklosovic edited comment on CASSANDRA-19739 at 7/2/24 12:07 PM: These dependencies were in cassandra-deps-tempalate which added them to the tarball. When added to cassandra-build-deps-template.xml, they are not in the tarball and it fixes Java 17 test above too. I enumerated all of them in parent-pom-template.xml and updated to 1.78. If we do not need this in the release tarball but just for the sake of tests, we can just move it to cassandra-build-deps-template.xml and be done with it. [~jlewandowski] [~edimitrova] do we need this in the release tarball? was (Author: smiklosovic): These dependencies were in cassandra-deps-tempalate which added them to a tarball. When added to cassandra-build-deps-template.xml. I enumerated all of them in parent-pom-template.xml and updated to 1.78. If we do not need this in the release tarball but just for the sake of tests, we can just move it to cassandra-build-deps-template.xml and be done with it. This fixes failed Java 17 test above too. [~jlewandowski] [~edimitrova] do we need this in the release tarball? > Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171, > CVE-2024-29857, CVE-2024-34447 > --- > > Key: CASSANDRA-19739 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19739 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.0-rc, 5.x > > > This came up after I bumped dependency-check version to 10.0.0 as suggested > in CASSANDRA-19738. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19739) Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171, CVE-2024-29857, CVE-2024-34447
[ https://issues.apache.org/jira/browse/CASSANDRA-19739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862409#comment-17862409 ] Stefan Miklosovic commented on CASSANDRA-19739: --- These dependencies were in cassandra-deps-tempalate which added them to a tarball. When added to cassandra-build-deps-template.xml. I enumerated all of them in parent-pom-template.xml and updated to 1.78. If we do not need this in the release tarball but just for the sake of tests, we can just move it to cassandra-build-deps-template.xml and be done with it. [~jlewandowski] [~edimitrova] do we need this in the release tarball? > Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171, > CVE-2024-29857, CVE-2024-34447 > --- > > Key: CASSANDRA-19739 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19739 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.0-rc, 5.x > > > This came up after I bumped dependency-check version to 10.0.0 as suggested > in CASSANDRA-19738. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19739) Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171, CVE-2024-29857, CVE-2024-34447
[ https://issues.apache.org/jira/browse/CASSANDRA-19739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862411#comment-17862411 ] Stefan Miklosovic commented on CASSANDRA-19739: --- https://github.com/apache/cassandra/pull/3393/files > Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171, > CVE-2024-29857, CVE-2024-34447 > --- > > Key: CASSANDRA-19739 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19739 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.0-rc, 5.x > > > This came up after I bumped dependency-check version to 10.0.0 as suggested > in CASSANDRA-19738. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-19739) Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171, CVE-2024-29857, CVE-2024-34447
[ https://issues.apache.org/jira/browse/CASSANDRA-19739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862409#comment-17862409 ] Stefan Miklosovic edited comment on CASSANDRA-19739 at 7/2/24 12:06 PM: These dependencies were in cassandra-deps-tempalate which added them to a tarball. When added to cassandra-build-deps-template.xml. I enumerated all of them in parent-pom-template.xml and updated to 1.78. If we do not need this in the release tarball but just for the sake of tests, we can just move it to cassandra-build-deps-template.xml and be done with it. This fixes failed Java 17 test above too. [~jlewandowski] [~edimitrova] do we need this in the release tarball? was (Author: smiklosovic): These dependencies were in cassandra-deps-tempalate which added them to a tarball. When added to cassandra-build-deps-template.xml. I enumerated all of them in parent-pom-template.xml and updated to 1.78. If we do not need this in the release tarball but just for the sake of tests, we can just move it to cassandra-build-deps-template.xml and be done with it. [~jlewandowski] [~edimitrova] do we need this in the release tarball? > Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171, > CVE-2024-29857, CVE-2024-34447 > --- > > Key: CASSANDRA-19739 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19739 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.0-rc, 5.x > > > This came up after I bumped dependency-check version to 10.0.0 as suggested > in CASSANDRA-19738. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19739) Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171, CVE-2024-29857, CVE-2024-34447
[ https://issues.apache.org/jira/browse/CASSANDRA-19739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862400#comment-17862400 ] Stefan Miklosovic commented on CASSANDRA-19739: --- https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-30172 https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-30171 https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-29857 https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-34447 > Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171, > CVE-2024-29857, CVE-2024-34447 > --- > > Key: CASSANDRA-19739 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19739 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.0-rc, 5.x > > > This came up after I bumped dependency-check version to 10.0.0 as suggested > in CASSANDRA-19738. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
svn commit: r70096 - in /dev/cassandra/5.0-rc1/redhat: ./ noboolean/ noboolean/repodata/ repodata/
Author: mck Date: Tue Jul 2 11:10:44 2024 New Revision: 70096 Log: staging cassandra rpm packages for 5.0-rc1 Added: dev/cassandra/5.0-rc1/redhat/ dev/cassandra/5.0-rc1/redhat/cassandra-5.0~rc1-1.noarch.rpm (with props) dev/cassandra/5.0-rc1/redhat/cassandra-5.0~rc1-1.src.rpm (with props) dev/cassandra/5.0-rc1/redhat/cassandra-tools-5.0~rc1-1.noarch.rpm (with props) dev/cassandra/5.0-rc1/redhat/noboolean/ dev/cassandra/5.0-rc1/redhat/noboolean/cassandra-5.0~rc1-1.noarch.rpm (with props) dev/cassandra/5.0-rc1/redhat/noboolean/cassandra-5.0~rc1-1.src.rpm (with props) dev/cassandra/5.0-rc1/redhat/noboolean/cassandra-tools-5.0~rc1-1.noarch.rpm (with props) dev/cassandra/5.0-rc1/redhat/noboolean/repodata/ dev/cassandra/5.0-rc1/redhat/noboolean/repodata/3cf06e6291a68088c42d09aa7b97dd0173aed84a0cc3db19f83a32a501aee68d-primary.sqlite.bz2 (with props) dev/cassandra/5.0-rc1/redhat/noboolean/repodata/3cf06e6291a68088c42d09aa7b97dd0173aed84a0cc3db19f83a32a501aee68d-primary.sqlite.bz2.asc dev/cassandra/5.0-rc1/redhat/noboolean/repodata/475e1e0b185090e14d26e79863557c76d365c5860c4316f8432a188e4d5cf169-primary.xml.gz (with props) dev/cassandra/5.0-rc1/redhat/noboolean/repodata/475e1e0b185090e14d26e79863557c76d365c5860c4316f8432a188e4d5cf169-primary.xml.gz.asc dev/cassandra/5.0-rc1/redhat/noboolean/repodata/4e3c900a8fdb94c4990fdf38c82af7088099f39152a9d8e881836ffc58933732-filelists.xml.gz (with props) dev/cassandra/5.0-rc1/redhat/noboolean/repodata/4e3c900a8fdb94c4990fdf38c82af7088099f39152a9d8e881836ffc58933732-filelists.xml.gz.asc dev/cassandra/5.0-rc1/redhat/noboolean/repodata/64f9c4f32e57fac78d6dc3ca9eabf72767eafaa93500cb1a4ea0e92bcec5121b-filelists.sqlite.bz2 (with props) dev/cassandra/5.0-rc1/redhat/noboolean/repodata/64f9c4f32e57fac78d6dc3ca9eabf72767eafaa93500cb1a4ea0e92bcec5121b-filelists.sqlite.bz2.asc dev/cassandra/5.0-rc1/redhat/noboolean/repodata/c5ffcea705f2da28cfd049ecc8daefff938a102679582e739a847aa32e7d64e9-other.sqlite.bz2 (with props) dev/cassandra/5.0-rc1/redhat/noboolean/repodata/c5ffcea705f2da28cfd049ecc8daefff938a102679582e739a847aa32e7d64e9-other.sqlite.bz2.asc dev/cassandra/5.0-rc1/redhat/noboolean/repodata/ddd136830baa04368bac065027b1a4db433eb9b7ecb66751550a2f56800c9931-other.xml.gz (with props) dev/cassandra/5.0-rc1/redhat/noboolean/repodata/ddd136830baa04368bac065027b1a4db433eb9b7ecb66751550a2f56800c9931-other.xml.gz.asc dev/cassandra/5.0-rc1/redhat/noboolean/repodata/repomd.xml dev/cassandra/5.0-rc1/redhat/noboolean/repodata/repomd.xml.asc dev/cassandra/5.0-rc1/redhat/repodata/ dev/cassandra/5.0-rc1/redhat/repodata/0fca6eefecc34ed98e03cec80865a477435283f5728b80e521e59829906570e3-other.xml.gz (with props) dev/cassandra/5.0-rc1/redhat/repodata/0fca6eefecc34ed98e03cec80865a477435283f5728b80e521e59829906570e3-other.xml.gz.asc dev/cassandra/5.0-rc1/redhat/repodata/10880284d1899dae338c6198cf0e7b4656b67efc38ea1396cc863fb3e1d6a538-filelists.sqlite.bz2 (with props) dev/cassandra/5.0-rc1/redhat/repodata/10880284d1899dae338c6198cf0e7b4656b67efc38ea1396cc863fb3e1d6a538-filelists.sqlite.bz2.asc dev/cassandra/5.0-rc1/redhat/repodata/2e044be68602a8b3cdbc5e0f28ed7025e2af6e141704e6c922a0e79aba10a2e9-primary.sqlite.bz2 (with props) dev/cassandra/5.0-rc1/redhat/repodata/2e044be68602a8b3cdbc5e0f28ed7025e2af6e141704e6c922a0e79aba10a2e9-primary.sqlite.bz2.asc dev/cassandra/5.0-rc1/redhat/repodata/ad9ed8c8dc13e5907bee7b8b8e597c5e725feaed5995f4a120ad761c29bedff1-other.sqlite.bz2 (with props) dev/cassandra/5.0-rc1/redhat/repodata/ad9ed8c8dc13e5907bee7b8b8e597c5e725feaed5995f4a120ad761c29bedff1-other.sqlite.bz2.asc dev/cassandra/5.0-rc1/redhat/repodata/b0162c9b018594052a167206696ae61f5bc8ae80b0fac596e06c1517003f06b1-primary.xml.gz (with props) dev/cassandra/5.0-rc1/redhat/repodata/b0162c9b018594052a167206696ae61f5bc8ae80b0fac596e06c1517003f06b1-primary.xml.gz.asc dev/cassandra/5.0-rc1/redhat/repodata/d61753fb85e2b77c771e8a00e66296f22c12007a0830f31a3e78bdcb87d6395c-filelists.xml.gz (with props) dev/cassandra/5.0-rc1/redhat/repodata/d61753fb85e2b77c771e8a00e66296f22c12007a0830f31a3e78bdcb87d6395c-filelists.xml.gz.asc dev/cassandra/5.0-rc1/redhat/repodata/repomd.xml dev/cassandra/5.0-rc1/redhat/repodata/repomd.xml.asc Added: dev/cassandra/5.0-rc1/redhat/cassandra-5.0~rc1-1.noarch.rpm == Binary file - no diff available. Propchange: dev/cassandra/5.0-rc1/redhat/cassandra-5.0~rc1-1.noarch.rpm -- svn:mime-type = application/octet-stream Added: dev/cassandra/5.0-rc1/redhat/cassandra-5.0~rc1-1.src.rpm == Binary file - no diff available. Propchange: dev/cassandra/5.0-rc1/re
svn commit: r70095 - in /dev/cassandra/5.0-rc1/debian: ./ dists/ dists/50x/ dists/50x/main/ dists/50x/main/binary-amd64/ dists/50x/main/binary-arm64/ dists/50x/main/binary-i386/ dists/50x/main/source/
Author: mck Date: Tue Jul 2 11:04:02 2024 New Revision: 70095 Log: staging cassandra debian packages for 5.0-rc1 Added: dev/cassandra/5.0-rc1/debian/ dev/cassandra/5.0-rc1/debian/cassandra-tools_5.0~rc1_all.deb (with props) dev/cassandra/5.0-rc1/debian/cassandra_5.0~rc1.dsc dev/cassandra/5.0-rc1/debian/cassandra_5.0~rc1.tar.gz (with props) dev/cassandra/5.0-rc1/debian/cassandra_5.0~rc1_all.deb (with props) dev/cassandra/5.0-rc1/debian/cassandra_5.0~rc1_amd64.buildinfo dev/cassandra/5.0-rc1/debian/cassandra_5.0~rc1_amd64.changes dev/cassandra/5.0-rc1/debian/dists/ dev/cassandra/5.0-rc1/debian/dists/50x/ dev/cassandra/5.0-rc1/debian/dists/50x/InRelease dev/cassandra/5.0-rc1/debian/dists/50x/Release dev/cassandra/5.0-rc1/debian/dists/50x/Release.gpg dev/cassandra/5.0-rc1/debian/dists/50x/main/ dev/cassandra/5.0-rc1/debian/dists/50x/main/binary-amd64/ dev/cassandra/5.0-rc1/debian/dists/50x/main/binary-amd64/Packages dev/cassandra/5.0-rc1/debian/dists/50x/main/binary-amd64/Packages.gz (with props) dev/cassandra/5.0-rc1/debian/dists/50x/main/binary-amd64/Release dev/cassandra/5.0-rc1/debian/dists/50x/main/binary-arm64/ dev/cassandra/5.0-rc1/debian/dists/50x/main/binary-arm64/Packages dev/cassandra/5.0-rc1/debian/dists/50x/main/binary-arm64/Packages.gz (with props) dev/cassandra/5.0-rc1/debian/dists/50x/main/binary-arm64/Release dev/cassandra/5.0-rc1/debian/dists/50x/main/binary-i386/ dev/cassandra/5.0-rc1/debian/dists/50x/main/binary-i386/Packages dev/cassandra/5.0-rc1/debian/dists/50x/main/binary-i386/Packages.gz (with props) dev/cassandra/5.0-rc1/debian/dists/50x/main/binary-i386/Release dev/cassandra/5.0-rc1/debian/dists/50x/main/source/ dev/cassandra/5.0-rc1/debian/dists/50x/main/source/Release dev/cassandra/5.0-rc1/debian/dists/50x/main/source/Sources.gz (with props) dev/cassandra/5.0-rc1/debian/pool/ dev/cassandra/5.0-rc1/debian/pool/main/ dev/cassandra/5.0-rc1/debian/pool/main/c/ dev/cassandra/5.0-rc1/debian/pool/main/c/cassandra/ dev/cassandra/5.0-rc1/debian/pool/main/c/cassandra/cassandra-tools_5.0~rc1_all.deb (with props) dev/cassandra/5.0-rc1/debian/pool/main/c/cassandra/cassandra_5.0~rc1.dsc dev/cassandra/5.0-rc1/debian/pool/main/c/cassandra/cassandra_5.0~rc1.tar.gz (with props) dev/cassandra/5.0-rc1/debian/pool/main/c/cassandra/cassandra_5.0~rc1_all.deb (with props) Added: dev/cassandra/5.0-rc1/debian/cassandra-tools_5.0~rc1_all.deb == Binary file - no diff available. Propchange: dev/cassandra/5.0-rc1/debian/cassandra-tools_5.0~rc1_all.deb -- svn:mime-type = application/octet-stream Added: dev/cassandra/5.0-rc1/debian/cassandra_5.0~rc1.dsc == --- dev/cassandra/5.0-rc1/debian/cassandra_5.0~rc1.dsc (added) +++ dev/cassandra/5.0-rc1/debian/cassandra_5.0~rc1.dsc Tue Jul 2 11:04:02 2024 @@ -0,0 +1,41 @@ +-BEGIN PGP SIGNED MESSAGE- +Hash: SHA512 + +Format: 1.0 +Source: cassandra +Binary: cassandra, cassandra-tools +Architecture: all +Version: 5.0~rc1 +Maintainer: Eric Evans +Uploaders: Sylvain Lebresne +Homepage: https://cassandra.apache.org +Standards-Version: 3.8.3 +Vcs-Browser: https://gitbox.apache.org/repos/asf?p=cassandra.git +Vcs-Git: https://gitbox.apache.org/repos/asf/cassandra.git +Build-Depends: debhelper (>= 11), openjdk-17-jdk-headless | openjdk-11-jdk-headless | java17-sdk | java11-sdk, ant (>= 1.10), ant-optional (>= 1.10), dh-python, python3-dev (>= 3.6), quilt, bash-completion +Package-List: + cassandra deb misc extra arch=all + cassandra-tools deb misc extra arch=all +Checksums-Sha1: + 7de42451e727b39030208345c9104fcb8e62bee0 23703459 cassandra_5.0~rc1.tar.gz +Checksums-Sha256: + 7d9ccfe14cfb9e2bf62cc2859e46a6171b1d3cf76c8a96b6f64de4f26285eac5 23703459 cassandra_5.0~rc1.tar.gz +Files: + 99d959125f7c11a193f202e211fec817 23703459 cassandra_5.0~rc1.tar.gz + +-BEGIN PGP SIGNATURE- + +iQIzBAEBCgAdFiEEpMRl/qDFUlYaOSph6RM1134+h8sFAmaD3nYACgkQ6RM1134+ +h8vWnhAAw9Df2C/Kgg403mAHUBvch8YyjN8ouaAWpoV9/XF9wMS1JOqWa8d+hyjA +f1k4Y27R8yqYk3ZvYACQCrEzqX58BiCUaan0F3f3dLyLMROR60slELPm9ipsZmID +7yIc20CosybxSOTavqHWMRx9Qo81tUJQ9TwsLfQUOghZSJBQqKU0OlbUh6NwRpP7 +0e2CITDwjzsB2qLY7kif4Y9caOeiorgcEayLt9t5CicwN5btukSH/EDOJcsKIa7M +xmzGhJmVvT+/hBxqJNBGPTuVKNpxqs7btbnzqFmhqDWfGKdxMz+clSh7nvR+wTUT +LW0VuLed9WgyGDioafW7t6Ogge4BUomPod7rJZV0FFkgoTWUI9hSyApjvEApTg0Q +CZaGiMAVtJI+BGjEPcFu0GfAhRrw9LLetRmOjlyinc0Ae7nSgWnu9AEbBAlAZ9Ap +6oZz5dO2XPpUE1btTOslFS8zOHB1key/8Y6ocyJ56o6Z/zH/gw/BqzNC6F1ZUshE +nM70sJVZydZ9q9khVuoRTqylQ6ammM4ScOPqu8180YX9sWHsXg5sqY4aMWtBS4bs +P4nzrcFyF7jUFcSgmWdqJWUGdFDhI29nWfZXz5PafR0STelk3SszNg2XYzwtcmCs +/ZPe75KdopH8bxNuK22cAfaEkbJ9EAgZMhsZRrA2HamvKAlxwq4= +=bJ0j +-END PGP
svn commit: r70094 - /dev/cassandra/5.0-rc1/
Author: mck Date: Tue Jul 2 11:00:29 2024 New Revision: 70094 Log: staging cassandra 5.0-rc1 Added: dev/cassandra/5.0-rc1/ dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-bin.tar.gz (with props) dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-bin.tar.gz.asc dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-bin.tar.gz.sha256 dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-bin.tar.gz.sha512 dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-src.tar.gz (with props) dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-src.tar.gz.asc dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-src.tar.gz.sha256 dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-src.tar.gz.sha512 Added: dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-bin.tar.gz == Binary file - no diff available. Propchange: dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-bin.tar.gz -- svn:mime-type = application/octet-stream Added: dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-bin.tar.gz.asc == --- dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-bin.tar.gz.asc (added) +++ dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-bin.tar.gz.asc Tue Jul 2 11:00:29 2024 @@ -0,0 +1,16 @@ +-BEGIN PGP SIGNATURE- + +iQIzBAABCgAdFiEEpMRl/qDFUlYaOSph6RM1134+h8sFAmaD3WQACgkQ6RM1134+ +h8sDgg//WudIQeTSsqxg+NMYG+QK68O4YomNbDr64od9DCpw0pLykR2QQmJe3yVg +T1GfH00C+CTN5nI0bWb3wQ48yYBrcBGrZTM2FKsFW601WhdjwGcLHZWQ21q5QTH1 +DhYHvP9GfxnS2BB72KOH8UDahHOLLsPZvjZ0tJ8HgXhjxHCmGj4pMQSVKXuRNCpi +2rc8s/yejIgZPnIYQFiRTVFO70Rer3+9A1pAVy+8RQDVDatJze5qzYUbwwFRADUb +vZEXDiu+2SOWPiIACs5LqviE5p+Mzt6TGhN16cMQAZqKqF6LoN8dJcs5ik13uHhN +nOyDfQjCS6XiqZMaQttAeWND/MU+xnPYe+8jR5eHvUj+m+0ozEW9nl5iDaQlQ12u +FLtfWtJHcPH1Km0mBFhyM/1SlvS0Z+e5ZM9lS2VKp/tbN/2O3ttrgTA5nsoKemlH +lZuE+hlyVDZB54NtzMD3QlQ/3blt7KvEdPCGYudWIqZpomvWGwTOjJe8xAb1Y7LK +KkhP1wlzpOHvymZ8ryybrK76bwgwPNrbIyuzbIi0gm3TNEG5wWa89n2Rv66eEpM7 +QfGPiSbnZCYs2RU6XRkqkQl0L4+gd6EGtUgD9mXSv+5nwI55BNNpCEQRjUTyOoUc +0NVR2qD/nn72WrvNv35Vs+mUg3vfE0pt1zDeXTzexrhMFWX9n9s= +=PQRl +-END PGP SIGNATURE- Added: dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-bin.tar.gz.sha256 == --- dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-bin.tar.gz.sha256 (added) +++ dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-bin.tar.gz.sha256 Tue Jul 2 11:00:29 2024 @@ -0,0 +1 @@ +eeefd24dfed3a4c775578857982b22be86f80cceb0ec386696d4d22049e38f84 Added: dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-bin.tar.gz.sha512 == --- dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-bin.tar.gz.sha512 (added) +++ dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-bin.tar.gz.sha512 Tue Jul 2 11:00:29 2024 @@ -0,0 +1 @@ +5646c32fa2dd21d77e7d40050b7fd1a10592b90f7098f4bd6dd1a0343fc46e87b0de4e7f63fec544421812ceb37677fc77f7c373e5c215263deb33c4eb12ebf1 Added: dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-src.tar.gz == Binary file - no diff available. Propchange: dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-src.tar.gz -- svn:mime-type = application/octet-stream Added: dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-src.tar.gz.asc == --- dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-src.tar.gz.asc (added) +++ dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-src.tar.gz.asc Tue Jul 2 11:00:29 2024 @@ -0,0 +1,16 @@ +-BEGIN PGP SIGNATURE- + +iQIzBAABCgAdFiEEpMRl/qDFUlYaOSph6RM1134+h8sFAmaD3WgACgkQ6RM1134+ +h8uqBBAA0EAp2IC1e92bGTivAe8u6fjya+TzZklrOe2UnTBSm8jf8sokbCmgUy8s +R14IDJruujqV0dcuB5fdq095eb2QANdYTqHJ4toq6XacE8xSzEWgHkZYtzyJ79Ue +Soy0DX/ZZy+5PUuLTpAypjs5oXVwzHnUGsmHPHRGgn6LfAPimvXBEK3/dKKNcifJ +2wzTC6CZ6/mzdmpmfdJvqJcIyhHdHtgmycuLzm8CDLvbA0pdeztP77rpYWRKSdTO +cSy1PRoIuVeBDmQvjmj5BiK01as4lClmWSBx54aqbvB2RU7WSaprvZzPgNf/Y5LH +ZFUsVM3iKU+CN1R8/OHKbC2paDPgE6AIkdzMVWR1sGpwRinNFXVCBrKHLGSUz7/q +3XgEp9/SmXmOi+pDDJKRv2AcddIvezmL3ZsteFXxcGtoVdNpOmyQh+XAlOFp/WK2 +thqohgq/WC42e6bWc3qO/gJ2Q/NIWx7oT0Vzyn9b6ImVxlHEGdj8BAhFcShdfLhr +l+UuPnqgV6sQbvF16n9RpxSft3F85u5GIX2InqTfEL5U/SuR7Vqqi+EMQrUPZhlk +ETNqnb5CB/Y5xntw0dL/CIciXLS/xgAjertlkuHpseNnopOAtGR2f2umVS87mWCI +5zqBZRITHAJWidrX8EZulPxNNZDnzmykN45er01k8edAFcrWqm0= +=a9ao +-END PGP SIGNATURE- Added: dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-src.tar.gz.sha256 == --- dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-src.tar.gz.sha256 (added) +++ dev/cassandra/5.0-rc1/apache-cassandra-5.0-rc1-src.tar.gz.sha256 Tue Jul 2 11:00:29 2024 @@
[jira] [Comment Edited] (CASSANDRA-19739) Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171, CVE-2024-29857, CVE-2024-34447
[
https://issues.apache.org/jira/browse/CASSANDRA-19739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862399#comment-17862399
]
Stefan Miklosovic edited comment on CASSANDRA-19739 at 7/2/24 10:59 AM:
what is interesting is that we have this dep in parent-pom-template.xml
{code}
org.bouncycastle
bcpkix-jdk18on
1.76
{code}
When I manually remove ~/.m2/repository/org/bouncycastle/bc* and I do ant
realclean && ant jar again, I see that it pulls
{code}
[resolver:resolve] Downloading
https://repo1.maven.org/maven2/org/bouncycastle/bcpkix-jdk18on/1.76/bcpkix-jdk18on-1.76.pom
[resolver:resolve] Downloaded
https://repo1.maven.org/maven2/org/bouncycastle/bcpkix-jdk18on/1.76/bcpkix-jdk18on-1.76.pom
(2 KB at 8.1 KB/sec)
[resolver:resolve] Downloading
https://repo1.maven.org/maven2/org/bouncycastle/bcprov-jdk18on/1.76/bcprov-jdk18on-1.76.pom
[resolver:resolve] Downloaded
https://repo1.maven.org/maven2/org/bouncycastle/bcprov-jdk18on/1.76/bcprov-jdk18on-1.76.pom
(2 KB at 65.5 KB/sec)
[resolver:resolve] Downloading
https://repo1.maven.org/maven2/org/bouncycastle/bcutil-jdk18on/1.76/bcutil-jdk18on-1.76.pom
[resolver:resolve] Downloaded
https://repo1.maven.org/maven2/org/bouncycastle/bcutil-jdk18on/1.76/bcutil-jdk18on-1.76.pom
(2 KB at 80.6 KB/sec)
{code}
so it pulls two more -
bcprov-jdk18on (where CVEs are)
bcutil-jdk18on
We should probably enumerate them explicitly, these two are transitive deps and
CVEs are found in one of them.
was (Author: smiklosovic):
what is interesting is that we have this dep in parent-pom-template.xml
{code}
org.bouncycastle
bcpkix-jdk18on
1.76
{code}
When I manually remove ~/.m2/repository/org/bouncycastle/bc* and I do ant
realclean && ant jar again, I see that it pulls
{code}
[resolver:resolve] Downloading
https://repo1.maven.org/maven2/org/bouncycastle/bcpkix-jdk18on/1.78/bcpkix-jdk18on-1.76.pom
[resolver:resolve] Downloaded
https://repo1.maven.org/maven2/org/bouncycastle/bcpkix-jdk18on/1.78/bcpkix-jdk18on-1.76.pom
(2 KB at 8.1 KB/sec)
[resolver:resolve] Downloading
https://repo1.maven.org/maven2/org/bouncycastle/bcprov-jdk18on/1.78/bcprov-jdk18on-1.76.pom
[resolver:resolve] Downloaded
https://repo1.maven.org/maven2/org/bouncycastle/bcprov-jdk18on/1.78/bcprov-jdk18on-1.76.pom
(2 KB at 65.5 KB/sec)
[resolver:resolve] Downloading
https://repo1.maven.org/maven2/org/bouncycastle/bcutil-jdk18on/1.78/bcutil-jdk18on-1.76.pom
[resolver:resolve] Downloaded
https://repo1.maven.org/maven2/org/bouncycastle/bcutil-jdk18on/1.78/bcutil-jdk18on-1.76.pom
(2 KB at 80.6 KB/sec)
{code}
so it pulls two more -
bcprov-jdk18on (where CVEs are)
bcutil-jdk18on
We should probably enumerate them explicitly, these two are transitive deps and
CVEs are found in one of them.
> Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171,
> CVE-2024-29857, CVE-2024-34447
> ---
>
> Key: CASSANDRA-19739
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19739
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 5.0-rc, 5.x
>
>
> This came up after I bumped dependency-check version to 10.0.0 as suggested
> in CASSANDRA-19738.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19739) Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171, CVE-2024-29857, CVE-2024-34447
[
https://issues.apache.org/jira/browse/CASSANDRA-19739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862399#comment-17862399
]
Stefan Miklosovic commented on CASSANDRA-19739:
---
what is interesting is that we have this dep in parent-pom-template.xml
{code}
org.bouncycastle
bcpkix-jdk18on
1.76
{code}
When I manually remove ~/.m2/repository/org/bouncycastle/bc* and I do ant
realclean && ant jar again, I see that it pulls
{code}
[resolver:resolve] Downloading
https://repo1.maven.org/maven2/org/bouncycastle/bcpkix-jdk18on/1.78/bcpkix-jdk18on-1.76.pom
[resolver:resolve] Downloaded
https://repo1.maven.org/maven2/org/bouncycastle/bcpkix-jdk18on/1.78/bcpkix-jdk18on-1.76.pom
(2 KB at 8.1 KB/sec)
[resolver:resolve] Downloading
https://repo1.maven.org/maven2/org/bouncycastle/bcprov-jdk18on/1.78/bcprov-jdk18on-1.76.pom
[resolver:resolve] Downloaded
https://repo1.maven.org/maven2/org/bouncycastle/bcprov-jdk18on/1.78/bcprov-jdk18on-1.76.pom
(2 KB at 65.5 KB/sec)
[resolver:resolve] Downloading
https://repo1.maven.org/maven2/org/bouncycastle/bcutil-jdk18on/1.78/bcutil-jdk18on-1.76.pom
[resolver:resolve] Downloaded
https://repo1.maven.org/maven2/org/bouncycastle/bcutil-jdk18on/1.78/bcutil-jdk18on-1.76.pom
(2 KB at 80.6 KB/sec)
{code}
so it pulls two more -
bcprov-jdk18on (where CVEs are)
bcutil-jdk18on
We should probably enumerate them explicitly, these two are transitive deps and
CVEs are found in one of them.
> Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171,
> CVE-2024-29857, CVE-2024-34447
> ---
>
> Key: CASSANDRA-19739
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19739
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 5.0-rc, 5.x
>
>
> This came up after I bumped dependency-check version to 10.0.0 as suggested
> in CASSANDRA-19738.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra) tag 5.0-rc1-tentative created (now 01eea8a0d7)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to tag 5.0-rc1-tentative in repository https://gitbox.apache.org/repos/asf/cassandra.git at 01eea8a0d7 (commit) This tag includes the following new commits: new 01eea8a0d7 Prepare debian changelog for 5.0-rc1 The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra) 01/01: Prepare debian changelog for 5.0-rc1
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to tag 5.0-rc1-tentative in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 01eea8a0d74deaede236edb25335fa470502106e Author: Mick Semb Wever AuthorDate: Tue Jul 2 12:54:06 2024 +0200 Prepare debian changelog for 5.0-rc1 --- debian/changelog | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index f95efc6b4f..0efef36984 100644 --- a/debian/changelog +++ b/debian/changelog @@ -2,7 +2,7 @@ cassandra (5.0~rc1) unstable; urgency=medium * New release - -- Mick Semb Wever Fri, 21 Jun 2024 16:10:00 +0200 + -- Mick Semb Wever Tue, 02 Jul 2024 12:53:45 +0200 cassandra (5.0~beta1) unstable; urgency=medium - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19668) SIGSEGV originating in Paxos V2 Scheduled Task
[
https://issues.apache.org/jira/browse/CASSANDRA-19668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-19668:
---
Fix Version/s: 4.1.6
5.0-beta2
5.0
5.1
(was: 5.x)
(was: 4.1.x)
(was: 5.0-rc)
> SIGSEGV originating in Paxos V2 Scheduled Task
> --
>
> Key: CASSANDRA-19668
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19668
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Lightweight Transactions
>Reporter: Jon Haddad
>Assignee: Jon Haddad
>Priority: Urgent
> Fix For: 4.1.6, 5.0-beta2, 5.0, 5.1
>
> Attachments: ci_summar-5.0.html, ci_summary-4.1.html,
> ci_summary-trunk.html
>
>
> I haven't gotten to the root cause of this yet. Several 4.1 nodes have
> crashed in in production. I'm not sure if this is related to Paxos v2 or
> not, but it is enabled. offheap_objects also enabled.
> I'm not sure if this affects 5.0, yet.
> Most of the crashes don't have a stacktrace - they only reference this
> {noformat}
> Stack: [0x7fabf4c34000,0x7fabf4d34000], sp=0x7fabf4d31f00, free
> space=1015k
> Native frames: (J=compiled Java code, A=aot compiled Java code,
> j=interpreted, Vv=VM code, C=native code)
> v ~StubRoutines::jint_disjoint_arraycopy
> {noformat}
> They all are in the {{ScheduledTasks}} thread.
> However, one node does have this in the crash log:
> {noformat}
> --- T H R E A D ---
> Current thread (0x78b375eac800): JavaThread "ScheduledTasks:1" daemon
> [_thread_in_Java, id=151791, stack(0x78b34b78,0x78b34b88)]
> Stack: [0x78b34b78,0x78b34b88], sp=0x78b34b87c350, free
> space=1008k
> Native frames: (J=compiled Java code, A=aot compiled Java code,
> j=interpreted, Vv=VM code, C=native code)
> J 29467 c2
> org.apache.cassandra.db.rows.AbstractCell.clone(Lorg/apache/cassandra/utils/memory/ByteBufferCloner;)Lorg/apache/cassandra/db/rows/Cell;
> (50 bytes) @ 0x78b3dd40a42f [0x78b3dd409de0+0x064f]
> J 17669 c2
> org.apache.cassandra.db.rows.Cell.clone(Lorg/apache/cassandra/utils/memory/Cloner;)Lorg/apache/cassandra/db/rows/ColumnData;
> (6 bytes) @ 0x78b3dc54edc0 [0x78b3dc54ed40+0x0080]
> J 17816 c2
> org.apache.cassandra.db.rows.BTreeRow$$Lambda$845.apply(Ljava/lang/Object;)Ljava/lang/Object;
> (12 bytes) @ 0x78b3dbed01a4 [0x78b3dbed0120+0x0084]
> J 17828 c2
> org.apache.cassandra.utils.btree.BTree.transform([Ljava/lang/Object;Ljava/util/function/Function;)[Ljava/lang/Object;
> (194 bytes) @ 0x78b3dc5f35f0 [0x78b3dc5f34a0+0x0150]
> J 35096 c2
> org.apache.cassandra.db.rows.BTreeRow.clone(Lorg/apache/cassandra/utils/memory/Cloner;)Lorg/apache/cassandra/db/rows/Row;
> (37 bytes) @ 0x78b3dda9111c [0x78b3dda90fe0+0x013c]
> J 30500 c2
> org.apache.cassandra.utils.memory.EnsureOnHeap$CloneToHeap.applyToRow(Lorg/apache/cassandra/db/rows/Row;)Lorg/apache/cassandra/db/rows/Row;
> (16 bytes) @ 0x78b3dd59b91c [0x78b3dd59b8c0+0x005c]
> J 26498 c2 org.apache.cassandra.db.transform.BaseRows.hasNext()Z (215 bytes)
> @ 0x78b3dcf1c454 [0x78b3dcf1c180+0x02d4]
> J 30775 c2
> org.apache.cassandra.utils.MergeIterator$OneToOne.computeNext()Ljava/lang/Object;
> (49 bytes) @ 0x78b3dc789020 [0x78b3dc788fc0+0x0060]
> J 9082 c2 org.apache.cassandra.utils.AbstractIterator.hasNext()Z (80 bytes) @
> 0x78b3dbb3c544 [0x78b3dbb3c440+0x0104]
> J 35593 c2
> org.apache.cassandra.service.paxos.uncommitted.PaxosRows$PaxosMemtableToKeyStateIterator.computeNext()Lorg/apache/cassandra/service/paxos/uncommitted/PaxosKeyState;
> (126 bytes) @ 0x78b3dc7ceeec [0x78b3dc7cee20+0x00cc]
> J 35591 c2
> org.apache.cassandra.service.paxos.uncommitted.PaxosRows$PaxosMemtableToKeyStateIterator.computeNext()Ljava/lang/Object;
> (5 bytes) @ 0x78b3dc7d09e4 [0x78b3dc7d09a0+0x0044]
> J 9082 c2 org.apache.cassandra.utils.AbstractIterator.hasNext()Z (80 bytes) @
> 0x78b3dbb3c544 [0x78b3dbb3c440+0x0104]
> J 34146 c2
> com.google.common.collect.Iterators.addAll(Ljava/util/Collection;Ljava/util/Iterator;)Z
> (41 bytes) @ 0x78b3dd9197e8 [0x78b3dd919680+0x0168]
> J 38256 c1
> org.apache.cassandra.service.paxos.uncommitted.PaxosRows.toIterator(Lorg/apache/cassandra/db/partitions/UnfilteredPartitionIterator;Lorg/apache/cassandra/schema/TableId;Z)Lorg/apache/cassandra/utils/CloseableIterator;
> (49 bytes) @ 0x78b3d6b677ac [0x78b3d6b672e0+0x04cc]
> J 34823 c1
> org.apache.cassan
[jira] [Comment Edited] (CASSANDRA-19739) Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171, CVE-2024-29857, CVE-2024-34447
[
https://issues.apache.org/jira/browse/CASSANDRA-19739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862392#comment-17862392
]
Stefan Miklosovic edited comment on CASSANDRA-19739 at 7/2/24 10:37 AM:
moving it to test scope fails all tests in
org.apache.cassandra.security.SSLFactoryTest for {*}Java 17{*}.
https://app.circleci.com/pipelines/github/instaclustr/cassandra//workflows/ff56cfa5-2cab-42c4-9926-69f9496d74fd/jobs/246921/tests
{code:java}
DEBUG [main] 2024-07-02 12:30:57,273 SelfSignedCertificate.java:253 - Failed to
generate a self-signed X.509 certificate using sun.security.x509:
java.lang.UnsupportedOperationException: OpenJdkSelfSignedCertGenerator not
supported on the used JDK version
at
io.netty.handler.ssl.util.OpenJdkSelfSignedCertGenerator.generate(OpenJdkSelfSignedCertGenerator.java:167)
at
io.netty.handler.ssl.util.SelfSignedCertificate.(SelfSignedCertificate.java:251)
at
io.netty.handler.ssl.util.SelfSignedCertificate.(SelfSignedCertificate.java:166)
at
io.netty.handler.ssl.util.SelfSignedCertificate.(SelfSignedCertificate.java:115)
at
io.netty.handler.ssl.util.SelfSignedCertificate.(SelfSignedCertificate.java:90)
at
org.apache.cassandra.security.SSLFactoryTest.(SSLFactoryTest.java:67)
{code}
or simply (this one is more prevalent)
{code}
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.cassandra.security.SSLFactoryTest
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77)
at
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499)
at
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480)
at
org.junit.runners.BlockJUnit4ClassRunner.createTest(BlockJUnit4ClassRunner.java:217)
{code}
I think that the former happens because I was testing it locally on Oracle Java
and it does not know any "OpenJdkSelfSignedCertGenerator" nevertheless it does
not work in Circle either for other reasons.
On Java 11 it works.
was (Author: smiklosovic):
moving it to test scope fails all tests in
org.apache.cassandra.security.SSLFactoryTest for {*}Java 17{*}.
https://app.circleci.com/pipelines/github/instaclustr/cassandra//workflows/ff56cfa5-2cab-42c4-9926-69f9496d74fd/jobs/246921/tests
{code:java}
DEBUG [main] 2024-07-02 12:30:57,273 SelfSignedCertificate.java:253 - Failed to
generate a self-signed X.509 certificate using sun.security.x509:
java.lang.UnsupportedOperationException: OpenJdkSelfSignedCertGenerator not
supported on the used JDK version
at
io.netty.handler.ssl.util.OpenJdkSelfSignedCertGenerator.generate(OpenJdkSelfSignedCertGenerator.java:167)
at
io.netty.handler.ssl.util.SelfSignedCertificate.(SelfSignedCertificate.java:251)
at
io.netty.handler.ssl.util.SelfSignedCertificate.(SelfSignedCertificate.java:166)
at
io.netty.handler.ssl.util.SelfSignedCertificate.(SelfSignedCertificate.java:115)
at
io.netty.handler.ssl.util.SelfSignedCertificate.(SelfSignedCertificate.java:90)
at
org.apache.cassandra.security.SSLFactoryTest.(SSLFactoryTest.java:67)
{code}
or simply (this one is more prevalent)
{code}
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.cassandra.security.SSLFactoryTest
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77)
at
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499)
at
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480)
at
org.junit.runners.BlockJUnit4ClassRunner.createTest(BlockJUnit4ClassRunner.java:217)
{code}
On Java 11 it works.
> Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171,
> CVE-2024-29857, CVE-2024-34447
> ---
>
> Key: CASSANDRA-19739
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19739
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 5.0-rc, 5.x
>
>
> This came up after I bumped dependency-check version to 10.0.0 as suggested
> in CASSA
[jira] [Comment Edited] (CASSANDRA-19739) Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171, CVE-2024-29857, CVE-2024-34447
[
https://issues.apache.org/jira/browse/CASSANDRA-19739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862392#comment-17862392
]
Stefan Miklosovic edited comment on CASSANDRA-19739 at 7/2/24 10:35 AM:
moving it to test scope fails all tests in
org.apache.cassandra.security.SSLFactoryTest for {*}Java 17{*}.
https://app.circleci.com/pipelines/github/instaclustr/cassandra//workflows/ff56cfa5-2cab-42c4-9926-69f9496d74fd/jobs/246921/tests
{code:java}
DEBUG [main] 2024-07-02 12:30:57,273 SelfSignedCertificate.java:253 - Failed to
generate a self-signed X.509 certificate using sun.security.x509:
java.lang.UnsupportedOperationException: OpenJdkSelfSignedCertGenerator not
supported on the used JDK version
at
io.netty.handler.ssl.util.OpenJdkSelfSignedCertGenerator.generate(OpenJdkSelfSignedCertGenerator.java:167)
at
io.netty.handler.ssl.util.SelfSignedCertificate.(SelfSignedCertificate.java:251)
at
io.netty.handler.ssl.util.SelfSignedCertificate.(SelfSignedCertificate.java:166)
at
io.netty.handler.ssl.util.SelfSignedCertificate.(SelfSignedCertificate.java:115)
at
io.netty.handler.ssl.util.SelfSignedCertificate.(SelfSignedCertificate.java:90)
at
org.apache.cassandra.security.SSLFactoryTest.(SSLFactoryTest.java:67)
{code}
or simply (this one is more prevalent)
{code}
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.cassandra.security.SSLFactoryTest
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77)
at
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499)
at
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480)
at
org.junit.runners.BlockJUnit4ClassRunner.createTest(BlockJUnit4ClassRunner.java:217)
{code}
On Java 11 it works.
was (Author: smiklosovic):
moving it to test scope fails all tests in
org.apache.cassandra.security.SSLFactoryTest for {*}Java 17{*}.
https://app.circleci.com/pipelines/github/instaclustr/cassandra//workflows/ff56cfa5-2cab-42c4-9926-69f9496d74fd/jobs/246921/tests
{code:java}
DEBUG [main] 2024-07-02 12:30:57,273 SelfSignedCertificate.java:253 - Failed to
generate a self-signed X.509 certificate using sun.security.x509:
java.lang.UnsupportedOperationException: OpenJdkSelfSignedCertGenerator not
supported on the used JDK version
at
io.netty.handler.ssl.util.OpenJdkSelfSignedCertGenerator.generate(OpenJdkSelfSignedCertGenerator.java:167)
at
io.netty.handler.ssl.util.SelfSignedCertificate.(SelfSignedCertificate.java:251)
at
io.netty.handler.ssl.util.SelfSignedCertificate.(SelfSignedCertificate.java:166)
at
io.netty.handler.ssl.util.SelfSignedCertificate.(SelfSignedCertificate.java:115)
at
io.netty.handler.ssl.util.SelfSignedCertificate.(SelfSignedCertificate.java:90)
at
org.apache.cassandra.security.SSLFactoryTest.(SSLFactoryTest.java:67)
{code}
On Java 11 it works.
> Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171,
> CVE-2024-29857, CVE-2024-34447
> ---
>
> Key: CASSANDRA-19739
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19739
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 5.0-rc, 5.x
>
>
> This came up after I bumped dependency-check version to 10.0.0 as suggested
> in CASSANDRA-19738.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
svn commit: r70092 - /dev/cassandra/cassandra-java-driver/4.18.1/ /release/cassandra/cassandra-java-driver/4.18.1/
Author: mck Date: Tue Jul 2 10:35:29 2024 New Revision: 70092 Log: cassandra-java-driver 4.18.1, ref: https://lists.apache.org/thread/n3142m6wk1y62bv879b7xk75vd3zglyh Added: release/cassandra/cassandra-java-driver/4.18.1/ - copied from r70091, dev/cassandra/cassandra-java-driver/4.18.1/ Removed: dev/cassandra/cassandra-java-driver/4.18.1/ - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19739) Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171, CVE-2024-29857, CVE-2024-34447
[
https://issues.apache.org/jira/browse/CASSANDRA-19739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862392#comment-17862392
]
Stefan Miklosovic commented on CASSANDRA-19739:
---
moving it to test scope fails all tests in
org.apache.cassandra.security.SSLFactoryTest for {*}Java 17{*}.
https://app.circleci.com/pipelines/github/instaclustr/cassandra//workflows/ff56cfa5-2cab-42c4-9926-69f9496d74fd/jobs/246921/tests
{code:java}
DEBUG [main] 2024-07-02 12:30:57,273 SelfSignedCertificate.java:253 - Failed to
generate a self-signed X.509 certificate using sun.security.x509:
java.lang.UnsupportedOperationException: OpenJdkSelfSignedCertGenerator not
supported on the used JDK version
at
io.netty.handler.ssl.util.OpenJdkSelfSignedCertGenerator.generate(OpenJdkSelfSignedCertGenerator.java:167)
at
io.netty.handler.ssl.util.SelfSignedCertificate.(SelfSignedCertificate.java:251)
at
io.netty.handler.ssl.util.SelfSignedCertificate.(SelfSignedCertificate.java:166)
at
io.netty.handler.ssl.util.SelfSignedCertificate.(SelfSignedCertificate.java:115)
at
io.netty.handler.ssl.util.SelfSignedCertificate.(SelfSignedCertificate.java:90)
at
org.apache.cassandra.security.SSLFactoryTest.(SSLFactoryTest.java:67)
{code}
On Java 11 it works.
> Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171,
> CVE-2024-29857, CVE-2024-34447
> ---
>
> Key: CASSANDRA-19739
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19739
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 5.0-rc, 5.x
>
>
> This came up after I bumped dependency-check version to 10.0.0 as suggested
> in CASSANDRA-19738.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19739) Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171, CVE-2024-29857, CVE-2024-34447
[ https://issues.apache.org/jira/browse/CASSANDRA-19739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17861351#comment-17861351 ] Stefan Miklosovic commented on CASSANDRA-19739: --- [~jlewandowski] [~edimitrova] should be that dependency test-scoped or not? > Investigate bcprov-jdk18on-1.76.jar: CVE-2024-30172, CVE-2024-30171, > CVE-2024-29857, CVE-2024-34447 > --- > > Key: CASSANDRA-19739 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19739 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.0-rc, 5.x > > > This came up after I bumped dependency-check version to 10.0.0 as suggested > in CASSANDRA-19738. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19735) Cannot correctly create keyspace statement with replication during schemaChange
[
https://issues.apache.org/jira/browse/CASSANDRA-19735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-19735:
Resolution: Not A Problem
Status: Resolved (was: Triage Needed)
This is failing because the dtest framework has already created that keyspace
(see {{DistributedTestBase::init}}).
> Cannot correctly create keyspace statement with replication during
> schemaChange
> ---
>
> Key: CASSANDRA-19735
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19735
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
>Reporter: ConfX
>Priority: Normal
> Fix For: 4.1.x, 5.0.x, 5.x
>
>
> h3. What happened
> A specific schema change for creating keyspace with replications failed
> during Cassandra upgrade testing, but can pass under Cassandra distributed
> testing (non-upgrade).
> h3. How to reproduce:
> Put the following test under
> {{{}cassandra/test/distributed/org/apache/cassandra/distributed/upgrade/{}}},
> and build dtest jars for any versions within [4.1.3, 5.0-alpha2].
> {code:java}
> package org.apache.cassandra.distributed.upgrade;
> public class demoUpgradeTest extends UpgradeTestBase
> @Test
> public void demoTest() throws Throwable {
> new TestCase()
> .nodes(1)
> .nodesToUpgrade(1)
> .withConfig(config -> config.with(NETWORK, GOSSIP,
> NATIVE_PROTOCOL))
> .upgradesToCurrentFrom(v41)
> .setup((cluster) -> {
> cluster.schemaChange(withKeyspace("CREATE KEYSPACE %s
> WITH replication = {'class': 'SimpleStrategy', 'replication_factor': 2}"));
> }).runAfterNodeUpgrade((cluster, node) -> {
> // let's do nothing here.
> }).run();
> }
> } {code}
> Run the test with
> {code:java}
> $ ant test-jvm-dtest-some-Duse.jdk11=true
> -Dtest.name=org.apache.cassandra.distributed.upgrade.demoUpgradeTest {code}
> You will see the following failure:
> {code:java}
> [junit-timeout] Testcase:
> demoTest(org.apache.cassandra.distributed.upgrade.demoUpgradeTest)-_jdk11:
> Caused an ERROR
> [junit-timeout] Cannot add existing keyspace "distributed_test_keyspace"
> [junit-timeout] org.apache.cassandra.exceptions.AlreadyExistsException:
> Cannot add existing keyspace "distributed_test_keyspace"
> [junit-timeout] at
> org.apache.cassandra.cql3.statements.schema.CreateKeyspaceStatement.apply(CreateKeyspaceStatement.java:78)
> [junit-timeout] at
> org.apache.cassandra.schema.DefaultSchemaUpdateHandler.apply(DefaultSchemaUpdateHandler.java:230)
> [junit-timeout] at
> org.apache.cassandra.schema.Schema.transform(Schema.java:597)
> [junit-timeout] at
> org.apache.cassandra.cql3.statements.schema.AlterSchemaStatement.execute(AlterSchemaStatement.java:114)
> [junit-timeout] at
> org.apache.cassandra.cql3.statements.schema.AlterSchemaStatement.execute(AlterSchemaStatement.java:60)
> [junit-timeout] at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:122)
> [junit-timeout] at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:103)
> [junit-timeout] at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:66)
> [junit-timeout] at
> org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61)
> [junit-timeout] at
> org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71)
> [junit-timeout] at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> [junit-timeout] at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> [junit-timeout] at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> [junit-timeout] at java.base/java.lang.Thread.run(Thread.java:829) {code}
> I have tested version pairs 4.1.3_4.1.4, 4.1.4_4.1.5, 4.1.5_5.0-alpha1, and
> 5.0-alpha1_5.0-alpha2. All of them have the same issue.
> I wrote a very similar test with Cassandra distributed test framework
> (non-upgrade test) as below:
> {code:java}
> package org.apache.cassandra.distributed.test.streaming;public class
> LCSStreamingKeepLevelTest extends TestBaseImpl
> {
> @Test
> public void demoTest() throws IOException
> {
> try (Cluster cluster = builder().withNodes(1)
> .withConfig(config -> config.with(NETWORK, GOSSIP,
> NATIVE_PROTOCOL))
> .start())
> {
> cluster.schemaChange(withKeyspace("CREATE KEYSPACE %s WITH
> replication = {'class': 'SimpleStrategy', 'replication_factor': 2}"));
>
(cassandra) branch trunk updated: Reconfigure CMS after replacement, bootstrap and move operations
This is an automated email from the ASF dual-hosted git repository.
marcuse 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 cbe07fd57e Reconfigure CMS after replacement, bootstrap and move
operations
cbe07fd57e is described below
commit cbe07fd57e3d94a1f2512fced3f38e69ad4b3eb2
Author: Marcus Eriksson
AuthorDate: Thu Jun 13 16:21:42 2024 +0200
Reconfigure CMS after replacement, bootstrap and move operations
Patch by marcuse; reviewed by Sam Tunnicliffe for CASSANDRA-19705
---
CHANGES.txt| 1 +
.../org/apache/cassandra/metrics/TCMMetrics.java | 7 ++
.../org/apache/cassandra/tcm/CMSOperations.java| 27 +++--
.../cassandra/tcm/ClusterMetadataService.java | 14 ++-
.../cassandra/tcm/sequences/BootstrapAndJoin.java | 4 +-
.../tcm/sequences/BootstrapAndReplace.java | 5 +-
.../org/apache/cassandra/tcm/sequences/Move.java | 5 +-
.../cms/PrepareCMSReconfiguration.java | 27 +
.../apache/cassandra/tools/nodetool/CMSAdmin.java | 27 +++--
.../test/tcm/CMSPlacementAfterBootstrapTest.java | 62
.../test/tcm/CMSPlacementAfterMoveTest.java| 56 +++
.../test/tcm/CMSPlacementAfterReplacementTest.java | 110 +
12 files changed, 324 insertions(+), 21 deletions(-)
diff --git a/CHANGES.txt b/CHANGES.txt
index e33d453ade..e37528d201 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
5.1
+ * Reconfigure CMS after replacement, bootstrap and move operations
(CASSANDRA-19705)
* Support querying LocalStrategy tables with any partitioner (CASSANDRA-19692)
* Relax slow_query_log_timeout for MultiNodeSAITest (CASSANDRA-19693)
* Audit Log entries are missing identity for mTLS connections
(CASSANDRA-19669)
diff --git a/src/java/org/apache/cassandra/metrics/TCMMetrics.java
b/src/java/org/apache/cassandra/metrics/TCMMetrics.java
index 134a1a34e2..29858ead80 100644
--- a/src/java/org/apache/cassandra/metrics/TCMMetrics.java
+++ b/src/java/org/apache/cassandra/metrics/TCMMetrics.java
@@ -30,6 +30,7 @@ import org.apache.cassandra.tcm.Epoch;
import org.apache.cassandra.utils.FBUtilities;
import static org.apache.cassandra.metrics.CassandraMetricsRegistry.Metrics;
+import static
org.apache.cassandra.tcm.transformations.cms.PrepareCMSReconfiguration.needsReconfiguration;
public class TCMMetrics
{
@@ -42,6 +43,7 @@ public class TCMMetrics
public final Gauge currentCMSSize;
public final Gauge unreachableCMSMembers;
public final Gauge isCMSMember;
+public final Gauge needsCMSReconfiguration;
public final Histogram fetchedPeerLogEntries;
public final Histogram fetchedCMSLogEntries;
public final Timer fetchPeerLogLatency;
@@ -91,6 +93,11 @@ public class TCMMetrics
return metadata != null &&
metadata.isCMSMember(FBUtilities.getBroadcastAddressAndPort()) ? 1 : 0;
});
+needsCMSReconfiguration =
Metrics.register(factory.createMetricName("NeedsCMSReconfiguration"), () -> {
+ClusterMetadata metadata = ClusterMetadata.currentNullable();
+return metadata != null && needsReconfiguration(metadata) ? 1 : 0;
+});
+
fetchedPeerLogEntries =
Metrics.histogram(factory.createMetricName("FetchedPeerLogEntries"), false);
fetchPeerLogLatency =
Metrics.timer(factory.createMetricName("FetchPeerLogLatency"));
fetchedCMSLogEntries =
Metrics.histogram(factory.createMetricName("FetchedCMSLogEntries"), false);
diff --git a/src/java/org/apache/cassandra/tcm/CMSOperations.java
b/src/java/org/apache/cassandra/tcm/CMSOperations.java
index 0d9f4915ea..2211a2bb3d 100644
--- a/src/java/org/apache/cassandra/tcm/CMSOperations.java
+++ b/src/java/org/apache/cassandra/tcm/CMSOperations.java
@@ -41,12 +41,22 @@ import org.apache.cassandra.tcm.sequences.ReconfigureCMS;
import org.apache.cassandra.tcm.serialization.Version;
import org.apache.cassandra.tcm.transformations.Unregister;
import org.apache.cassandra.tcm.transformations.cms.AdvanceCMSReconfiguration;
+import org.apache.cassandra.tcm.transformations.cms.PrepareCMSReconfiguration;
import org.apache.cassandra.utils.FBUtilities;
import org.apache.cassandra.utils.MBeanWrapper;
public class CMSOperations implements CMSOperationsMBean
{
public static final String MBEAN_OBJECT_NAME =
"org.apache.cassandra.tcm:type=CMSOperations";
+public static final String MEMBERS = "MEMBERS";
+public static final String NEEDS_RECONFIGURATION = "NEEDS_RECONFIGURATION";
+public static final String IS_MEMBER = "IS_MEMBER";
+public static final String SERVICE_STATE = "SERVICE_STATE";
+public static final String IS_MIGRATING = "IS_MIGRATING";
+public static final String EPOCH = "EPOCH";
+public static final String LOCAL_PENDING = "LOCAL_PENDING";
+public static fin
[jira] [Updated] (CASSANDRA-19705) Reconfigure CMS after move/bootstrap/replacement
[
https://issues.apache.org/jira/browse/CASSANDRA-19705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19705:
Fix Version/s: 5.1-alpha1
(was: 5.x)
Source Control Link:
https://github.com/apache/cassandra/commit/cbe07fd57e3d94a1f2512fced3f38e69ad4b3eb2
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
committed, thanks!
> Reconfigure CMS after move/bootstrap/replacement
>
>
> Key: CASSANDRA-19705
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19705
> Project: Cassandra
> Issue Type: Improvement
> Components: Cluster/Membership
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.1-alpha1
>
> Attachments: ci_summary-1.html, ci_summary.html
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The CMS placement uses SimpleStrategy/NTS to decide where it is placed to
> make it easier to safely bounce a cluster using existing tools (with CMS
> placement {{dc1: 3, dc2: 3}} we will use the placements for min_token in a
> NetworkTopologyStrategy with the same replication setting).
> We need to reconfigure this after move/bootstrap/replacement though, since
> the placements might have changed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
