[cassandra-website] branch asf-staging updated (0e271508b -> 51cbd1644)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 0e271508b generate docs for f02aa10d new 51cbd1644 generate docs for f02aa10d 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 (0e271508b) \ N -- N -- N refs/heads/asf-staging (51cbd1644) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4852435 -> 4852435 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18708) Test failure: org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
[
https://issues.apache.org/jira/browse/CASSANDRA-18708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-18708:
Test and Documentation Plan:
Patch:
https://github.com/apache/cassandra/pull/2558/commits/fc7378072d1ca6b117fc3b56a4d7d3db4704ea5a
CI JDK11:
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2459/workflows/ea002384-b9ce-4360-bad1-f98cbf45e73e
CI JDK17:
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2459/workflows/ee61a0ae-b785-449e-a055-8d94e9035d87
J17 on J11 DTests failed due to some CircleCI problems - restarted and
completed successfully here -
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2459/workflows/75c48124-e607-4fbb-8b43-96f87334c87e
RefCountedTest logs do not contain any inaccessibleObjects exceptions
Status: Patch Available (was: In Progress)
> Test failure:
> org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
>
>
> Key: CASSANDRA-18708
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18708
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.x
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1650/testReport/junit/org.apache.cassandra.tools/StandaloneSplitterWithCQLTesterTest/testNoSnapshotOption__jdk17/]
> h3.
> {code:java}
> Error Message
> java.lang.reflect.InaccessibleObjectException: Unable to make field private
> final sun.nio.fs.UnixFileSystem sun.nio.fs.UnixPath.fs accessible: module
> java.base does not "opens sun.nio.fs" to unnamed module @1f28c152 at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178)
> at java.base/java.lang.reflect.Field.setAccessible(Field.java:172) at
> org.apache.cassandra.utils.concurrent.Ref.getFields(Ref.java:656) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.traverse(Ref.java:613) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.run(Ref.java:568) at
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
> at
> java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:833)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18708) Test failure: org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
[
https://issues.apache.org/jira/browse/CASSANDRA-18708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-18708:
Test and Documentation Plan:
Patch:
https://github.com/apache/cassandra/pull/2558/commits/fc7378072d1ca6b117fc3b56a4d7d3db4704ea5a
CI JDK11:
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2459/workflows/ea002384-b9ce-4360-bad1-f98cbf45e73e
CI JDK17:
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2459/workflows/ee61a0ae-b785-449e-a055-8d94e9035d87
J17 on J11 DTests failed due to some CircleCI problems - restarted and
completed successfully here -
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2459/workflows/75c48124-e607-4fbb-8b43-96f87334c87e
RefCountedTest logs do not contain any InaccessibleObjectsException exceptions
was:
Patch:
https://github.com/apache/cassandra/pull/2558/commits/fc7378072d1ca6b117fc3b56a4d7d3db4704ea5a
CI JDK11:
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2459/workflows/ea002384-b9ce-4360-bad1-f98cbf45e73e
CI JDK17:
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2459/workflows/ee61a0ae-b785-449e-a055-8d94e9035d87
J17 on J11 DTests failed due to some CircleCI problems - restarted and
completed successfully here -
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2459/workflows/75c48124-e607-4fbb-8b43-96f87334c87e
RefCountedTest logs do not contain any inaccessibleObjects exceptions
> Test failure:
> org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
>
>
> Key: CASSANDRA-18708
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18708
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.x
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1650/testReport/junit/org.apache.cassandra.tools/StandaloneSplitterWithCQLTesterTest/testNoSnapshotOption__jdk17/]
> h3.
> {code:java}
> Error Message
> java.lang.reflect.InaccessibleObjectException: Unable to make field private
> final sun.nio.fs.UnixFileSystem sun.nio.fs.UnixPath.fs accessible: module
> java.base does not "opens sun.nio.fs" to unnamed module @1f28c152 at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178)
> at java.base/java.lang.reflect.Field.setAccessible(Field.java:172) at
> org.apache.cassandra.utils.concurrent.Ref.getFields(Ref.java:656) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.traverse(Ref.java:613) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.run(Ref.java:568) at
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
> at
> java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:833)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18708) Test failure: org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
[
https://issues.apache.org/jira/browse/CASSANDRA-18708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752225#comment-17752225
]
Ekaterina Dimitrova commented on CASSANDRA-18708:
-
I can see the same error in the logs when we run RefCountedTest. The tests
succeed, but we see the error printed from
[here|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/utils/concurrent/Ref.java#L571-L574]
StandaloneSplitterWithCQLTesterTest is explicitly checking tool logs for
errors. Thus this class fails occasionally.
To solve the problem, we can use Unsafe. Unfortunately, this might not work in
rare cases - not accessible lambda, and when we move to post-15 Java, Cassandra
builds with records and hidden classes. (Unsafe#objectFieldOffset in Java 17
throws UnsupportedOperationException when it sees a hidden class(lambda is
implemented using hidden classes) or record).
I also added a new exception type for more clarity -
UnaccessibleFieldException. Jamm has almost the same one, but the name is
CannotAccessFieldException. I intentionally made those two with different names
to avoid confusing them in the code/logs.
I considered adding a utility class, but I do not want to encourage people to
use Unsafe tricks broadly.
With the proposed patch, I saw no more exceptions in the RefCountedTest logs.
The patch is highly influenced by what was done in Jamm. [~blerer], do you mind
reviewing?
Patch:
https://github.com/apache/cassandra/pull/2558/commits/fc7378072d1ca6b117fc3b56a4d7d3db4704ea5a
CI JDK11:
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2459/workflows/ea002384-b9ce-4360-bad1-f98cbf45e73e
CI JDK17:
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2459/workflows/ee61a0ae-b785-449e-a055-8d94e9035d87
J17 on J11 DTests failed due to some CircleCI problems - restarted and
completed successfully here -
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2459/workflows/75c48124-e607-4fbb-8b43-96f87334c87e
> Test failure:
> org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
>
>
> Key: CASSANDRA-18708
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18708
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.x
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1650/testReport/junit/org.apache.cassandra.tools/StandaloneSplitterWithCQLTesterTest/testNoSnapshotOption__jdk17/]
> h3.
> {code:java}
> Error Message
> java.lang.reflect.InaccessibleObjectException: Unable to make field private
> final sun.nio.fs.UnixFileSystem sun.nio.fs.UnixPath.fs accessible: module
> java.base does not "opens sun.nio.fs" to unnamed module @1f28c152 at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178)
> at java.base/java.lang.reflect.Field.setAccessible(Field.java:172) at
> org.apache.cassandra.utils.concurrent.Ref.getFields(Ref.java:656) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.traverse(Ref.java:613) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.run(Ref.java:568) at
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
> at
> java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:833)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17684) MacOS install should include cql.html local help file
[
https://issues.apache.org/jira/browse/CASSANDRA-17684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Schoening updated CASSANDRA-17684:
---
Mentor: Brad Schoening
> MacOS install should include cql.html local help file
> -
>
> Key: CASSANDRA-17684
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17684
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Interpreter
>Reporter: Brad Schoening
>Assignee: Vineet Gali
>Priority: Normal
> Fix For: 5.x
>
>
> On MacOS, /usr/share is not writable – even by root. Instead,
> /usr/local/share is the preferred location.
> The current share directory path is /usr/share/doc/cassandra/CQL.html. This
> would just add an alternative path.
> Using a list comprehension would simplify the current code. E.g.,
> {quote}import pathlib
> HTML_FALLBACK = 'https://cassandra.apache.org/doc/latest/cql/index.html'
> loc = ( Path('./doc/cql3/CQL.html'),
> Path('/usr/share/doc/cassandra/CQL.html'),
> Path('{color:#4c9aff}/usr/local/share{color}/doc/cassandra/CQL.html' ))
> item = next((x.as_uri() for x in loc if os.path.exists( x )), HTML_FALLBACK)
> {quote}
> Homebrew doesn't install the doc files, so this would likely need either
> a) added to homebrew in
> [https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/cassandra.rb]
> or
> b) installed with pip's setup.cql and accessed with Python's
> [importlib.resources|https://docs.python.org/3/library/importlib.resources.html]
--
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-17684) MacOS install should include cql.html local help file
[
https://issues.apache.org/jira/browse/CASSANDRA-17684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Schoening updated CASSANDRA-17684:
---
Summary: MacOS install should include cql.html local help file (was: MacOS
install should include cql.html on-line help file)
> MacOS install should include cql.html local help file
> -
>
> Key: CASSANDRA-17684
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17684
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Interpreter
>Reporter: Brad Schoening
>Assignee: Vineet Gali
>Priority: Normal
> Fix For: 5.x
>
>
> On MacOS, /usr/share is not writable – even by root. Instead,
> /usr/local/share is the preferred location.
> The current share directory path is /usr/share/doc/cassandra/CQL.html. This
> would just add an alternative path.
> Using a list comprehension would simplify the current code. E.g.,
> {quote}import pathlib
> HTML_FALLBACK = 'https://cassandra.apache.org/doc/latest/cql/index.html'
> loc = ( Path('./doc/cql3/CQL.html'),
> Path('/usr/share/doc/cassandra/CQL.html'),
> Path('{color:#4c9aff}/usr/local/share{color}/doc/cassandra/CQL.html' ))
> item = next((x.as_uri() for x in loc if os.path.exists( x )), HTML_FALLBACK)
> {quote}
> Homebrew doesn't install the doc files, so this would likely need either
> a) added to homebrew in
> [https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/cassandra.rb]
> or
> b) installed with pip's setup.cql and accessed with Python's
> [importlib.resources|https://docs.python.org/3/library/importlib.resources.html]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (b03ca387 -> 0e271508)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard b03ca387 generate docs for f02aa10d new 0e271508 generate docs for f02aa10d 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 (b03ca387) \ N -- N -- N refs/heads/asf-staging (0e271508) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4852435 -> 4852435 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17992) Upgrade Netty on 5.0
[ https://issues.apache.org/jira/browse/CASSANDRA-17992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17992: Authors: Ekaterina Dimitrova, Jacek Lewandowski (was: Jacek Lewandowski) > Upgrade Netty on 5.0 > > > Key: CASSANDRA-17992 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17992 > Project: Cassandra > Issue Type: Task > Components: Dependencies >Reporter: Ekaterina Dimitrova >Assignee: Jacek Lewandowski >Priority: Normal > Fix For: 5.0 > > Attachments: important-netty-inter-releases.md, > netty-release-notes-filtered.md, netty-release-notes.md, signature.asc > > Time Spent: 1h > Remaining Estimate: 0h > > I haven't been able to identify from the Netty docs which was the lowest > version where JDK17 was added but we are about 40 versions behind in netty 4 > so I suspect we better update. > -We need to consider there was an issue with class cast exceptions when > building with JDK17 with newer versions of netty (the newest available in > March 2022). For the record, we didn't see those when running CI on JDK8 and > JDK11. We also need to carefully revise the changes between the netty > versions. -->- CASSANDRA-18180 > Upgrading will cover also a fix in netty that was discussed in > [this|https://the-asf.slack.com/archives/CK23JSY2K/p1665567660202989] ASF > Slack thread. > CC [~benedict] , [~aleksey] -- 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-18692) [Cassandra Analytics] Fix bulk writes with Buffered RowBufferMode
[
https://issues.apache.org/jira/browse/CASSANDRA-18692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yifan Cai updated CASSANDRA-18692:
--
Fix Version/s: NA
Since Version: NA
Source Control Link:
https://github.com/apache/cassandra-analytics/commit/82b3c0a79c9322142738a4ec2ff7d4d4c0be2370
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> [Cassandra Analytics] Fix bulk writes with Buffered RowBufferMode
> --
>
> Key: CASSANDRA-18692
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18692
> Project: Cassandra
> Issue Type: Bug
> Components: Analytics Library
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Fix For: NA
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When setting {{Buffered}} {{RowBufferMode}} as part of the {{WriterOption's}}
> , {{org.apache.cassandra.spark.bulkwriter.RecordWriter}} ignores that
> configuration and uses the batch size to finalize an SSTable and start using
> a new one if new rows are available.
--
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-18692) [Cassandra Analytics] Fix bulk writes with Buffered RowBufferMode
[
https://issues.apache.org/jira/browse/CASSANDRA-18692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yifan Cai updated CASSANDRA-18692:
--
Status: Ready to Commit (was: Review In Progress)
> [Cassandra Analytics] Fix bulk writes with Buffered RowBufferMode
> --
>
> Key: CASSANDRA-18692
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18692
> Project: Cassandra
> Issue Type: Bug
> Components: Analytics Library
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When setting {{Buffered}} {{RowBufferMode}} as part of the {{WriterOption's}}
> , {{org.apache.cassandra.spark.bulkwriter.RecordWriter}} ignores that
> configuration and uses the batch size to finalize an SSTable and start using
> a new one if new rows are available.
--
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-analytics] branch trunk updated: CASSANDRA-18692 Fix bulk writes with Buffered RowBufferMode
This is an automated email from the ASF dual-hosted git repository.
ycai pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-analytics.git
The following commit(s) were added to refs/heads/trunk by this push:
new 82b3c0a CASSANDRA-18692 Fix bulk writes with Buffered RowBufferMode
82b3c0a is described below
commit 82b3c0a79c9322142738a4ec2ff7d4d4c0be2370
Author: Francisco Guerrero
AuthorDate: Tue Jul 25 12:41:10 2023 -0700
CASSANDRA-18692 Fix bulk writes with Buffered RowBufferMode
When setting Buffered RowBufferMode as part of the `WriterOption`s,
`org.apache.cassandra.spark.bulkwriter.RecordWriter` ignores that
configuration and instead
uses the batch size to determine when to finalize an SSTable and start
writing a new SSTable,
if more rows are available.
In this commit, we fix
`org.apache.cassandra.spark.bulkwriter.RecordWriter#checkBatchSize`
to take into account the configured `RowBufferMode`. And in specific to the
case of the
`UNBUFFERED` RowBufferMode, we check then the batchSize of the SSTable
during writes, and for
the case of `BUFFERED` that check will take no effect.
Co-authored-by: Doug Rohrer
Patch by Francisco Guerrero, Doug Rohrer; Reviewed by Dinesh Joshi, Yifan
Cai for CASSANDRA-18692
---
CHANGES.txt| 1 +
build.gradle | 8 +-
.../cassandra/spark/bulkwriter/BulkSparkConf.java | 1 +
.../bulkwriter/CassandraBulkWriterContext.java | 15 --
.../spark/bulkwriter/CassandraJobInfo.java | 2 +
.../apache/cassandra/spark/bulkwriter/JobInfo.java | 3 +
.../cassandra/spark/bulkwriter/RecordWriter.java | 34 +--
.../cassandra/spark/bulkwriter/SSTableWriter.java | 19 +-
.../spark/bulkwriter/SSTableWriterFactory.java | 5 +-
.../cassandra/spark/data/CassandraDataLayer.java | 243 +++--
.../clients/SidecarNativeLibrariesTest.java} | 22 +-
.../spark/bulkwriter/BulkSparkConfTest.java| 3 +-
.../spark/bulkwriter/CassandraRingMonitorTest.java | 2 +-
.../spark/bulkwriter/MockBulkWriterContext.java| 21 +-
.../bulkwriter/NonValidatingTestSSTableWriter.java | 4 +-
.../spark/bulkwriter/RecordWriterTest.java | 60 -
.../cassandra/spark/bulkwriter/RingUtils.java | 34 ++-
.../spark/bulkwriter/SSTableWriterTest.java| 6 +-
.../bulkwriter/StreamSessionConsistencyTest.java | 2 -
.../spark/bulkwriter/StreamSessionTest.java| 2 +-
.../spark/bulkwriter/TokenPartitionerTest.java | 12 +-
.../apache/cassandra/bridge/CassandraBridge.java | 2 +-
.../apache/cassandra/bridge}/RowBufferMode.java| 17 +-
cassandra-four-zero/build.gradle | 11 +-
.../bridge/CassandraBridgeImplementation.java | 4 +-
.../bridge/SSTableWriterImplementation.java| 47 +++-
.../bridge/SSTableWriterImplementationTest.java| 103 +
.../apache/cassandra/utils/ReflectionUtils.java| 65 ++
28 files changed, 506 insertions(+), 242 deletions(-)
diff --git a/CHANGES.txt b/CHANGES.txt
index afbb30a..41e2b04 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
1.0.0
+ * Fix bulk writes with Buffered RowBufferMode (CASSANDRA-18692)
* Minor Refactoring to Improve Code Reusability (CASSANDRA-18684)
* Fix cassandra-analytics-core-example (CASSANDRA-18662)
* Added caching of Node Settings to improve efficiency (CASSANDRA-18633)
diff --git a/build.gradle b/build.gradle
index 5772b48..837c6fe 100644
--- a/build.gradle
+++ b/build.gradle
@@ -20,16 +20,10 @@
import java.nio.file.Files
import java.nio.file.Paths
-buildscript {
- dependencies {
-classpath(group: 'com.github.jengelman.gradle.plugins', name: 'shadow',
version: '6.1.0')
- }
-}
-
plugins {
id 'java'
id 'java-library'
- id 'com.github.johnrengelman.shadow' version '5.1.0'
+ id 'com.github.johnrengelman.shadow' version '7.1.2'
// Release Audit Tool (RAT) plugin for checking project licenses
id("org.nosphere.apache.rat") version "0.8.0"
diff --git
a/cassandra-analytics-core/src/main/java/org/apache/cassandra/spark/bulkwriter/BulkSparkConf.java
b/cassandra-analytics-core/src/main/java/org/apache/cassandra/spark/bulkwriter/BulkSparkConf.java
index a719df7..798f259 100644
---
a/cassandra-analytics-core/src/main/java/org/apache/cassandra/spark/bulkwriter/BulkSparkConf.java
+++
b/cassandra-analytics-core/src/main/java/org/apache/cassandra/spark/bulkwriter/BulkSparkConf.java
@@ -37,6 +37,7 @@ import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.apache.cassandra.bridge.CassandraBridgeFactory;
+import org.apache.cassandra.bridge.RowBufferMode;
import org.apache.cassandra.clients.SidecarInstanceImpl;
import org.apache.cassandra.sidecar.client.SidecarInstance;
import org.apache.cassandra.spark.bulkwriter.token.ConsistencyLevel;
diff --git
[jira] [Commented] (CASSANDRA-18692) [Cassandra Analytics] Fix bulk writes with Buffered RowBufferMode
[
https://issues.apache.org/jira/browse/CASSANDRA-18692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752185#comment-17752185
]
Yifan Cai commented on CASSANDRA-18692:
---
+1 on the patch!
> [Cassandra Analytics] Fix bulk writes with Buffered RowBufferMode
> --
>
> Key: CASSANDRA-18692
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18692
> Project: Cassandra
> Issue Type: Bug
> Components: Analytics Library
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When setting {{Buffered}} {{RowBufferMode}} as part of the {{WriterOption's}}
> , {{org.apache.cassandra.spark.bulkwriter.RecordWriter}} ignores that
> configuration and uses the batch size to finalize an SSTable and start using
> a new one if new rows are available.
--
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
[GitHub] [cassandra-analytics] JeetKunDoug commented on a diff in pull request #13: CASSANDRA-18692 Fix bulk writes with Buffered RowBufferMode
JeetKunDoug commented on code in PR #13:
URL:
https://github.com/apache/cassandra-analytics/pull/13#discussion_r1287708124
##
cassandra-four-zero/src/main/java/org/apache/cassandra/bridge/SSTableWriterImplementation.java:
##
@@ -80,4 +79,28 @@ public void close() throws IOException
{
writer.close();
}
+
+@VisibleForTesting
+static CQLSSTableWriter.Builder configureBuilder(String inDirectory,
+ String createStatement,
+ String insertStatement,
+ RowBufferMode
rowBufferMode,
+ int bufferSizeMB,
+ IPartitioner
cassPartitioner)
+{
+CQLSSTableWriter.Builder builder = CQLSSTableWriter.builder()
+
.inDirectory(inDirectory)
+
.forTable(createStatement)
+
.withPartitioner(cassPartitioner)
+
.using(insertStatement);
+if (rowBufferMode == RowBufferMode.UNBUFFERED)
+{
+builder.sorted();
+}
+else if (rowBufferMode == RowBufferMode.BUFFERED)
+{
+builder.withBufferSizeInMB(bufferSizeMB);
Review Comment:
I think, for now, we leave this just a configuration option... Validating it
given the Spark environment and picking a reasonable upper-bound would take
some experimentation (and would likely involve more than just the
executor.memory setting, as there are other config settings that deal w/ memory
like memory overhead).
--
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
[GitHub] [cassandra-analytics] JeetKunDoug commented on a diff in pull request #13: CASSANDRA-18692 Fix bulk writes with Buffered RowBufferMode
JeetKunDoug commented on code in PR #13:
URL:
https://github.com/apache/cassandra-analytics/pull/13#discussion_r1287705006
##
cassandra-analytics-core/src/main/java/org/apache/cassandra/spark/bulkwriter/RecordWriter.java:
##
@@ -114,16 +115,21 @@ public StreamResult write(Iterator> sourceIterato
checkBatchSize(streamSession, partitionId, job);
}
-if (batchSize != 0)
+if (sstableWriter != null)
{
- finalizeSSTable(streamSession, partitionId, sstableWriter,
batchNumber, batchSize);
+finalizeSSTable(streamSession, partitionId, sstableWriter,
batchNumber, batchSize);
Review Comment:
Given this is essentially the last step before we're done with the
sstablewriter, we don't really need to set the sstablewriter to null here -
this RecordWriter instance should be collected as soon as the upload/commits
finish, and we close the sstablewriter on finalize so we should be good w/o
nulling it out.
--
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
[GitHub] [cassandra-analytics] yifan-c commented on a diff in pull request #13: CASSANDRA-18692 Fix bulk writes with Buffered RowBufferMode
yifan-c commented on code in PR #13:
URL:
https://github.com/apache/cassandra-analytics/pull/13#discussion_r1287667789
##
cassandra-four-zero/src/main/java/org/apache/cassandra/bridge/SSTableWriterImplementation.java:
##
@@ -80,4 +79,28 @@ public void close() throws IOException
{
writer.close();
}
+
+@VisibleForTesting
+static CQLSSTableWriter.Builder configureBuilder(String inDirectory,
+ String createStatement,
+ String insertStatement,
+ RowBufferMode
rowBufferMode,
+ int bufferSizeMB,
+ IPartitioner
cassPartitioner)
+{
+CQLSSTableWriter.Builder builder = CQLSSTableWriter.builder()
+
.inDirectory(inDirectory)
+
.forTable(createStatement)
+
.withPartitioner(cassPartitioner)
+
.using(insertStatement);
+if (rowBufferMode == RowBufferMode.UNBUFFERED)
+{
+builder.sorted();
+}
+else if (rowBufferMode == RowBufferMode.BUFFERED)
+{
+builder.withBufferSizeInMB(bufferSizeMB);
Review Comment:
nit: maybe decide a valid value range for `bufferSizeMB` and validate.
`CQLSSTableWriter` accepts whatever int value.
For the upper bound, I think 1/2 of the `spark.executor.memory` is a good
limit.
##
cassandra-analytics-core/src/main/java/org/apache/cassandra/spark/bulkwriter/RecordWriter.java:
##
@@ -114,16 +115,21 @@ public StreamResult write(Iterator> sourceIterato
checkBatchSize(streamSession, partitionId, job);
}
-if (batchSize != 0)
+if (sstableWriter != null)
{
- finalizeSSTable(streamSession, partitionId, sstableWriter,
batchNumber, batchSize);
+finalizeSSTable(streamSession, partitionId, sstableWriter,
batchNumber, batchSize);
Review Comment:
nit: reset `sstableWriter` to `null` after `finalizeSSTable`
--
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-18529) Remove legacy command line options from cassandra-stress
[ https://issues.apache.org/jira/browse/CASSANDRA-18529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752176#comment-17752176 ] Stefan Miklosovic commented on CASSANDRA-18529: --- [~timothytu] [~bschoeni] could you please remind why we decided to go with "unprepared" when using "native" by default? As I read the original code, I see that "native" has "prepared" by default and unprepared when "unprepared" flag is specified. Contrary, "simplenative" has it other way around. By here we want to introduce native and by default unprepared? more here https://github.com/driftx/cassandra/commit/3759d0826e5d92624f0af5de6f861d070897f4ee#r123969698 > Remove legacy command line options from cassandra-stress > > > Key: CASSANDRA-18529 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18529 > Project: Cassandra > Issue Type: Improvement > Components: Tool/stress >Reporter: Brad Schoening >Assignee: Timothy Tu >Priority: Low > Fix For: 5.x > > Attachments: signature.asc, signature.asc > > > The cassandra-stress *mode* option allows specifying options for native > protocol and cql3, but these don't seem useful as there would seem to be no > other valid options now that cql3 is the standard and thrift no longer > supported. > -mode native cql3 user=cassandra password=xx > can be simplified to: > -mode user=cassandra password=xx > Also, the readme.txt in tools/stress states "cassandra-stress supports > benchmarking any Cassandra cluster of version 2.0+" but maybe should be > updated to a supported Cassandra version, i.e., 3.11.x. -- 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-18692) [Cassandra Analytics] Fix bulk writes with Buffered RowBufferMode
[
https://issues.apache.org/jira/browse/CASSANDRA-18692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Joshi updated CASSANDRA-18692:
-
Reviewers: Dinesh Joshi, Yifan Cai (was: Dinesh Joshi, Yifan Cai, Yifan
Cai)
> [Cassandra Analytics] Fix bulk writes with Buffered RowBufferMode
> --
>
> Key: CASSANDRA-18692
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18692
> Project: Cassandra
> Issue Type: Bug
> Components: Analytics Library
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When setting {{Buffered}} {{RowBufferMode}} as part of the {{WriterOption's}}
> , {{org.apache.cassandra.spark.bulkwriter.RecordWriter}} ignores that
> configuration and uses the batch size to finalize an SSTable and start using
> a new one if new rows are available.
--
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-18692) [Cassandra Analytics] Fix bulk writes with Buffered RowBufferMode
[
https://issues.apache.org/jira/browse/CASSANDRA-18692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752174#comment-17752174
]
Dinesh Joshi commented on CASSANDRA-18692:
--
Branch: https://github.com/frankgh/cassandra-analytics/tree/CASSANDRA-18692
+1, thanks for the patch.
> [Cassandra Analytics] Fix bulk writes with Buffered RowBufferMode
> --
>
> Key: CASSANDRA-18692
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18692
> Project: Cassandra
> Issue Type: Bug
> Components: Analytics Library
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When setting {{Buffered}} {{RowBufferMode}} as part of the {{WriterOption's}}
> , {{org.apache.cassandra.spark.bulkwriter.RecordWriter}} ignores that
> configuration and uses the batch size to finalize an SSTable and start using
> a new one if new rows are available.
--
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-18727) JMXUtil.getJmxConnector should retry connection attempts
[ https://issues.apache.org/jira/browse/CASSANDRA-18727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752172#comment-17752172 ] Jon Meredith commented on CASSANDRA-18727: -- +1 > JMXUtil.getJmxConnector should retry connection attempts > - > > Key: CASSANDRA-18727 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18727 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/java >Reporter: Doug Rohrer >Assignee: Doug Rohrer >Priority: Normal > Labels: pull-request-available > > We previously added a JMXUtil class that makes it easy for dtests to get a > JMX connection. It ends up that occasionally the JMX server side needs more > time to start up (especially when stopping and restarting instances, which > we’re now doing more frequently, or when stopping and restarting the whole > cluster). In these cases, JMXUtil.getJmxConnector can fail, when it would be > possible to connect if a retry mechanism was added. We should add this > capability to the in-jvm dtest framework. > -- 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-18621) Update Cassandra logos on ASF project logos site
[ https://issues.apache.org/jira/browse/CASSANDRA-18621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick McFadin updated CASSANDRA-18621: Component/s: Legacy/Documentation and Website > Update Cassandra logos on ASF project logos site > > > Key: CASSANDRA-18621 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18621 > Project: Cassandra > Issue Type: Task > Components: Legacy/Documentation and Website >Reporter: Melissa Logan >Assignee: Melissa Logan >Priority: Normal > Attachments: Cassandra_R.zip > > > It appears that the Cassandra logos on the ASF project logos website are > outdated, as they include lowercase letters and no trademark: > https://www.apache.org/logos/#cassandra > The logo currently being used on the website is this one: > https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/images/logo-white.svg > To ensure proper usage by contributors and third parties, I propose the > creation of the following logo set based on the current website logo: > Version 1 - update and create black and white versions > Version 2- remove > Version 3 - update and create black and white versions > Version 4 - no change > If these already exist somewhere, then please upload them to the ASF project > logos page (requires a committer): https://www.apache.org/logos/about.html > Otherwise I will be asking our designer to create hi-res versions to be > uploaded. -- 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-18580) Baseline Metrics for Accord Transactions
[
https://issues.apache.org/jira/browse/CASSANDRA-18580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751746#comment-17751746
]
Jacek Lewandowski edited comment on CASSANDRA-18580 at 8/8/23 8:21 PM:
---
thanks [~maedhroz], so far I have those:
measured on a replica:
- time to commit
- time to execute
- time to apply
- application time (how long did writes take)
- partial deps histogram
measured on a coordinator:
- dependencies histogram
- fast path meter
- slow path meter
- preempted transactions meter
- timeouts meter
- time to recover (which is a timer + meter, so the number )
- something computed as current timestamp measured after the recovery minus
ballot as a timestamp (though need to investigate if it makes any sense)
all of that is separated for read-only and rw transactions (based on flags in
TxnId)
I'm happy to add the missing one: size of the progress log and size of commands
for key when loaded
was (Author: jlewandowski):
thanks [~maedhroz], so far I have those:
measured on a replica:
- time to commit
- time to execute
- time to apply
- application time (how long did writes take)
- partial deps histogram
measured on a coordinator:
- dependencies histogram
- fast path meter
- slow path meter
- preempted transactions meter
- timeouts meter
- time to recover (which is a timer + meter, so the number )
- something computed as current timestamp measured after the recovery minus
ballot as a timestamp (though need to investigate if it makes any sense)
all of that is separated for read-only and rw transactions (based on flags in
TxnId)
I'm happy to add the missing one: side of the progress log and size of commands
for key when loaded
> Baseline Metrics for Accord Transactions
>
>
> Key: CASSANDRA-18580
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18580
> Project: Cassandra
> Issue Type: Improvement
> Components: Accord, Observability/JMX, Observability/Metrics
>Reporter: Caleb Rackliffe
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Based on some conversations w/ [~benedict] and [~dcapwell], this is the
> initial set of metrics that seem both feasible to implement and useful as we
> monitor the health of a cluster performing Accord transactions:
> 1.) Basic latency metrics for transactions up to the point of COMMIT and rate
> metrics for preemption, failure, and timeouts at the coordinator.
> This has already been implemented and split into read and write-specific
> metrics. Our position for now is that metrics around preemption should be
> useful in place of a more difficult-to-define metric around how many
> transactions are completed via recovery.
> 2.) Global cache stats/metrics (i.e. aggregated for all command stores)
> We could, at some point, build metrics scoped to a specific {{CommandStore}},
> but they might be awkward in MBean/JMX space, as command stores would have to
> be identified by ID or key range…the latter possibly being able to change
> across epochs. (An alternative would be just publishing command
> store-specific stats on-demand to a virtual table instead.)
> 3.) Something like a decaying histogram of the number of dependencies per
> transaction (or per partial transaction).
> If this is getting worse over time, it could be useful to know/be a way for
> us to detect that contention is increasing. We should be able to hook this up
> to {{ProgressLog}} notifications. Recording for PartialDeps/PartialTxn (which
> ProgressLog gives us at pre-accept) seems acceptable, given this is a
> directional metric.
--
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-18727) JMXUtil.getJmxConnector should retry connection attempts
[ https://issues.apache.org/jira/browse/CASSANDRA-18727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752169#comment-17752169 ] Dinesh Joshi commented on CASSANDRA-18727: -- +1, thanks for the patch. > JMXUtil.getJmxConnector should retry connection attempts > - > > Key: CASSANDRA-18727 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18727 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/java >Reporter: Doug Rohrer >Assignee: Doug Rohrer >Priority: Normal > Labels: pull-request-available > > We previously added a JMXUtil class that makes it easy for dtests to get a > JMX connection. It ends up that occasionally the JMX server side needs more > time to start up (especially when stopping and restarting instances, which > we’re now doing more frequently, or when stopping and restarting the whole > cluster). In these cases, JMXUtil.getJmxConnector can fail, when it would be > possible to connect if a retry mechanism was added. We should add this > capability to the in-jvm dtest framework. > -- 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-18727) JMXUtil.getJmxConnector should retry connection attempts
[ https://issues.apache.org/jira/browse/CASSANDRA-18727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Joshi updated CASSANDRA-18727: - Reviewers: Alex Petrov, Dinesh Joshi, Jon Meredith (was: Alex Petrov, Jon Meredith) > JMXUtil.getJmxConnector should retry connection attempts > - > > Key: CASSANDRA-18727 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18727 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/java >Reporter: Doug Rohrer >Assignee: Doug Rohrer >Priority: Normal > Labels: pull-request-available > > We previously added a JMXUtil class that makes it easy for dtests to get a > JMX connection. It ends up that occasionally the JMX server side needs more > time to start up (especially when stopping and restarting instances, which > we’re now doing more frequently, or when stopping and restarting the whole > cluster). In these cases, JMXUtil.getJmxConnector can fail, when it would be > possible to connect if a retry mechanism was added. We should add this > capability to the in-jvm dtest framework. > -- 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-18736) Streaming exception race creates corrupt transaction log files that prevent restart
[
https://issues.apache.org/jira/browse/CASSANDRA-18736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Meredith updated CASSANDRA-18736:
-
Bug Category: Parent values: Availability(12983)Level 1 values: Process
Crash(12992)
Complexity: Normal
Discovered By: User Report
Fix Version/s: 4.0.x
4.1.x
5.0
Severity: Low
Status: Open (was: Triage Needed)
> Streaming exception race creates corrupt transaction log files that prevent
> restart
> ---
>
> Key: CASSANDRA-18736
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18736
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Streaming, Local/Startup and Shutdown
>Reporter: Jon Meredith
>Assignee: Jon Meredith
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0
>
>
> On restart, Cassandra logs this message and terminates.
> {code:java}
> ERROR 2023-07-17T17:17:22,931 [main]
> org.apache.cassandra.db.lifecycle.LogTransaction:561 - Unexpected disk state:
> failed to read transaction log
> [nb_txn_stream_39d5f6b0-fb81-11ed-8f46-e97b3f61511e.log in
> /datadir1/keyspace/table-c9527530a0d611e8813f034699fc9043]
> Files and contents follow:
> /datadir1/keyspace/table-c9527530a0d611e8813f034699fc9043/nb_txn_stream_39d5f6b0-fb81-11ed-8f46-e97b3f61511e.log
> ABORT:[,0,0][737437348]
> ***This record should have been the last one in all replicas
>
> ADD:[/datadir1/keyspace/table-c9527530a0d611e8813f034699fc9043/nb-284490-big-,0,8][2493503833]
> {code}
> The root cause is a race during streaming exception handling.
> Although concurrent modification of to the {{LogTransaction}} was added for
> CASSANDRA-16225, there is nothing to prevent usage after the transaction is
> completed (committed/aborted) once it has been processed by
> {{TransactionTidier}} (after the last reference is released). Before the
> transaction is tidied, the {{LogFile}} keeps a list of records that are
> checked for completion before adding new entries. In {{TransactionTidier}}
> {{LogFile.records}} are cleared as no longer needed, however the
> LogTransaction/LogFile is still accessible to the stream.
> The changes in CASSANDRA-17273 added a parallel set of {{onDiskRecords}} that
> could be used to reliably recreate the transaction log at any new datadirs
> the same as the existing
> datadirs - regardless of the effect of
> {{LogTransaction.untrackNew/LogFile.remove}}
> If a streaming exception causes the LogTransaction to be aborted and tidied
> just before {{SimpleSSTableMultiWriter}} calls trackNew to add a new sstable.
> At the time of the call, the {{LogFile}} will not contain any {{LogReplicas}},
> {{LogFile.records}} will be empty, and {{LogFile.onDiskRecords}} will contain
> an {{ABORT}}.
> When {{LogTransaction.trackNew/LogFile.add}} is called, the check for
> completed transaction fails as records is empty, there are no replicas on the
> datadir, so {{maybeCreateReplicas}} creates a new txnlog file replica
> containing ABORT, then
> appends an ADD record.
> The LogFile has already been tidied after the abort so the txnlog file is not
> removed and sits on disk until a restart, causing the faiulre.
> There is a related exception caused with a different interleaving of aborts,
> after an sstable is added, however this is just a nuisance in the logs as the
> LogRelica is already created with an {{ADD}} record first.
> {code:java}
> java.lang.AssertionError:
> [ADD:[/datadir1/keyspace/table/nb-23314378-big-,0,8][1869379820]] is not
> tracked by 55be35b0-35d1-11ee-865d-8b1e3c48ca06
> at org.apache.cassandra.db.lifecycle.LogFile.remove(LogFile.java:388)
> at
> org.apache.cassandra.db.lifecycle.LogTransaction.untrackNew(LogTransaction.java:158)
> at
> org.apache.cassandra.db.lifecycle.LifecycleTransaction.untrackNew(LifecycleTransaction.java:577)
> at
> org.apache.cassandra.db.streaming.CassandraStreamReceiver$1.untrackNew(CassandraStreamReceiver.java:149)
> at
> org.apache.cassandra.io.sstable.SimpleSSTableMultiWriter.abort(SimpleSSTableMultiWriter.java:95)
> at
> org.apache.cassandra.io.sstable.format.RangeAwareSSTableWriter.abort(RangeAwareSSTableWriter.java:191)
> at
> org.apache.cassandra.db.streaming.CassandraCompressedStreamReader.read(CassandraCompressedStreamReader.java:115)
> at
> org.apache.cassandra.db.streaming.CassandraIncomingFile.read(CassandraIncomingFile.java:85)
> at
> org.apache.cassandra.streaming.messages.IncomingStreamMessage$1.deserialize(IncomingStreamMessage.java:53)
> at
> org.apache.cassandra.streaming.messages.IncomingStreamMessage$1.deserialize(IncomingStreamMessage.java:38)
>
[jira] [Created] (CASSANDRA-18736) Streaming exception race creates corrupt transaction log files that prevent restart
Jon Meredith created CASSANDRA-18736:
Summary: Streaming exception race creates corrupt transaction log
files that prevent restart
Key: CASSANDRA-18736
URL: https://issues.apache.org/jira/browse/CASSANDRA-18736
Project: Cassandra
Issue Type: Bug
Components: Consistency/Streaming, Local/Startup and Shutdown
Reporter: Jon Meredith
Assignee: Jon Meredith
On restart, Cassandra logs this message and terminates.
{code:java}
ERROR 2023-07-17T17:17:22,931 [main]
org.apache.cassandra.db.lifecycle.LogTransaction:561 - Unexpected disk state:
failed to read transaction log
[nb_txn_stream_39d5f6b0-fb81-11ed-8f46-e97b3f61511e.log in
/datadir1/keyspace/table-c9527530a0d611e8813f034699fc9043]
Files and contents follow:
/datadir1/keyspace/table-c9527530a0d611e8813f034699fc9043/nb_txn_stream_39d5f6b0-fb81-11ed-8f46-e97b3f61511e.log
ABORT:[,0,0][737437348]
***This record should have been the last one in all replicas
ADD:[/datadir1/keyspace/table-c9527530a0d611e8813f034699fc9043/nb-284490-big-,0,8][2493503833]
{code}
The root cause is a race during streaming exception handling.
Although concurrent modification of to the {{LogTransaction}} was added for
CASSANDRA-16225, there is nothing to prevent usage after the transaction is
completed (committed/aborted) once it has been processed by
{{TransactionTidier}} (after the last reference is released). Before the
transaction is tidied, the {{LogFile}} keeps a list of records that are checked
for completion before adding new entries. In {{TransactionTidier}}
{{LogFile.records}} are cleared as no longer needed, however the
LogTransaction/LogFile is still accessible to the stream.
The changes in CASSANDRA-17273 added a parallel set of {{onDiskRecords}} that
could be used to reliably recreate the transaction log at any new datadirs the
same as the existing
datadirs - regardless of the effect of
{{LogTransaction.untrackNew/LogFile.remove}}
If a streaming exception causes the LogTransaction to be aborted and tidied
just before {{SimpleSSTableMultiWriter}} calls trackNew to add a new sstable.
At the time of the call, the {{LogFile}} will not contain any {{LogReplicas}},
{{LogFile.records}} will be empty, and {{LogFile.onDiskRecords}} will contain
an {{ABORT}}.
When {{LogTransaction.trackNew/LogFile.add}} is called, the check for completed
transaction fails as records is empty, there are no replicas on the datadir, so
{{maybeCreateReplicas}} creates a new txnlog file replica containing ABORT, then
appends an ADD record.
The LogFile has already been tidied after the abort so the txnlog file is not
removed and sits on disk until a restart, causing the faiulre.
There is a related exception caused with a different interleaving of aborts,
after an sstable is added, however this is just a nuisance in the logs as the
LogRelica is already created with an {{ADD}} record first.
{code:java}
java.lang.AssertionError:
[ADD:[/datadir1/keyspace/table/nb-23314378-big-,0,8][1869379820]] is not
tracked by 55be35b0-35d1-11ee-865d-8b1e3c48ca06
at org.apache.cassandra.db.lifecycle.LogFile.remove(LogFile.java:388)
at
org.apache.cassandra.db.lifecycle.LogTransaction.untrackNew(LogTransaction.java:158)
at
org.apache.cassandra.db.lifecycle.LifecycleTransaction.untrackNew(LifecycleTransaction.java:577)
at
org.apache.cassandra.db.streaming.CassandraStreamReceiver$1.untrackNew(CassandraStreamReceiver.java:149)
at
org.apache.cassandra.io.sstable.SimpleSSTableMultiWriter.abort(SimpleSSTableMultiWriter.java:95)
at
org.apache.cassandra.io.sstable.format.RangeAwareSSTableWriter.abort(RangeAwareSSTableWriter.java:191)
at
org.apache.cassandra.db.streaming.CassandraCompressedStreamReader.read(CassandraCompressedStreamReader.java:115)
at
org.apache.cassandra.db.streaming.CassandraIncomingFile.read(CassandraIncomingFile.java:85)
at
org.apache.cassandra.streaming.messages.IncomingStreamMessage$1.deserialize(IncomingStreamMessage.java:53)
at
org.apache.cassandra.streaming.messages.IncomingStreamMessage$1.deserialize(IncomingStreamMessage.java:38)
at
org.apache.cassandra.streaming.messages.StreamMessage.deserialize(StreamMessage.java:53)
at
org.apache.cassandra.streaming.async.StreamingInboundHandler$StreamDeserializingTask.run(StreamingInboundHandler.java:172)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:829)
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18676) CorruptedSSTablesCompactionsTest is flaky
[
https://issues.apache.org/jira/browse/CASSANDRA-18676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752165#comment-17752165
]
Ekaterina Dimitrova commented on CASSANDRA-18676:
-
FYI, Opened ticket CASSANDRA-18676 for the failures
> CorruptedSSTablesCompactionsTest is flaky
> -
>
> Key: CASSANDRA-18676
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18676
> Project: Cassandra
> Issue Type: Bug
> Components: Local/SSTable, Test/unit
>Reporter: Branimir Lambov
>Assignee: Branimir Lambov
>Priority: Normal
> Fix For: 5.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> See e.g. [this
> run|https://app.circleci.com/pipelines/github/blambov/cassandra/510/workflows/fd484f76-b0f0-48c9-8672-d73bdc36b8ec/jobs/13575/tests].
> The test was looked at for CASSANDRA-15879, but it is still failing from time
> to time. One of the failures appears to be introduced by CASSANDRA-14227 and
> the others by CASSANDRA-18134. The failures are genuine problems with
> handling corruption, not just test issues.
> The {{CorruptSSTableException}} paths in {{SSTableIdentityIterator}} should
> likely also catch {{AssertionError}} and {{IllegalArgumentException}}, and
> most probably the tombstone verification should be done on the read path.
--
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-18676) CorruptedSSTablesCompactionsTest is flaky
[
https://issues.apache.org/jira/browse/CASSANDRA-18676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752165#comment-17752165
]
Ekaterina Dimitrova edited comment on CASSANDRA-18676 at 8/8/23 7:49 PM:
-
FYI, Opened ticket CASSANDRA-18735 for the failures
was (Author: e.dimitrova):
FYI, Opened ticket CASSANDRA-18676 for the failures
> CorruptedSSTablesCompactionsTest is flaky
> -
>
> Key: CASSANDRA-18676
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18676
> Project: Cassandra
> Issue Type: Bug
> Components: Local/SSTable, Test/unit
>Reporter: Branimir Lambov
>Assignee: Branimir Lambov
>Priority: Normal
> Fix For: 5.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> See e.g. [this
> run|https://app.circleci.com/pipelines/github/blambov/cassandra/510/workflows/fd484f76-b0f0-48c9-8672-d73bdc36b8ec/jobs/13575/tests].
> The test was looked at for CASSANDRA-15879, but it is still failing from time
> to time. One of the failures appears to be introduced by CASSANDRA-14227 and
> the others by CASSANDRA-18134. The failures are genuine problems with
> handling corruption, not just test issues.
> The {{CorruptSSTableException}} paths in {{SSTableIdentityIterator}} should
> likely also catch {{AssertionError}} and {{IllegalArgumentException}}, and
> most probably the tombstone verification should be done on the read path.
--
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-18735) Test failure: Fix Python DTests post CASSANDRA-18676
[ https://issues.apache.org/jira/browse/CASSANDRA-18735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752164#comment-17752164 ] Ekaterina Dimitrova commented on CASSANDRA-18735: - CC [~blambov] and [~Bereng] > Test failure: Fix Python DTests post CASSANDRA-18676 > > > Key: CASSANDRA-18735 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18735 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 5.x > > > From Butler: > |failling|DTEST|u.cql_tests > |[TestCQLNodes3RF3_Upgrade_current_4_1_x_To_indev_trunk.test_negative_timestamp > (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_current_4_1_x_To_indev_trunk/test_negative_timestamp]| > |failing|DTEST|u.cql_tests > |[TestCQLNodes2RF1_Upgrade_indev_4_0_x_To_indev_trunk.test_negative_timestamp > (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_indev_4_0_x_To_indev_trunk/test_negative_timestamp]| > |failing|DTEST|u.cql_tests |[cls.test_negative_timestamp (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/cls/test_negative_timestamp]| > |failing|DTEST|u.cql_tests > |[TestCQLNodes3RF3_Upgrade_indev_4_1_x_To_indev_trunk.test_negative_timestamp > (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_indev_4_1_x_To_indev_trunk/test_negative_timestamp]| > |failing|DTEST|u.cql_tests > |[TestCQLNodes3RF3_Upgrade_indev_4_0_x_To_indev_trunk.test_negative_timestamp > (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_indev_4_0_x_To_indev_trunk/test_negative_timestamp]| > |failing|DTEST|u.cql_tests > |[TestCQLNodes3RF3_Upgrade_current_4_0_x_To_indev_trunk.test_negative_timestamp > (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_current_4_0_x_To_indev_trunk/test_negative_timestamp]| > |failing|DTEST|u.cql_tests > |[TestCQLNodes2RF1_Upgrade_current_4_0_x_To_indev_trunk.test_negative_timestamp > (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_current_4_0_x_To_indev_trunk/test_negative_timestamp]| > |failing|DTEST|u.cql_tests > |[TestCQLNodes2RF1_Upgrade_current_4_1_x_To_indev_trunk.test_negative_timestamp > (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_current_4_1_x_To_indev_trunk/test_negative_timestamp]| > |failing|DTEST|u.cql_tests > |[TestCQLNodes2RF1_Upgrade_indev_4_1_x_To_indev_trunk.test_negative_timestamp > (upgrade)|https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_indev_4_1_x_To_indev_trunk/test_negative_timestamp]| -- 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-18735) Test failure: Fix Python DTests post CASSANDRA-18676
[ https://issues.apache.org/jira/browse/CASSANDRA-18735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-18735: Bug Category: Parent values: Correctness(12982)Level 1 values: Test Failure(12990) Complexity: Normal Component/s: CI Discovered By: User Report Severity: Normal Status: Open (was: Triage Needed) > Test failure: Fix Python DTests post CASSANDRA-18676 > > > Key: CASSANDRA-18735 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18735 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Priority: Normal > > From Butler: > |failling|DTEST|u.cql_tests > |[TestCQLNodes3RF3_Upgrade_current_4_1_x_To_indev_trunk.test_negative_timestamp > (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_current_4_1_x_To_indev_trunk/test_negative_timestamp]| > |failing|DTEST|u.cql_tests > |[TestCQLNodes2RF1_Upgrade_indev_4_0_x_To_indev_trunk.test_negative_timestamp > (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_indev_4_0_x_To_indev_trunk/test_negative_timestamp]| > |failing|DTEST|u.cql_tests |[cls.test_negative_timestamp (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/cls/test_negative_timestamp]| > |failing|DTEST|u.cql_tests > |[TestCQLNodes3RF3_Upgrade_indev_4_1_x_To_indev_trunk.test_negative_timestamp > (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_indev_4_1_x_To_indev_trunk/test_negative_timestamp]| > |failing|DTEST|u.cql_tests > |[TestCQLNodes3RF3_Upgrade_indev_4_0_x_To_indev_trunk.test_negative_timestamp > (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_indev_4_0_x_To_indev_trunk/test_negative_timestamp]| > |failing|DTEST|u.cql_tests > |[TestCQLNodes3RF3_Upgrade_current_4_0_x_To_indev_trunk.test_negative_timestamp > (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_current_4_0_x_To_indev_trunk/test_negative_timestamp]| > |failing|DTEST|u.cql_tests > |[TestCQLNodes2RF1_Upgrade_current_4_0_x_To_indev_trunk.test_negative_timestamp > (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_current_4_0_x_To_indev_trunk/test_negative_timestamp]| > |failing|DTEST|u.cql_tests > |[TestCQLNodes2RF1_Upgrade_current_4_1_x_To_indev_trunk.test_negative_timestamp > (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_current_4_1_x_To_indev_trunk/test_negative_timestamp]| > |failing|DTEST|u.cql_tests > |[TestCQLNodes2RF1_Upgrade_indev_4_1_x_To_indev_trunk.test_negative_timestamp > (upgrade)|https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_indev_4_1_x_To_indev_trunk/test_negative_timestamp]| -- 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-18735) Test failure: Fix Python DTests post CASSANDRA-18676
[ https://issues.apache.org/jira/browse/CASSANDRA-18735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-18735: Fix Version/s: 5.x > Test failure: Fix Python DTests post CASSANDRA-18676 > > > Key: CASSANDRA-18735 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18735 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 5.x > > > From Butler: > |failling|DTEST|u.cql_tests > |[TestCQLNodes3RF3_Upgrade_current_4_1_x_To_indev_trunk.test_negative_timestamp > (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_current_4_1_x_To_indev_trunk/test_negative_timestamp]| > |failing|DTEST|u.cql_tests > |[TestCQLNodes2RF1_Upgrade_indev_4_0_x_To_indev_trunk.test_negative_timestamp > (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_indev_4_0_x_To_indev_trunk/test_negative_timestamp]| > |failing|DTEST|u.cql_tests |[cls.test_negative_timestamp (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/cls/test_negative_timestamp]| > |failing|DTEST|u.cql_tests > |[TestCQLNodes3RF3_Upgrade_indev_4_1_x_To_indev_trunk.test_negative_timestamp > (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_indev_4_1_x_To_indev_trunk/test_negative_timestamp]| > |failing|DTEST|u.cql_tests > |[TestCQLNodes3RF3_Upgrade_indev_4_0_x_To_indev_trunk.test_negative_timestamp > (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_indev_4_0_x_To_indev_trunk/test_negative_timestamp]| > |failing|DTEST|u.cql_tests > |[TestCQLNodes3RF3_Upgrade_current_4_0_x_To_indev_trunk.test_negative_timestamp > (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_current_4_0_x_To_indev_trunk/test_negative_timestamp]| > |failing|DTEST|u.cql_tests > |[TestCQLNodes2RF1_Upgrade_current_4_0_x_To_indev_trunk.test_negative_timestamp > (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_current_4_0_x_To_indev_trunk/test_negative_timestamp]| > |failing|DTEST|u.cql_tests > |[TestCQLNodes2RF1_Upgrade_current_4_1_x_To_indev_trunk.test_negative_timestamp > (upgrade) > |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_current_4_1_x_To_indev_trunk/test_negative_timestamp]| > |failing|DTEST|u.cql_tests > |[TestCQLNodes2RF1_Upgrade_indev_4_1_x_To_indev_trunk.test_negative_timestamp > (upgrade)|https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_indev_4_1_x_To_indev_trunk/test_negative_timestamp]| -- 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-18735) Test failure: Fix Python DTests post CASSANDRA-18676
Ekaterina Dimitrova created CASSANDRA-18735: --- Summary: Test failure: Fix Python DTests post CASSANDRA-18676 Key: CASSANDRA-18735 URL: https://issues.apache.org/jira/browse/CASSANDRA-18735 Project: Cassandra Issue Type: Bug Reporter: Ekaterina Dimitrova >From Butler: |failling|DTEST|u.cql_tests |[TestCQLNodes3RF3_Upgrade_current_4_1_x_To_indev_trunk.test_negative_timestamp (upgrade) |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_current_4_1_x_To_indev_trunk/test_negative_timestamp]| |failing|DTEST|u.cql_tests |[TestCQLNodes2RF1_Upgrade_indev_4_0_x_To_indev_trunk.test_negative_timestamp (upgrade) |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_indev_4_0_x_To_indev_trunk/test_negative_timestamp]| |failing|DTEST|u.cql_tests |[cls.test_negative_timestamp (upgrade) |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/cls/test_negative_timestamp]| |failing|DTEST|u.cql_tests |[TestCQLNodes3RF3_Upgrade_indev_4_1_x_To_indev_trunk.test_negative_timestamp (upgrade) |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_indev_4_1_x_To_indev_trunk/test_negative_timestamp]| |failing|DTEST|u.cql_tests |[TestCQLNodes3RF3_Upgrade_indev_4_0_x_To_indev_trunk.test_negative_timestamp (upgrade) |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_indev_4_0_x_To_indev_trunk/test_negative_timestamp]| |failing|DTEST|u.cql_tests |[TestCQLNodes3RF3_Upgrade_current_4_0_x_To_indev_trunk.test_negative_timestamp (upgrade) |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_current_4_0_x_To_indev_trunk/test_negative_timestamp]| |failing|DTEST|u.cql_tests |[TestCQLNodes2RF1_Upgrade_current_4_0_x_To_indev_trunk.test_negative_timestamp (upgrade) |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_current_4_0_x_To_indev_trunk/test_negative_timestamp]| |failing|DTEST|u.cql_tests |[TestCQLNodes2RF1_Upgrade_current_4_1_x_To_indev_trunk.test_negative_timestamp (upgrade) |https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_current_4_1_x_To_indev_trunk/test_negative_timestamp]| |failing|DTEST|u.cql_tests |[TestCQLNodes2RF1_Upgrade_indev_4_1_x_To_indev_trunk.test_negative_timestamp (upgrade)|https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_indev_4_1_x_To_indev_trunk/test_negative_timestamp]| -- 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-17667) Text value containing "/*" interpreted as multiline comment in cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-17667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vineet Gali updated CASSANDRA-17667:
Mentor: Attila Homoki (was: Brad Schoening)
> Text value containing "/*" interpreted as multiline comment in cqlsh
>
>
> Key: CASSANDRA-17667
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17667
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: ANOOP THOMAS
>Assignee: Vineet Gali
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.x
>
>
> I use CQLSH command line utility to load some DDLs. The version of utility I
> use is this:
> {noformat}
> [cqlsh 6.0.0 | Cassandra 4.0.0.47 | CQL spec 3.4.5 | Native protocol
> v5]{noformat}
> Command that loads DDL.cql:
> {noformat}
> cqlsh -u username -p password cassandra.example.com 65503 --ssl -f DDL.cql
> {noformat}
> I have a line in CQL script that breaks the syntax.
> {noformat}
> INSERT into tablename (key,columnname1,columnname2) VALUES
> ('keyName','value1','/value2/*/value3');{noformat}
> {{/*}} here is interpreted as start of multi-line comment. It used to work on
> older versions of cqlsh. The error I see looks like this:
> {noformat}
> SyntaxException: line 4:2 mismatched input 'Update' expecting ')'
> (...,'value1','/value2INSERT into tablename(INSERT into tablename
> (key,columnname1,columnname2)) VALUES ('[Update]-...) SyntaxException: line
> 1:0 no viable alternative at input '(' ([(]...)
> {noformat}
> Same behavior while running in interactive mode too. {{/*}} inside a CQL
> statement should not be interpreted as start of multi-line comment.
> With schema:
> {code:java}
> CREATE TABLE tablename ( key text primary key, columnname1 text, columnname2
> text);{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17667) Text value containing "/*" interpreted as multiline comment in cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-17667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vineet Gali updated CASSANDRA-17667:
Mentor: Brad Schoening
> Text value containing "/*" interpreted as multiline comment in cqlsh
>
>
> Key: CASSANDRA-17667
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17667
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: ANOOP THOMAS
>Assignee: Vineet Gali
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.x
>
>
> I use CQLSH command line utility to load some DDLs. The version of utility I
> use is this:
> {noformat}
> [cqlsh 6.0.0 | Cassandra 4.0.0.47 | CQL spec 3.4.5 | Native protocol
> v5]{noformat}
> Command that loads DDL.cql:
> {noformat}
> cqlsh -u username -p password cassandra.example.com 65503 --ssl -f DDL.cql
> {noformat}
> I have a line in CQL script that breaks the syntax.
> {noformat}
> INSERT into tablename (key,columnname1,columnname2) VALUES
> ('keyName','value1','/value2/*/value3');{noformat}
> {{/*}} here is interpreted as start of multi-line comment. It used to work on
> older versions of cqlsh. The error I see looks like this:
> {noformat}
> SyntaxException: line 4:2 mismatched input 'Update' expecting ')'
> (...,'value1','/value2INSERT into tablename(INSERT into tablename
> (key,columnname1,columnname2)) VALUES ('[Update]-...) SyntaxException: line
> 1:0 no viable alternative at input '(' ([(]...)
> {noformat}
> Same behavior while running in interactive mode too. {{/*}} inside a CQL
> statement should not be interpreted as start of multi-line comment.
> With schema:
> {code:java}
> CREATE TABLE tablename ( key text primary key, columnname1 text, columnname2
> text);{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17667) Text value containing "/*" interpreted as multiline comment in cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-17667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vineet Gali reassigned CASSANDRA-17667:
---
Assignee: Vineet Gali
> Text value containing "/*" interpreted as multiline comment in cqlsh
>
>
> Key: CASSANDRA-17667
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17667
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: ANOOP THOMAS
>Assignee: Vineet Gali
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.x
>
>
> I use CQLSH command line utility to load some DDLs. The version of utility I
> use is this:
> {noformat}
> [cqlsh 6.0.0 | Cassandra 4.0.0.47 | CQL spec 3.4.5 | Native protocol
> v5]{noformat}
> Command that loads DDL.cql:
> {noformat}
> cqlsh -u username -p password cassandra.example.com 65503 --ssl -f DDL.cql
> {noformat}
> I have a line in CQL script that breaks the syntax.
> {noformat}
> INSERT into tablename (key,columnname1,columnname2) VALUES
> ('keyName','value1','/value2/*/value3');{noformat}
> {{/*}} here is interpreted as start of multi-line comment. It used to work on
> older versions of cqlsh. The error I see looks like this:
> {noformat}
> SyntaxException: line 4:2 mismatched input 'Update' expecting ')'
> (...,'value1','/value2INSERT into tablename(INSERT into tablename
> (key,columnname1,columnname2)) VALUES ('[Update]-...) SyntaxException: line
> 1:0 no viable alternative at input '(' ([(]...)
> {noformat}
> Same behavior while running in interactive mode too. {{/*}} inside a CQL
> statement should not be interpreted as start of multi-line comment.
> With schema:
> {code:java}
> CREATE TABLE tablename ( key text primary key, columnname1 text, columnname2
> text);{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-18051) Optimize and fix flaky test_network_topology_strategy and test_network_topology_strategy_each_quorum for large containers in CircleCI
[
https://issues.apache.org/jira/browse/CASSANDRA-18051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova reassigned CASSANDRA-18051:
---
Assignee: (was: Ekaterina Dimitrova)
> Optimize and fix flaky test_network_topology_strategy and
> test_network_topology_strategy_each_quorum for large containers in CircleCI
> -
>
> Key: CASSANDRA-18051
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18051
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest/python
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
>
> As pointed in CASSANDRA-18001, there are two Python Large DTests that fail
> because of not enough resources with large containers. [~adelapena] looked
> into them and suggested that the tests themselves can be optimized for
> running on Large containers instead of using XLarge containers for only two
> tests from the whole suite.
> {quote}As for the two tests starting nine nodes each,
> {{test_network_topology_strategy}} and
> {{{}test_network_topology_strategy_each_quorum{}}}, I think they were added
> by CASSANDRA-10584 to test multi-DC consistency levels. I wonder if they
> actually need to start 3 data centers with 3 nodes each. Would two data
> centers with 3 nodes be enough to test multi-DC consistency levels with
> multiple data centers? 6 nodes should be doable on Circle with the current
> resources.
> {quote}
> EDIT: On further testing it was noticed that the tests also started failing
> on 3.0 and 3.11 even with XLarge containers and there might be also some
> timing issue further involved and to be investigated.
--
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-18621) Update Cassandra logos on ASF project logos site
[ https://issues.apache.org/jira/browse/CASSANDRA-18621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752159#comment-17752159 ] Melissa Logan commented on CASSANDRA-18621: --- A zip file with logos is attached. This includes updating the logo with the (R) as Cassandra is a registered trademark (versus TM which is for unregistered trademarks). An update to the homepage logo is also needed (PR coming soon). A committer is required to update these on the ASF project logos page as described here: https://www.apache.org/logos/about.html. Anyone? :) Note: The project logo page was recently made more visible in the recent apache.org navigation update. Having updating Cassandra logos here will help community members be in compliance with ASF legal policies. > Update Cassandra logos on ASF project logos site > > > Key: CASSANDRA-18621 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18621 > Project: Cassandra > Issue Type: Task >Reporter: Melissa Logan >Assignee: Melissa Logan >Priority: Normal > Attachments: Cassandra_R.zip > > > It appears that the Cassandra logos on the ASF project logos website are > outdated, as they include lowercase letters and no trademark: > https://www.apache.org/logos/#cassandra > The logo currently being used on the website is this one: > https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/images/logo-white.svg > To ensure proper usage by contributors and third parties, I propose the > creation of the following logo set based on the current website logo: > Version 1 - update and create black and white versions > Version 2- remove > Version 3 - update and create black and white versions > Version 4 - no change > If these already exist somewhere, then please upload them to the ASF project > logos page (requires a committer): https://www.apache.org/logos/about.html > Otherwise I will be asking our designer to create hi-res versions to be > uploaded. -- 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-18621) Update Cassandra logos on ASF project logos site
[ https://issues.apache.org/jira/browse/CASSANDRA-18621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Logan updated CASSANDRA-18621: -- Attachment: Cassandra_R.zip > Update Cassandra logos on ASF project logos site > > > Key: CASSANDRA-18621 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18621 > Project: Cassandra > Issue Type: Task >Reporter: Melissa Logan >Assignee: Melissa Logan >Priority: Normal > Attachments: Cassandra_R.zip > > > It appears that the Cassandra logos on the ASF project logos website are > outdated, as they include lowercase letters and no trademark: > https://www.apache.org/logos/#cassandra > The logo currently being used on the website is this one: > https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/images/logo-white.svg > To ensure proper usage by contributors and third parties, I propose the > creation of the following logo set based on the current website logo: > Version 1 - update and create black and white versions > Version 2- remove > Version 3 - update and create black and white versions > Version 4 - no change > If these already exist somewhere, then please upload them to the ASF project > logos page (requires a committer): https://www.apache.org/logos/about.html > Otherwise I will be asking our designer to create hi-res versions to be > uploaded. -- 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-18529) Remove legacy command line options from cassandra-stress
[ https://issues.apache.org/jira/browse/CASSANDRA-18529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752153#comment-17752153 ] Brandon Williams commented on CASSANDRA-18529: -- Looks good, my +1 stands. > Remove legacy command line options from cassandra-stress > > > Key: CASSANDRA-18529 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18529 > Project: Cassandra > Issue Type: Improvement > Components: Tool/stress >Reporter: Brad Schoening >Assignee: Timothy Tu >Priority: Low > Fix For: 5.x > > Attachments: signature.asc, signature.asc > > > The cassandra-stress *mode* option allows specifying options for native > protocol and cql3, but these don't seem useful as there would seem to be no > other valid options now that cql3 is the standard and thrift no longer > supported. > -mode native cql3 user=cassandra password=xx > can be simplified to: > -mode user=cassandra password=xx > Also, the readme.txt in tools/stress states "cassandra-stress supports > benchmarking any Cassandra cluster of version 2.0+" but maybe should be > updated to a supported Cassandra version, i.e., 3.11.x. -- 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-18692) [Cassandra Analytics] Fix bulk writes with Buffered RowBufferMode
[
https://issues.apache.org/jira/browse/CASSANDRA-18692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yifan Cai updated CASSANDRA-18692:
--
Reviewers: Dinesh Joshi, Yifan Cai, Yifan Cai
Status: Review In Progress (was: Patch Available)
> [Cassandra Analytics] Fix bulk writes with Buffered RowBufferMode
> --
>
> Key: CASSANDRA-18692
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18692
> Project: Cassandra
> Issue Type: Bug
> Components: Analytics Library
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When setting {{Buffered}} {{RowBufferMode}} as part of the {{WriterOption's}}
> , {{org.apache.cassandra.spark.bulkwriter.RecordWriter}} ignores that
> configuration and uses the batch size to finalize an SSTable and start using
> a new one if new rows are available.
--
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
[GitHub] [cassandra-analytics] dineshjoshi commented on pull request #13: CASSANDRA-18692 Fix bulk writes with Buffered RowBufferMode
dineshjoshi commented on PR #13: URL: https://github.com/apache/cassandra-analytics/pull/13#issuecomment-1670060605 +1 LGTM. -- 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] [Assigned] (CASSANDRA-18635) Fix flaky test: org.apache.cassandra.distributed.test.UpgradeSSTablesTest
[
https://issues.apache.org/jira/browse/CASSANDRA-18635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña reassigned CASSANDRA-18635:
-
Assignee: (was: Andres de la Peña)
> Fix flaky test: org.apache.cassandra.distributed.test.UpgradeSSTablesTest
> -
>
> Key: CASSANDRA-18635
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18635
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Brandon Williams
>Priority: Normal
> Fix For: 5.x
>
>
> Seen here:
> https://app.circleci.com/pipelines/github/driftx/cassandra/1095/workflows/6114e2e3-8dcc-4bb0-b664-ae7d82c3349f/jobs/33405/tests
> {noformat}
> junit.framework.AssertionFailedError: expected:<0> but was:<2>
> at
> org.apache.cassandra.distributed.test.UpgradeSSTablesTest.upgradeSSTablesInterruptsOngoingCompaction(UpgradeSSTablesTest.java:86)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18635) Fix flaky test: org.apache.cassandra.distributed.test.UpgradeSSTablesTest
[
https://issues.apache.org/jira/browse/CASSANDRA-18635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-18635:
--
Authors: (was: Andres de la Peña)
> Fix flaky test: org.apache.cassandra.distributed.test.UpgradeSSTablesTest
> -
>
> Key: CASSANDRA-18635
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18635
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Brandon Williams
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 5.x
>
>
> Seen here:
> https://app.circleci.com/pipelines/github/driftx/cassandra/1095/workflows/6114e2e3-8dcc-4bb0-b664-ae7d82c3349f/jobs/33405/tests
> {noformat}
> junit.framework.AssertionFailedError: expected:<0> but was:<2>
> at
> org.apache.cassandra.distributed.test.UpgradeSSTablesTest.upgradeSSTablesInterruptsOngoingCompaction(UpgradeSSTablesTest.java:86)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18635) Fix flaky test: org.apache.cassandra.distributed.test.UpgradeSSTablesTest
[
https://issues.apache.org/jira/browse/CASSANDRA-18635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752137#comment-17752137
]
Andres de la Peña commented on CASSANDRA-18635:
---
The test seems to be flaky since its introduction by CASSANDRA-17851
([377e114cb1459895423c292cb0bf7f921fd30e43|https://github.com/apache/cassandra/commit/377e114cb1459895423c292cb0bf7f921fd30e43]):
https://app.circleci.com/pipelines/github/adelapena/cassandra/3093/workflows/67c2fdec-1f07-4343-9482-150478cea032/jobs/66582/tests
CC [~ifesdjeen] [~jmckenzie]
> Fix flaky test: org.apache.cassandra.distributed.test.UpgradeSSTablesTest
> -
>
> Key: CASSANDRA-18635
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18635
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Brandon Williams
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 5.x
>
>
> Seen here:
> https://app.circleci.com/pipelines/github/driftx/cassandra/1095/workflows/6114e2e3-8dcc-4bb0-b664-ae7d82c3349f/jobs/33405/tests
> {noformat}
> junit.framework.AssertionFailedError: expected:<0> but was:<2>
> at
> org.apache.cassandra.distributed.test.UpgradeSSTablesTest.upgradeSSTablesInterruptsOngoingCompaction(UpgradeSSTablesTest.java:86)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11248) (windows) dtest failure in commitlog_test.TestCommitLog.stop_failure_policy_test and stop_commit_failure_policy_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-11248:
-
Resolution: Won't Fix
Status: Resolved (was: Open)
> (windows) dtest failure in
> commitlog_test.TestCommitLog.stop_failure_policy_test and
> stop_commit_failure_policy_test
>
>
> Key: CASSANDRA-11248
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11248
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest/python
>Reporter: Russ Hatch
>Priority: Normal
> Labels: dtest, windows
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest_win32/167/testReport/commitlog_test/TestCommitLog/stop_failure_policy_test
> Failed on CassCI build cassandra-2.2_dtest_win32 #167
> failing intermittently, looks possibly related to CASSANDRA-11242 with:
> {noformat}
> Cannot find the commitlog failure message in logs
> {noformat}
> But there's another suspect message here not present on 11242, which is
> {noformat}
> [node1 ERROR] Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file
> D:\jenkins\workspace\cassandra-2.2_dtest_win32\cassandra\/logs/gc.log due to
> No such file or directory
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11439) [windows] dtest failure in replication_test.SnitchConfigurationUpdateTest
[ https://issues.apache.org/jira/browse/CASSANDRA-11439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-11439: - Resolution: Won't Fix Status: Resolved (was: Open) > [windows] dtest failure in replication_test.SnitchConfigurationUpdateTest > - > > Key: CASSANDRA-11439 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11439 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/python >Reporter: Philip Thompson >Priority: Normal > Labels: dtest, windows > > Almost all of the SnitchConfigurationUpdateTests have begun failing on > windows, across all versions. > I suspect this is due to the recent CCM changes to use universal_newlines in > nodetool output, which was needed for Python3 functionality. I assume the > tests' expected output of the CCM functions just needs to be updated. > example failure: > http://cassci.datastax.com/job/cassandra-2.2_dtest_win32/213/testReport/replication_test/SnitchConfigurationUpdateTest/test_failed_snitch_update_gossiping_property_file_snitch > Failed on CassCI build cassandra-2.2_dtest_win32 #213 -- 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-10208) Windows dtest 2.2: commitlog_test.TestCommitLog.stop_failure_policy_test
[
https://issues.apache.org/jira/browse/CASSANDRA-10208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-10208:
-
Resolution: Won't Fix
Status: Resolved (was: Open)
> Windows dtest 2.2: commitlog_test.TestCommitLog.stop_failure_policy_test
>
>
> Key: CASSANDRA-10208
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10208
> Project: Cassandra
> Issue Type: Sub-task
>Reporter: Philip Thompson
>Assignee: Alan Boudreault
>Priority: Normal
> Labels: Windows
> Fix For: 2.2.x
>
>
> {{commitlog_test.TestCommitLog.stop_commit_failure_policy_test}} and
> {{commitlog_test.TestCommitLog.stop_failure_policy_test}} are failing here:
> http://cassci.datastax.com/job/cassandra-2.2_dtest_win32/72/testReport/#
> The stack trace is as follows:
> {code}
> File "C:\tools\python2\lib\unittest\case.py", line 329, in run
> testMethod()
> File
> "D:\jenkins\workspace\cassandra-2.2_dtest_win32\cassandra-dtest\commitlog_test.py",
> line 254, in stop_failure_policy_test
> self.assertTrue(failure, "Cannot find the commitlog failure message in
> logs")
> File "C:\tools\python2\lib\unittest\case.py", line 422, in assertTrue
> raise self.failureException(msg)
> 'Cannot find the commitlog failure message in logs
> {code}
> I can only reproduce the failure for {{stop_commit_failure_policy_test}}
> locally, but I assume that's just flakiness.
--
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-11251) (windows) dtest failure in putget_test.TestPutGet.non_local_read_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-11251:
-
Resolution: Won't Fix
Status: Resolved (was: Open)
> (windows) dtest failure in putget_test.TestPutGet.non_local_read_test
> -
>
> Key: CASSANDRA-11251
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11251
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest/python
>Reporter: Russ Hatch
>Priority: Normal
> Labels: dtest, windows
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest_win32/174/testReport/putget_test/TestPutGet/non_local_read_test
> Failed on CassCI build cassandra-2.2_dtest_win32 #174
> Failing intermittently, error:
> {noformat}
> code=1500 [Replica(s) failed to execute write] message="Operation failed -
> received 1 responses and 1 failures" info={'failures': 1,
> 'received_responses': 1, 'required_responses': 2, 'consistency': 'QUORUM'}
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11281) (windows) dtest failures with permission issues on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-11281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-11281: - Resolution: Won't Fix Status: Resolved (was: Open) > (windows) dtest failures with permission issues on trunk > > > Key: CASSANDRA-11281 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11281 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/python >Reporter: Russ Hatch >Priority: Normal > Labels: dtest, windows > > example failure: > http://cassci.datastax.com/job/trunk_dtest_win32/337/testReport/bootstrap_test/TestBootstrap/shutdown_wiped_node_cannot_join_test > Failed on CassCI build trunk_dtest_win32 #337 > Failing tests with very similar error messages: > * > compaction_test.TestCompaction_with_DateTieredCompactionStrategy.compaction_strategy_switching_test > * > compaction_test.TestCompaction_with_LeveledCompactionStrategy.compaction_strategy_switching_test > * bootstrap_test.TestBootstrap.shutdown_wiped_node_cannot_join_test > * bootstrap_test.TestBootstrap.killed_wiped_node_cannot_join_test > * bootstrap_test.TestBootstrap.decommissioned_wiped_node_can_join_test > * > bootstrap_test.TestBootstrap.decommissioned_wiped_node_can_gossip_to_single_seed_test > * bootstrap_test.TestBootstrap.failed_bootstrap_wiped_node_can_join_test -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11234) (windows) dtest failure in largecolumn_test.TestLargeColumn.cleanup_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-11234:
-
Resolution: Won't Fix
Status: Resolved (was: Open)
> (windows) dtest failure in largecolumn_test.TestLargeColumn.cleanup_test
>
>
> Key: CASSANDRA-11234
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11234
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest/python
>Reporter: Russ Hatch
>Priority: Normal
> Labels: dtest, windows
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest_win32/156/testReport/largecolumn_test/TestLargeColumn/cleanup_test
> Failed on CassCI build cassandra-2.2_dtest_win32 #156
> failing consistently
> looks like maybe a python platform issue or something:
> {noformat}
> Expected output from nodetool gcstats starts with a header line with first
> column Interval
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11266) (windows) dtest failure in read_repair_test.TestReadRepair.alter_rf_and_run_read_repair_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-11266:
-
Resolution: Won't Fix
Status: Resolved (was: Open)
> (windows) dtest failure in
> read_repair_test.TestReadRepair.alter_rf_and_run_read_repair_test
>
>
> Key: CASSANDRA-11266
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11266
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest/python
>Reporter: Russ Hatch
>Priority: Normal
> Labels: dtest, windows
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_dtest_win32/140/testReport/read_repair_test/TestReadRepair/alter_rf_and_run_read_repair_test
> Failed on CassCI build cassandra-3.0_dtest_win32 #140
> Failing on every run, looks like could be test or cassandra issue.
> {noformat}
> Couldn't identify initial replica
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11691) (windows) dtest failure in replace_address_test.TestReplaceAddress.fail_without_replace_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-11691:
-
Resolution: Won't Fix
Status: Resolved (was: Open)
> (windows) dtest failure in
> replace_address_test.TestReplaceAddress.fail_without_replace_test
>
>
> Key: CASSANDRA-11691
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11691
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest/python
>Reporter: Russ Hatch
>Priority: Normal
> Labels: dtest, windows
>
> looks to be a new test, first run failing with:
> {noformat}
> [Error 5] Access is denied:
> 'd:\\temp\\dtest-kof1fj\\test\\node3\\commitlogs\\CommitLog-6-1461863368272.log'
> {noformat}
> maybe a windows python compat issue?
> http://cassci.datastax.com/job/trunk_dtest_win32/401/testReport/replace_address_test/TestReplaceAddress/fail_without_replace_test
> Failed on CassCI build trunk_dtest_win32 #401
--
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-11242) (windows) dtest failure in commitlog_test.TestCommitLog.ignore_failure_policy_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-11242:
-
Resolution: Won't Fix
Status: Resolved (was: Open)
> (windows) dtest failure in
> commitlog_test.TestCommitLog.ignore_failure_policy_test
> --
>
> Key: CASSANDRA-11242
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11242
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest/python
>Reporter: Russ Hatch
>Priority: Normal
> Labels: dtest, windows
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest_win32/162/testReport/commitlog_test/TestCommitLog/ignore_failure_policy_test
> Failed on CassCI build cassandra-2.2_dtest_win32 #162
> looks like a probably test issue, failing intermittently, recent failure
> message:
> {noformat}
> Cannot find the commitlog failure message in logs
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11236) (windows) dtest failure in scrub_test.TestScrub.test_standalone_scrub
[
https://issues.apache.org/jira/browse/CASSANDRA-11236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-11236:
-
Resolution: Won't Fix
Status: Resolved (was: Open)
> (windows) dtest failure in scrub_test.TestScrub.test_standalone_scrub
> -
>
> Key: CASSANDRA-11236
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11236
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest/python
>Reporter: Russ Hatch
>Priority: Normal
> Labels: dtest, windows
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest_win32/156/testReport/scrub_test/TestScrub/test_standalone_scrub
> Failed on CassCI build cassandra-2.2_dtest_win32 #156
> Failing on every run on windows, with:
> {noformat}
> sstablescrub failed
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11241) (windows) dtest failure in jmx_test.TestJMX.phi_test
[ https://issues.apache.org/jira/browse/CASSANDRA-11241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-11241: - Resolution: Won't Fix Status: Resolved (was: Open) > (windows) dtest failure in jmx_test.TestJMX.phi_test > > > Key: CASSANDRA-11241 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11241 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/python >Reporter: Russ Hatch >Priority: Normal > Labels: dtest, windows > > example failure: > http://cassci.datastax.com/job/cassandra-2.2_dtest_win32/162/testReport/jmx_test/TestJMX/phi_test > Failed on CassCI build cassandra-2.2_dtest_win32 #162 > Looks like a probable test issue, failing every run. -- 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-11284) (windows) dtest failure trying to remove files
[ https://issues.apache.org/jira/browse/CASSANDRA-11284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-11284: - Resolution: Won't Fix Status: Resolved (was: Open) > (windows) dtest failure trying to remove files > -- > > Key: CASSANDRA-11284 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11284 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/python >Reporter: Russ Hatch >Priority: Normal > Labels: dtest, windows > > example failures: > http://cassci.datastax.com/job/trunk_dtest_win32/337/testReport/scrub_test/TestScrubIndexes/test_scrub_collections_table > http://cassci.datastax.com/job/trunk_dtest_win32/337/testReport/scrub_test/TestScrubIndexes/test_scrub_static_table/ > http://cassci.datastax.com/job/trunk_dtest_win32/342/testReport/scrub_test/TestScrub/test_nodetool_scrub/ > These tests are failing frequently but not every time, failure is unable to > delete files either because permission denied or does not exist. It's > possible these two tests are failing for differing reasons, but looks similar > enough to group on this ticket. -- 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-18733) Waiting indefinitely on ReceivedMessage response in StreamSession#receive() can cause deadlock
[
https://issues.apache.org/jira/browse/CASSANDRA-18733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe reassigned CASSANDRA-18733:
---
Assignee: Jon Meredith (was: Caleb Rackliffe)
> Waiting indefinitely on ReceivedMessage response in StreamSession#receive()
> can cause deadlock
> --
>
> Key: CASSANDRA-18733
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18733
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair, Consistency/Streaming
>Reporter: Caleb Rackliffe
>Assignee: Jon Meredith
>Priority: Normal
> Fix For: 4.1.x, 5.0, 5.x
>
>
> I've observed in a recent stack trace from a node running 4.1 what looks like
> a deadlock around the {{StreamSession}} monitor lock when
> {{StreamSession#receive()}} waits via {{syncUninteruptibly()}} for a response
> to a control message.
> {noformat}
> "Messaging-EventLoop-3-10" #320 daemon prio=5 os_prio=0 cpu=57979617.98ms
> elapsed=5587916.03s tid=0x7f056e88ae00 nid=0x80ec waiting for monitor
> entry [0x7f056d277000]
>java.lang.Thread.State: BLOCKED (on object monitor)
> at
> org.apache.cassandra.streaming.StreamSession.closeSession(StreamSession.java:524)
> - waiting to lock <0x0006816fae70> (a
> org.apache.cassandra.streaming.StreamSession)
> at
> org.apache.cassandra.streaming.StreamSession.onError(StreamSession.java:690)
> at
> org.apache.cassandra.streaming.async.StreamingMultiplexedChannel.onMessageComplete(StreamingMultiplexedChannel.java:264)
> at
> org.apache.cassandra.streaming.async.StreamingMultiplexedChannel.lambda$sendMessage$1(StreamingMultiplexedChannel.java:233)
> at
> org.apache.cassandra.streaming.async.StreamingMultiplexedChannel$$Lambda$2029/0x0008007a0c40.operationComplete(Unknown
> Source)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.notifyListener(ListenerList.java:134)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.notifyListener(ListenerList.java:148)
> at
> org.apache.cassandra.utils.concurrent.ListenerList$GenericFutureListenerList.notifySelf(ListenerList.java:190)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.lambda$notifyExclusive$0(ListenerList.java:124)
> at
> org.apache.cassandra.utils.concurrent.ListenerList$$Lambda$950/0x000800666040.accept(Unknown
> Source)
> at
> org.apache.cassandra.utils.concurrent.IntrusiveStack.forEach(IntrusiveStack.java:195)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.notifyExclusive(ListenerList.java:124)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.notify(ListenerList.java:96)
> at
> org.apache.cassandra.utils.concurrent.AsyncFuture.trySet(AsyncFuture.java:104)
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.tryFailure(AbstractFuture.java:148)
> at
> org.apache.cassandra.utils.concurrent.AsyncPromise.tryFailure(AsyncPromise.java:139)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.safeSetFailure(AbstractChannel.java:1009)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.write(AbstractChannel.java:870)
> at
> io.netty.channel.DefaultChannelPipeline$HeadContext.write(DefaultChannelPipeline.java:1367)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeWrite0(AbstractChannelHandlerContext.java:717)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeWriteAndFlush(AbstractChannelHandlerContext.java:764)
> at
> io.netty.channel.AbstractChannelHandlerContext$WriteTask.run(AbstractChannelHandlerContext.java:1071)
> at
> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
> at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
> at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(java.base@11.0.16/Thread.java:829)
> {noformat}
> It seems that while {{receive()} is holding the monitor lock on
> {{StreamSession}}, the callback that executes on a different thread for the
> control message it sends carries an error. This error, when handled in
> {{onError()}}, then calls {{closeSession()}}, which tries to acquire the
> monitor lock already held in {{receive()}}.
> {noformat}
>
[jira] [Assigned] (CASSANDRA-18598) Use trie for literal index building
[ https://issues.apache.org/jira/browse/CASSANDRA-18598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Rackliffe reassigned CASSANDRA-18598: --- Assignee: Atri Sharma > Use trie for literal index building > --- > > Key: CASSANDRA-18598 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18598 > Project: Cassandra > Issue Type: Improvement >Reporter: Mike Adamson >Assignee: Atri Sharma >Priority: Normal > > The BlockBalancedTreeRamBuffer for numerics indexes uses a trie for building > indexes in memory before flushing to disk. The RAMStringIndexer for literal > indexes does not do this. It uses lucene classes to build the in memory index > before flushing. > We should combine both of the in-memory index builders and have them both use > the trie. -- 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-18590) Introduce IndexTermType to replace TypeUtils in SAI
[
https://issues.apache.org/jira/browse/CASSANDRA-18590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe reassigned CASSANDRA-18590:
---
Assignee: Atri Sharma
> Introduce IndexTermType to replace TypeUtils in SAI
> ---
>
> Key: CASSANDRA-18590
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18590
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/SAI
>Reporter: Mike Adamson
>Assignee: Atri Sharma
>Priority: Normal
>
> From a review comment by [~adelapena] on the
> [CASSANDRA-18067|https://issues.apache.org/jira/browse/CASSANDRA-18067] PR
> {quote}Not directly related to this ticket, but it seems to me that the
> methods on TypeUtil do a lot of repeated work in the hot path just to
> determine the data type of the caller. These operations include finding the
> base type of reversed multiple times, multiple instanceof calls, etc. All
> these operations on each index are called with the same
> IndexContext#getValidator argument, needlessly repeating work for every
> column value.
> I understand that most of the methods on TypeUtil are things that would
> normally be part of AbstractType, so each particular data type can provide
> its own implementation. But we don't want to couple the generic data types
> with SAI, so we have this class instead.
> I think that we could add a kind of TermType class decorating AbstractType,
> and subclass it for every data type that gets special treatment (LONG,
> VARINT, DECIMAL and INET). Then, IndexContext would hold the adequate
> instance of TermType. This instance would be able to provide the same
> operations as the current TypeUtil, but without the type checks.{quote}
--
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-17534) CQLSH help topic links are broken between textile and online files
[
https://issues.apache.org/jira/browse/CASSANDRA-17534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-17534:
--
Fix Version/s: 3.0.30
3.11.16
4.0.12
4.1.4
5.0
(was: 3.0.x)
(was: 3.11.x)
(was: 5.x)
(was: 4.0.x)
(was: 4.1.x)
(was: 5.1.x)
Since Version: NA
Source Control Link:
https://github.com/apache/cassandra/commit/28c04fbdde56c4a4e20aadd38952b5148467e443
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> CQLSH help topic links are broken between textile and online files
> --
>
> Key: CASSANDRA-17534
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17534
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Brad Schoening
>Assignee: Vineet Gali
>Priority: Normal
> Fix For: 3.0.30, 3.11.16, 4.0.12, 4.1.4, 5.0
>
>
> CQLSH help topics opens a generic CQL page, not the specific topic. This
> happens when docs are not installed locally, and it tries to open the online
> version.
> The file cqlsh.py has:
> {{ # default location of local CQL.html}}
> {{ if os.path.exists(CASSANDRA_PATH + '/doc/cql3/CQL.html'):}}
> {{ }}
> {{ else:}}
> {{ # fallback to online version}}
> {{ CASSANDRA_CQL_HTML = CASSANDRA_CQL_HTML_FALLBACK}}
> For example,
> {{cqlsh> help truncate;}}
> opens the page:
> [https://cassandra.apache.org/doc/latest/cassandra/cql/index.html#truncateStmt]
> but there is no information about 'truncate' on that page and the anchor
> #truncateStmt doesn't exist.
> the correct page anchor is:
> [https://cassandra.apache.org/doc/latest/cassandra/cql/ddl.html#truncate-statement]
> The local file anchors appear they may be incorrect as well:
> [https://github.com/apache/cassandra/blob/trunk/doc/cql3/CQL.textile#truncate]
> To reproduce this, 'pip install cqlsh' on a machine without a Cassandra
> package install.
--
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.0 updated (7ec9b7cf4f -> 1e6df948a7)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 7ec9b7cf4f Merge branch 'cassandra-3.11' into cassandra-4.0 add 28c04fbdde Fix CQLSH online help topic link add 7f92f1bc22 Merge branch 'cassandra-3.0' into cassandra-3.11 add 1e6df948a7 Merge branch 'cassandra-3.11' into cassandra-4.0 No new revisions were added by this update. Summary of changes: CHANGES.txt | 1 + bin/cqlsh.py | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-3.11 updated (60d04d6713 -> 7f92f1bc22)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch cassandra-3.11 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 60d04d6713 Merge branch 'cassandra-3.0' into cassandra-3.11 add 28c04fbdde Fix CQLSH online help topic link add 7f92f1bc22 Merge branch 'cassandra-3.0' into cassandra-3.11 No new revisions were added by this update. Summary of changes: CHANGES.txt | 1 + bin/cqlsh.py | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) - 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 (d850cd7372 -> 8549f232b5)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git from d850cd7372 Merge branch 'cassandra-4.0' into cassandra-4.1 add 28c04fbdde Fix CQLSH online help topic link add 7f92f1bc22 Merge branch 'cassandra-3.0' into cassandra-3.11 add 1e6df948a7 Merge branch 'cassandra-3.11' into cassandra-4.0 add 8549f232b5 Merge branch 'cassandra-4.0' into cassandra-4.1 No new revisions were added by this update. Summary of changes: CHANGES.txt | 1 + bin/cqlsh.py | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-3.0 updated (5c4dd3b993 -> 28c04fbdde)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch cassandra-3.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 5c4dd3b993 Remove unused suppressions add 28c04fbdde Fix CQLSH online help topic link No new revisions were added by this update. Summary of changes: CHANGES.txt | 1 + bin/cqlsh.py | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) - 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. smiklosovic pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit ab40d85cd15cb6d539f5fe1e7e042c685e249af7 Merge: 5a9b79bb83 ada67cb2a4 Author: Stefan Miklosovic AuthorDate: Tue Aug 8 18:07:00 2023 +0200 Merge branch 'cassandra-5.0' into trunk CHANGES.txt | 1 + pylib/cqlshlib/cqlshmain.py | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --cc pylib/cqlshlib/cqlshmain.py index 7f15b13bb1,de00c1c7dd..df59c4717f --- a/pylib/cqlshlib/cqlshmain.py +++ b/pylib/cqlshlib/cqlshmain.py @@@ -,9 -2217,14 +,9 @@@ def setup_cqlruleset(cqlmodule) cqlruleset.commands_end_with_newline.update(cqlshhandling.my_commands_ending_with_newline) -def setup_cqldocs(cqlmodule): -global cqldocs -cqldocs = cqlmodule.cqldocs - - def setup_docspath(path): global CASSANDRA_CQL_HTML - CASSANDRA_CQL_HTML_FALLBACK = 'https://cassandra.apache.org/doc/latest/cql/index.html' + CASSANDRA_CQL_HTML_FALLBACK = 'https://cassandra.apache.org/doc/latest/cassandra/cql/cql_singlefile.html' # # default location of local CQL.html if os.path.exists(path + '/doc/cql3/CQL.html'): - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (5a9b79bb83 -> ab40d85cd1)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from 5a9b79bb83 Merge branch 'cassandra-5.0' into trunk add 28c04fbdde Fix CQLSH online help topic link add 7f92f1bc22 Merge branch 'cassandra-3.0' into cassandra-3.11 add 1e6df948a7 Merge branch 'cassandra-3.11' into cassandra-4.0 add 8549f232b5 Merge branch 'cassandra-4.0' into cassandra-4.1 add ada67cb2a4 Merge branch 'cassandra-4.1' into cassandra-5.0 new ab40d85cd1 Merge branch 'cassandra-5.0' into trunk 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: CHANGES.txt | 1 + pylib/cqlshlib/cqlshmain.py | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) - 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 (3dd2665f12 -> ada67cb2a4)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch cassandra-5.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 3dd2665f12 Merge branch 'cassandra-4.1' into cassandra-5.0 add 28c04fbdde Fix CQLSH online help topic link add 7f92f1bc22 Merge branch 'cassandra-3.0' into cassandra-3.11 add 1e6df948a7 Merge branch 'cassandra-3.11' into cassandra-4.0 add 8549f232b5 Merge branch 'cassandra-4.0' into cassandra-4.1 add ada67cb2a4 Merge branch 'cassandra-4.1' into cassandra-5.0 No new revisions were added by this update. Summary of changes: CHANGES.txt | 1 + pylib/cqlshlib/cqlshmain.py | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18734) SAI result retriever is filtering too many rows
[ https://issues.apache.org/jira/browse/CASSANDRA-18734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Rackliffe updated CASSANDRA-18734: Reviewers: Caleb Rackliffe > SAI result retriever is filtering too many rows > --- > > Key: CASSANDRA-18734 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18734 > Project: Cassandra > Issue Type: Bug > Components: Feature/SAI >Reporter: Mike Adamson >Assignee: Mike Adamson >Priority: Normal > Attachments: image-2023-08-08-13-48-19-701.png, > image-2023-08-08-13-49-19-576.png > > > Performance tests on SAI have shown that the number of rows being filtered > for wide row partitions is more than expected. For a 10k row/partition test - > limit 10, the following has been observed. > !image-2023-08-08-13-49-19-576.png|width=952,height=368! > This is not the expected outcome of row-awareness and needs investigating. > The number of rows read should, roughly, match the number of partitions read. > -- 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-18733) Waiting indefinitely on ReceivedMessage response in StreamSession#receive() can cause deadlock
[
https://issues.apache.org/jira/browse/CASSANDRA-18733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-18733:
Reviewers: Caleb Rackliffe
> Waiting indefinitely on ReceivedMessage response in StreamSession#receive()
> can cause deadlock
> --
>
> Key: CASSANDRA-18733
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18733
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair, Consistency/Streaming
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 4.1.x, 5.0, 5.x
>
>
> I've observed in a recent stack trace from a node running 4.1 what looks like
> a deadlock around the {{StreamSession}} monitor lock when
> {{StreamSession#receive()}} waits via {{syncUninteruptibly()}} for a response
> to a control message.
> {noformat}
> "Messaging-EventLoop-3-10" #320 daemon prio=5 os_prio=0 cpu=57979617.98ms
> elapsed=5587916.03s tid=0x7f056e88ae00 nid=0x80ec waiting for monitor
> entry [0x7f056d277000]
>java.lang.Thread.State: BLOCKED (on object monitor)
> at
> org.apache.cassandra.streaming.StreamSession.closeSession(StreamSession.java:524)
> - waiting to lock <0x0006816fae70> (a
> org.apache.cassandra.streaming.StreamSession)
> at
> org.apache.cassandra.streaming.StreamSession.onError(StreamSession.java:690)
> at
> org.apache.cassandra.streaming.async.StreamingMultiplexedChannel.onMessageComplete(StreamingMultiplexedChannel.java:264)
> at
> org.apache.cassandra.streaming.async.StreamingMultiplexedChannel.lambda$sendMessage$1(StreamingMultiplexedChannel.java:233)
> at
> org.apache.cassandra.streaming.async.StreamingMultiplexedChannel$$Lambda$2029/0x0008007a0c40.operationComplete(Unknown
> Source)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.notifyListener(ListenerList.java:134)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.notifyListener(ListenerList.java:148)
> at
> org.apache.cassandra.utils.concurrent.ListenerList$GenericFutureListenerList.notifySelf(ListenerList.java:190)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.lambda$notifyExclusive$0(ListenerList.java:124)
> at
> org.apache.cassandra.utils.concurrent.ListenerList$$Lambda$950/0x000800666040.accept(Unknown
> Source)
> at
> org.apache.cassandra.utils.concurrent.IntrusiveStack.forEach(IntrusiveStack.java:195)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.notifyExclusive(ListenerList.java:124)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.notify(ListenerList.java:96)
> at
> org.apache.cassandra.utils.concurrent.AsyncFuture.trySet(AsyncFuture.java:104)
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.tryFailure(AbstractFuture.java:148)
> at
> org.apache.cassandra.utils.concurrent.AsyncPromise.tryFailure(AsyncPromise.java:139)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.safeSetFailure(AbstractChannel.java:1009)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.write(AbstractChannel.java:870)
> at
> io.netty.channel.DefaultChannelPipeline$HeadContext.write(DefaultChannelPipeline.java:1367)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeWrite0(AbstractChannelHandlerContext.java:717)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeWriteAndFlush(AbstractChannelHandlerContext.java:764)
> at
> io.netty.channel.AbstractChannelHandlerContext$WriteTask.run(AbstractChannelHandlerContext.java:1071)
> at
> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
> at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
> at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(java.base@11.0.16/Thread.java:829)
> {noformat}
> It seems that while {{receive()} is holding the monitor lock on
> {{StreamSession}}, the callback that executes on a different thread for the
> control message it sends carries an error. This error, when handled in
> {{onError()}}, then calls {{closeSession()}}, which tries to acquire the
> monitor lock already held in {{receive()}}.
> {noformat}
> "Stream-Deserializer-/100.70.229.6:7000-de724029"
[jira] [Commented] (CASSANDRA-18455) Fix test_putget – dtest.putget_test.TestPutGet
[
https://issues.apache.org/jira/browse/CASSANDRA-18455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752116#comment-17752116
]
Brandon Williams commented on CASSANDRA-18455:
--
I'm not sure what else there is to do here since we already wait for agreement
in both create_ks and create_cf, though I guess this is interesting since
apparently the agreement was a lie. I'll note that this test [shouldn't be
running|https://github.com/apache/cassandra-dtest/blob/trunk/putget_test.py#L21]
though.
> Fix test_putget – dtest.putget_test.TestPutGet
> --
>
> Key: CASSANDRA-18455
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18455
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.x
>
>
> Seen on current trunk, here:
> [https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/2416/tests]
> {code:java}
> Error failed on teardown with "Unexpected error found in node logs (see
> stdout for full details). Errors: [[node3] 'ERROR [PendingRangeCalculator:1]
> 2023-04-08 00:54:06,468 JVMStabilityInspector.java:68 - Exception in thread
> Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
> Unknown keyspace system_traces\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:325)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:163)\n\tat
> org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
>
> org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:163)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:152)\n\tat
> org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
>
> org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce.run(SingleThreadExecutorPlus.java:60)\n\tat
>
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)\n\tat
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)\n\tat
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.lang.Thread.run(Thread.java:750)']" Stacktrace Unexpected error found
> in node logs (see stdout for full details). Errors: [[node3] 'ERROR
> [PendingRangeCalculator:1] 2023-04-08 00:54:06,468
> JVMStabilityInspector.java:68 - Exception in thread
> Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
> Unknown keyspace system_traces\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:325)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:163)\n\tat
> org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
>
> org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:163)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:152)\n\tat
> org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
>
> org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce.run(SingleThreadExecutorPlus.java:60)\n\tat
>
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)\n\tat
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)\n\tat
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.lang.Thread.run(Thread.java:750)']{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18705) Create release branch cassandra-5.0
[
https://issues.apache.org/jira/browse/CASSANDRA-18705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752115#comment-17752115
]
Michael Semb Wever commented on CASSANDRA-18705:
cassandra-dtest patch:
https://github.com/apache/cassandra-dtest/compare/trunk...thelastpickle:cassandra-dtest:mck/18705
> Create release branch cassandra-5.0
> ---
>
> Key: CASSANDRA-18705
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18705
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 5.x
>
>
> Figure out what needs to be done beyond the following…
> 1. Create release branch
> {code}
> git switch -c cassandra-5.0 trunk
> git push --set-upstream origin cassandra-5.0
> {code}
> 2. Bump trunk's version
> {code}
> git switch trunk
> # increment version to 5.1
> edit build.xml debian/changelog CHANGES.txt NEWS.txt
> {code}
> 2a. Update jvm-dtest supported upgrade paths, and dtest jar generation (both
> circleci and in-tree scripts)
> -
> https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
>
> -
> https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
> - https://github.com/apache/cassandra/blob/trunk/.build/run-tests.sh#L85
> 3. Add `5.0-alpha`, `5.0-alpha1`, `5.0-beta`, `5.0-rc`, `5.0.x` and `5.1.x`
> to jira versions
> (no existing tickets will be changed - assignees need to change appropriate
> bugs from 5.x to what is appropriate…)
> 4. Update docker images to include cassandra-5.0
> (Docker images also need to be deployed)
> 5. Add pipeline to ci-cassandra
> https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
> 6. Add dtest version and upgrade paths
> -
> https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
> -
> https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
> 7. Update how_to_commit documentation
> https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc
> 8. Update website CI to trigger off cassandra-5.0 builds
> -
> https://github.com/apache/cassandra-builds/commit/1fc9b5ee71dc37e1145f276ead5c680c6b3fe3db
--
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-18529) Remove legacy command line options from cassandra-stress
[ https://issues.apache.org/jira/browse/CASSANDRA-18529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752110#comment-17752110 ] Brandon Williams commented on CASSANDRA-18529: -- Sure. ||Branch||CI|| |[trunk|https://github.com/driftx/cassandra/tree/CASSANDRA-18529-trunk]|[j11|https://app.circleci.com/pipelines/github/driftx/cassandra/1173/workflows/bd1d2237-aadf-491f-9671-e361cb78e269], [j17|https://app.circleci.com/pipelines/github/driftx/cassandra/1173/workflows/9a065b50-a77f-49c0-9cd4-f9ab66144b34]| > Remove legacy command line options from cassandra-stress > > > Key: CASSANDRA-18529 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18529 > Project: Cassandra > Issue Type: Improvement > Components: Tool/stress >Reporter: Brad Schoening >Assignee: Timothy Tu >Priority: Low > Fix For: 5.x > > Attachments: signature.asc, signature.asc > > > The cassandra-stress *mode* option allows specifying options for native > protocol and cql3, but these don't seem useful as there would seem to be no > other valid options now that cql3 is the standard and thrift no longer > supported. > -mode native cql3 user=cassandra password=xx > can be simplified to: > -mode user=cassandra password=xx > Also, the readme.txt in tools/stress states "cassandra-stress supports > benchmarking any Cassandra cluster of version 2.0+" but maybe should be > updated to a supported Cassandra version, i.e., 3.11.x. -- 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-18529) Remove legacy command line options from cassandra-stress
[ https://issues.apache.org/jira/browse/CASSANDRA-18529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752106#comment-17752106 ] Timothy Tu commented on CASSANDRA-18529: [~smiklosovic] I added the compatibility. [~brandon.williams] can we run the Cl again? > Remove legacy command line options from cassandra-stress > > > Key: CASSANDRA-18529 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18529 > Project: Cassandra > Issue Type: Improvement > Components: Tool/stress >Reporter: Brad Schoening >Assignee: Timothy Tu >Priority: Low > Fix For: 5.x > > Attachments: signature.asc, signature.asc > > > The cassandra-stress *mode* option allows specifying options for native > protocol and cql3, but these don't seem useful as there would seem to be no > other valid options now that cql3 is the standard and thrift no longer > supported. > -mode native cql3 user=cassandra password=xx > can be simplified to: > -mode user=cassandra password=xx > Also, the readme.txt in tools/stress states "cassandra-stress supports > benchmarking any Cassandra cluster of version 2.0+" but maybe should be > updated to a supported Cassandra version, i.e., 3.11.x. -- 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-18724) Investigate unmatched suppressions
[
https://issues.apache.org/jira/browse/CASSANDRA-18724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18724:
-
Fix Version/s: 3.0.30
3.11.16
4.0.12
4.1.4
5.0
(was: 3.0.x)
(was: 3.11.x)
(was: 5.x)
(was: 4.0.x)
(was: 4.1.x)
Since Version: NA
Source Control Link:
https://github.com/apache/cassandra/commit/5c4dd3b99393c63c1e0c5a672f0af28361541a7a
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed, thanks!
> Investigate unmatched suppressions
> --
>
> Key: CASSANDRA-18724
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18724
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 3.0.30, 3.11.16, 4.0.12, 4.1.4, 5.0
>
>
> Since we upgraded OWASP, it now reports unmatched suppressions ("Suppression
> Rule had zero matches") we should investigate and possibly remove.
--
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] 01/01: Merge branch 'cassandra-3.0' into cassandra-3.11
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-3.11 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 60d04d6713c9bc604d4528bf4df9cce7cd84c67a Merge: bee215cce6 5c4dd3b993 Author: Brandon Williams AuthorDate: Tue Aug 8 10:03:31 2023 -0500 Merge branch 'cassandra-3.0' into cassandra-3.11 .build/dependency-check-suppressions.xml | 43 CHANGES.txt | 1 + 2 files changed, 1 insertion(+), 43 deletions(-) diff --cc .build/dependency-check-suppressions.xml index 58b38b7e62,d0a81458db..47d37c53db --- a/.build/dependency-check-suppressions.xml +++ b/.build/dependency-check-suppressions.xml @@@ -126,20 -88,22 +89,14 @@@ CVE-2019-0205 - - + -^pkg:maven/org\.codehaus\.jackson/jackson\-mapper\-asl@.*$ -CVE-2017-7525 -CVE-2017-15095 -CVE-2017-17485 -CVE-2018-5968 -CVE-2018-14718 -CVE-2018-1000873 -CVE-2018-7489 -CVE-2019-10172 -CVE-2019-14540 -CVE-2019-14893 -CVE-2019-16335 -CVE-2019-17267 +^pkg:maven/com\.fasterxml\.jackson\.core/jackson\-databind@.*$ +CVE-2022-42003 +CVE-2022-42004 +CVE-2023-35116 + CVE-2022-42003 + CVE-2022-42004 - - - ^pkg:maven/com\.fasterxml\.jackson\.core/jackson\-core@.*$ - CVE-2022-45688 - - diff --cc CHANGES.txt index 86f4b5c758,697262750a..8ca47eb52d --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,13 -1,5 +1,14 @@@ -3.0.30 +3.11.16 + * Moved jflex from runtime to build dependencies (CASSANDRA-18664) + * Fix CAST function for float to decimal (CASSANDRA-18647) + * Suppress CVE-2022-45688 (CASSANDRA-18643) + * Remove unrepaired SSTables from garbage collection when only_purge_repaired_tombstones is true (CASSANDRA-14204) + * Wait for live endpoints in gossip waiting to settle (CASSANDRA-18543) + * Fix error message handling when trying to use CLUSTERING ORDER with non-clustering column (CASSANDRA-17818 + * Add keyspace and table name to exception message during ColumnSubselection deserialization (CASSANDRA-18346) + * Remove unnecessary String.format invocation in QueryProcessor when getting a prepared statement from cache (CASSANDRA-17202) +Merged from 3.0: + * Remove unused suppressions (CASSANDRA-18724) * Upgrade OWASP to 8.3.1 (CASSANDRA-18650) * Suppress CVE-2023-34462 (CASSANDRA-18649) * Add support for AWS Ec2 IMDSv2 (CASSANDRA-16555) - 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. brandonwilliams pushed a commit to branch cassandra-5.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 3dd2665f12a81f55f82eddb5f054b39ca94140c9 Merge: 53d1644ff4 d850cd7372 Author: Brandon Williams AuthorDate: Tue Aug 8 10:28:16 2023 -0500 Merge branch 'cassandra-4.1' into cassandra-5.0 .build/dependency-check-suppressions.xml | 52 CHANGES.txt | 3 ++ 2 files changed, 3 insertions(+), 52 deletions(-) diff --cc .build/dependency-check-suppressions.xml index d7a66cb3bf,b7ebb45e57..6c2e52c3ca --- a/.build/dependency-check-suppressions.xml +++ b/.build/dependency-check-suppressions.xml @@@ -44,42 -35,26 +35,6 @@@ CVE-2021-4235 CVE-2017-18640 - - - ^pkg:maven/net\.openhft/chronicle\-wire@.*$ - cpe:/a:wire:wire - - - - ^pkg:maven/org\.apache\.commons.*$ - CVE-2021-37533 - - - ^pkg:maven/commons-io/.*$ - CVE-2021-37533 - - - ^pkg:maven/commons-cli/.*$ - CVE-2021-37533 - -- - ^pkg:maven/commons-codec/.*$ - CVE-2021-37533 - -^pkg:maven/com\.google\.guava/guava@.*$ -CVE-2020-8908 -CVE-2023-2976 -- -- -- --^pkg:maven/io\.netty/netty\-all@.*$ --CVE-2021-21290 --CVE-2021-21295 --CVE-2021-21409 --CVE-2021-37136 --CVE-2021-37137 --CVE-2021-43797 --CVE-2022-24823 --CVE-2022-41881 --CVE-2022-41915 --CVE-2023-34462 -- ^pkg:maven/com\.fasterxml\.jackson\.core/jackson\-databind@.*$ @@@ -87,11 -62,5 +42,4 @@@ CVE-2022-42004 CVE-2023-35116 - - - - ^pkg:maven/com\.fasterxml\.jackson\.core/jackson\-core@.*$ - CVE-2022-45688 - -- diff --cc CHANGES.txt index 921ad41f4d,0f33ba0e2e..278b93387d --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,186 -1,5 +1,189 @@@ -4.1.4 +5.0 + * Upgraded Netty to 4.1.96, added BouncyCastle dependency (CASSANDRA-17992) + * Fix for (unsupported) big endian unaligned architecture, eg s390x (CASSANDRA-17723) + * CIDR filtering authorizer (CASSANDRA-18592) + * Remove 3.x from the versions checked for prepared statement behaviour (CASSANDRA-18695) + * Add vector similarity functions (CASSANDRA-18640) + * Lift MessagingService.minimum_version to 40 (CASSANDRA-18314) + * Introduce pluggable crypto providers and default to AmazonCorrettoCryptoProvider (CASSANDRA-18624) + * Improved DeletionTime serialization (CASSANDRA-18648) + * CEP-7: Storage Attached Indexes (CASSANDRA-16052) + * Add equals/hashCode override for ServerEncryptionOptions (CASSANDRA-18428) + * Upgrade ECJ to version 3.33.0 (CASSANDRA-18190) + * Fix ClassCastException from jdk GaloisCounterMode when using JDK17 provider (CASSANDRA-18180) + * Drop JDK8, add JDK17 (CASSANDRA-18255) + * Remove WaitingOnFreeMemtableSpace and DroppedMutations metrics (CASSANDRA-18298) + * Upgrade Jamm version to 0.4.0 (CASSANDRA-17884, CASSANDRA-16304, CASSANDRA-18329) + * Remove legacy 3.0/3.11 buffer pool metrics (CASSANDRA-18313) + * Add AzureSnitch (CASSANDRA-18646) + * Implementation of the Unified Compaction Strategy as described in CEP-26 (CASSANDRA-18397) + * Upgrade commons cli to 1.5.0 (CASSANDRA-18659) + * Disable the deprecated keyspace/table thresholds and convert them to guardrails (CASSANDRA-18617) + * Deprecate CloudstackSnitch and remove duplicate code in snitches (CASSANDRA-18438) + * Add support for vectors in UDFs (CASSANDRA-18613) + * Improve vector value validation errors (CASSANDRA-18652) + * Upgrade Guava to 32.0.1 (CASSANDRA-18645) + * Add duration and count of partition keys to sstablemetadata (CASSANDRA-18639) + * Remove deprecated compaction_tombstone_warning_threshold and compaction_large_partition_warning_threshold from yaml (CASSANDRA-18626) + * Enhance nodetool compactionstats with additional metrics (CASSANDRA-18305) + * Added support for type VECTOR (CASSANDRA-18504) + * Expose bootstrap and decommission state to nodetool info (CASSANDRA-18555) + * Fix SSTabledump errors when dumping data from index (CASSANDRA-17698) + * Avoid unnecessary deserialization of terminal arguments when executing CQL functions (CASSANDRA-18566) + * Remove dependency on pytz library for setting CQLSH timezones on Python version >= 3.9 (CASSANDRA-17433) + * Extend maximum expiration date (CASSANDRA-14227) + * Add guardrail for partition tombstones and deprecate compaction_tombstone_warning_threshold (CASSANDRA-17194) + * Print header and statistics for cassandra-stress output with arbitrary frequency (CASSANDRA-12972) + * CEP-25: Trie-indexed SSTable format (CASSANDRA-18398) + * Make cassandra-stress able to read all credentials from a file (CASSANDRA-18544)
[cassandra] branch cassandra-3.11 updated (bee215cce6 -> 60d04d6713)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch cassandra-3.11 in repository https://gitbox.apache.org/repos/asf/cassandra.git from bee215cce6 Merge branch 'cassandra-3.0' into cassandra-3.11 new 5c4dd3b993 Remove unused suppressions new 60d04d6713 Merge branch 'cassandra-3.0' into cassandra-3.11 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: .build/dependency-check-suppressions.xml | 43 CHANGES.txt | 1 + 2 files changed, 1 insertion(+), 43 deletions(-) - 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 (b94436c783 -> d850cd7372)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git from b94436c783 update ConfigCompatibility test new 5c4dd3b993 Remove unused suppressions new 60d04d6713 Merge branch 'cassandra-3.0' into cassandra-3.11 new 7ec9b7cf4f Merge branch 'cassandra-3.11' into cassandra-4.0 new d850cd7372 Merge branch 'cassandra-4.0' into cassandra-4.1 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: .build/dependency-check-suppressions.xml | 37 CHANGES.txt | 1 + 2 files changed, 1 insertion(+), 37 deletions(-) - 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 (53d1644ff4 -> 3dd2665f12)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch cassandra-5.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 53d1644ff4 Upgraded to Netty 4.1.96 new 5c4dd3b993 Remove unused suppressions new 60d04d6713 Merge branch 'cassandra-3.0' into cassandra-3.11 new 7ec9b7cf4f Merge branch 'cassandra-3.11' into cassandra-4.0 new d850cd7372 Merge branch 'cassandra-4.0' into cassandra-4.1 new 3dd2665f12 Merge branch 'cassandra-4.1' into cassandra-5.0 The 5 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: .build/dependency-check-suppressions.xml | 52 CHANGES.txt | 3 ++ 2 files changed, 3 insertions(+), 52 deletions(-) - 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.0' into cassandra-4.1
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit d850cd7372c963bd7633b3ea900d1957aa320c7a Merge: b94436c783 7ec9b7cf4f Author: Brandon Williams AuthorDate: Tue Aug 8 10:11:26 2023 -0500 Merge branch 'cassandra-4.0' into cassandra-4.1 .build/dependency-check-suppressions.xml | 37 CHANGES.txt | 1 + 2 files changed, 1 insertion(+), 37 deletions(-) diff --cc CHANGES.txt index 6bb86a057a,62b70b072f..0f33ba0e2e --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -5,12 -3,12 +5,13 @@@ Merged from 4.0 * Fix BulkLoader ignoring cipher suites options (CASSANDRA-18582) * Migrate Python optparse to argparse (CASSANDRA-17914) Merged from 3.11: - * Moved jflex from runtime to build dependencies (CASSANDRA-18664) Merged from 3.0: + * Remove unused suppressions (CASSANDRA-18724) -4.0.11 +4.1.3 + * Add a virtual table that exposes currently running queries (CASSANDRA-15241) +Merged from 4.0: * Revert CASSANDRA-16718 (CASSANDRA-18560) * Upgrade snappy to 1.1.10.1 (CASSANDRA-18608) * Fix assertion error when describing mv as table (CASSANDRA-18596) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (d24baecac9 -> 5a9b79bb83)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from d24baecac9 Simplify pylib/cqlshlib/helptopics.py using associative array new 5c4dd3b993 Remove unused suppressions new 60d04d6713 Merge branch 'cassandra-3.0' into cassandra-3.11 new 7ec9b7cf4f Merge branch 'cassandra-3.11' into cassandra-4.0 new d850cd7372 Merge branch 'cassandra-4.0' into cassandra-4.1 new 3dd2665f12 Merge branch 'cassandra-4.1' into cassandra-5.0 new 5a9b79bb83 Merge branch 'cassandra-5.0' into trunk The 6 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: .build/dependency-check-suppressions.xml | 52 CHANGES.txt | 3 ++ 2 files changed, 3 insertions(+), 52 deletions(-) - 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. brandonwilliams pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 5a9b79bb83f8fd102a148e8bf5632acb6eb8ae4e Merge: d24baecac9 3dd2665f12 Author: Brandon Williams AuthorDate: Tue Aug 8 10:29:38 2023 -0500 Merge branch 'cassandra-5.0' into trunk .build/dependency-check-suppressions.xml | 52 CHANGES.txt | 3 ++ 2 files changed, 3 insertions(+), 52 deletions(-) - 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-3.11' into cassandra-4.0
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 7ec9b7cf4f9827d3feaa15b62932cbfa0480b938 Merge: 8b331ddb4d 60d04d6713 Author: Brandon Williams AuthorDate: Tue Aug 8 10:07:00 2023 -0500 Merge branch 'cassandra-3.11' into cassandra-4.0 .build/dependency-check-suppressions.xml | 37 CHANGES.txt | 1 + 2 files changed, 1 insertion(+), 37 deletions(-) diff --cc .build/dependency-check-suppressions.xml index ae7ff368a7,47d37c53db..b7ebb45e57 --- a/.build/dependency-check-suppressions.xml +++ b/.build/dependency-check-suppressions.xml @@@ -20,19 -20,18 +20,10 @@@ https://jeremylong.github.io/DependencyCheck/general/suppression.html --> https://jeremylong.github.io/DependencyCheck/dependency-suppression.1.3.xsd;> - - - ^pkg:maven/com\.datastax\.cassandra/cassandra\-driver\-core@.*$ - CVE-2018-8016 - CVE-2019-2684 - CVE-2020-13946 - CVE-2020-17516 - CVE-2021-44521 - - -^pkg:maven/org\.xerial\.snappy/snappy\-java@.*$ -CVE-2023-34453 -CVE-2023-34454 -CVE-2023-34455 - - - + ^pkg:maven/org\.yaml/snakeyaml@.*$ CVE-2023-2251 -CVE-2017-18640 CVE-2022-25857 CVE-2022-38749 CVE-2022-38750 @@@ -44,37 -43,14 +35,15 @@@ CVE-2021-4235 CVE-2017-18640 - - - ^pkg:maven/net\.openhft/chronicle\-wire@.*$ - cpe:/a:wire:wire - - - + + +^pkg:maven/com\.google\.guava/guava@.*$ +CVE-2020-8908 +CVE-2023-2976 + - - - ^pkg:maven/org\.apache\.commons.*$ - CVE-2021-37533 - - - ^pkg:maven/commons-io/.*$ - CVE-2021-37533 - - - ^pkg:maven/commons-cli/.*$ - CVE-2021-37533 - - - ^pkg:maven/commons-codec/.*$ - CVE-2021-37533 - + ^pkg:maven/io\.netty/netty\-all@.*$ -CVE-2019-16869 -CVE-2019-20444 -CVE-2019-20445 -CVE-2020-7238 CVE-2021-21290 CVE-2021-21295 CVE-2021-21409 @@@ -92,12 -95,8 +61,6 @@@ CVE-2022-42003 CVE-2022-42004 CVE-2023-35116 - CVE-2022-42003 - CVE-2022-42004 - - - ^pkg:maven/com\.fasterxml\.jackson\.core/jackson\-core@.*$ - CVE-2022-45688 - - diff --cc CHANGES.txt index a45b6dce5d,8ca47eb52d..62b70b072f --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,20 -1,5 +1,21 @@@ -3.11.16 +4.0.12 + * Fix NTS log message when an unrecognized strategy option is passed (CASSANDRA-18679) + * Fix BulkLoader ignoring cipher suites options (CASSANDRA-18582) + * Migrate Python optparse to argparse (CASSANDRA-17914) +Merged from 3.11: * Moved jflex from runtime to build dependencies (CASSANDRA-18664) +Merged from 3.0: ++ * Remove unused suppressions (CASSANDRA-18724) + + +4.0.11 + * Revert CASSANDRA-16718 (CASSANDRA-18560) + * Upgrade snappy to 1.1.10.1 (CASSANDRA-18608) + * Fix assertion error when describing mv as table (CASSANDRA-18596) + * Track the amount of read data per row (CASSANDRA-18513) + * Fix Down nodes counter in nodetool describecluster (CASSANDRA-18512) + * Remove unnecessary shuffling of GossipDigests in Gossiper#makeRandomGossipDigest (CASSANDRA-18546) +Merged from 3.11: * Fix CAST function for float to decimal (CASSANDRA-18647) * Suppress CVE-2022-45688 (CASSANDRA-18643) * Remove unrepaired SSTables from garbage collection when only_purge_repaired_tombstones is true (CASSANDRA-14204) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-3.0 updated: Remove unused suppressions
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-3.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/cassandra-3.0 by this push: new 5c4dd3b993 Remove unused suppressions 5c4dd3b993 is described below commit 5c4dd3b99393c63c1e0c5a672f0af28361541a7a Author: Brandon Williams AuthorDate: Fri Aug 4 08:30:42 2023 -0500 Remove unused suppressions Patch by brandonwilliams; reviewed by adelapena and edimitrova for CASSANDRA-18724 --- .build/dependency-check-suppressions.xml | 44 CHANGES.txt | 1 + 2 files changed, 1 insertion(+), 44 deletions(-) diff --git a/.build/dependency-check-suppressions.xml b/.build/dependency-check-suppressions.xml index dead8f6120..d0a81458db 100644 --- a/.build/dependency-check-suppressions.xml +++ b/.build/dependency-check-suppressions.xml @@ -62,25 +62,6 @@ CVE-2023-34462 - - -^pkg:maven/ch\.qos\.logback/logback\-core@.*$ -CVE-2017-5929 - - -^pkg:maven/ch\.qos\.logback/logback\-classic@.*$ -CVE-2017-5929 - - - - -^pkg:maven/com\.datastax\.cassandra/cassandra\-driver\-core@.*$ -CVE-2019-2684 -CVE-2020-13946 -CVE-2020-17516 -CVE-2021-44521 - - ^pkg:maven/com\.google\.guava/guava@.*$ @@ -89,24 +70,6 @@ CVE-2023-2976 - - -^pkg:maven/org\.apache\.commons.*$ -CVE-2021-37533 - - -^pkg:maven/commons-io/.*$ -CVE-2021-37533 - - -^pkg:maven/commons-cli/.*$ -CVE-2021-37533 - - -^pkg:maven/commons-codec/.*$ -CVE-2021-37533 - - ^pkg:maven/org\.apache\.thrift/libthrift@.*$ @@ -142,12 +105,5 @@ CVE-2019-16335 CVE-2019-17267 - - -^pkg:maven/com\.fasterxml\.jackson\.core/jackson\-databind@.*$ -CVE-2023-35116 - CVE-2022-42003 - CVE-2022-42004 - diff --git a/CHANGES.txt b/CHANGES.txt index fbe5e0751b..697262750a 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 3.0.30 + * Remove unused suppressions (CASSANDRA-18724) * Upgrade OWASP to 8.3.1 (CASSANDRA-18650) * Suppress CVE-2023-34462 (CASSANDRA-18649) * Add support for AWS Ec2 IMDSv2 (CASSANDRA-16555) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.0 updated (8b331ddb4d -> 7ec9b7cf4f)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 8b331ddb4d Fix NTS log message when an unrecognized strategy option is passed new 5c4dd3b993 Remove unused suppressions new 60d04d6713 Merge branch 'cassandra-3.0' into cassandra-3.11 new 7ec9b7cf4f Merge branch 'cassandra-3.11' into cassandra-4.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: .build/dependency-check-suppressions.xml | 37 CHANGES.txt | 1 + 2 files changed, 1 insertion(+), 37 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18724) Investigate unmatched suppressions
[
https://issues.apache.org/jira/browse/CASSANDRA-18724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752089#comment-17752089
]
Ekaterina Dimitrova commented on CASSANDRA-18724:
-
{quote}We are missing a patch for the newly created 5.0 branch, but I assume it
will be identical to {{{}trunk{}}}. +1.
{quote}
Good point, I missed we have a brand new cassandra–5.0 branch. There is a
single patch difference which I do not see how it can influence what we do here.
My +1 still stands, assuming we add also the 5.0 patch in the merge.
> Investigate unmatched suppressions
> --
>
> Key: CASSANDRA-18724
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18724
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
>
> Since we upgraded OWASP, it now reports unmatched suppressions ("Suppression
> Rule had zero matches") we should investigate and possibly remove.
--
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-18584) CEP-29: NOT operator
[ https://issues.apache.org/jira/browse/CASSANDRA-18584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Kolaczkowski updated CASSANDRA-18584: --- Test and Documentation Plan: Unit / intergration tests included Local performance tests (single node) + fallout testing (distributed) Status: Patch Available (was: In Progress) > CEP-29: NOT operator > > > Key: CASSANDRA-18584 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18584 > Project: Cassandra > Issue Type: New Feature > Components: CQL/Interpreter, CQL/Semantics, CQL/Syntax, Feature/SAI >Reporter: Piotr Kolaczkowski >Assignee: Piotr Kolaczkowski >Priority: Normal > > Implement new CQL operators: > - NOT CONTAINS, > - NOT CONTAINS KEY, > - NOT IN > - NOT LIKE > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-29%3A+CQL+NOT+operator -- 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-18723) bcprov-jdk15on-1.70.jar vulnerability: CVE-2023-33201
[
https://issues.apache.org/jira/browse/CASSANDRA-18723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752084#comment-17752084
]
Stefan Miklosovic commented on CASSANDRA-18723:
---
[~e.dimitrova] good eye!
Yes this is on the way ...
> bcprov-jdk15on-1.70.jar vulnerability: CVE-2023-33201
> -
>
> Key: CASSANDRA-18723
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18723
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 5.0
>
>
> https://nvd.nist.gov/vuln/detail/CVE-2023-33201
> {quote}
> Bouncy Castle For Java before 1.74 is affected by an LDAP injection
> vulnerability. The vulnerability only affects applications that use an LDAP
> CertStore from Bouncy Castle to validate X.509 certificates. During the
> certificate validation process, Bouncy Castle inserts the certificate's
> Subject Name into an LDAP search filter without any escaping, which leads to
> an LDAP injection vulnerability.
> {quote}
--
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-18584) CEP-29: NOT operator
[ https://issues.apache.org/jira/browse/CASSANDRA-18584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752083#comment-17752083 ] Piotr Kolaczkowski commented on CASSANDRA-18584: Because LIKE operator is habdled neither by ALLOW FILTERING nor SAI, we'd like to postpone NOT LIKE implementation until we have more complete LIKE implementation first. WDYT? > CEP-29: NOT operator > > > Key: CASSANDRA-18584 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18584 > Project: Cassandra > Issue Type: New Feature > Components: CQL/Interpreter, CQL/Semantics, CQL/Syntax, Feature/SAI >Reporter: Piotr Kolaczkowski >Assignee: Piotr Kolaczkowski >Priority: Normal > > Implement new CQL operators: > - NOT CONTAINS, > - NOT CONTAINS KEY, > - NOT IN > - NOT LIKE > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-29%3A+CQL+NOT+operator -- 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-18584) CEP-29: NOT operator
[
https://issues.apache.org/jira/browse/CASSANDRA-18584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17731631#comment-17731631
]
Piotr Kolaczkowski edited comment on CASSANDRA-18584 at 8/8/23 2:59 PM:
Implemented:
- NOT CONTANS, NOT CONTAINS KEY, NOT IN, non-equals != anywhere with ALLOW
FILTERING
- Fast NOT IN and non-equals on clustering columns (w/o ALLOW FILTERING)
- Ability to use equality with other slice operators (including NOT IN and !=).
- SAI acceleraton of NOT CONTAINS / NOT CONTAINS KEY and map entry inequality
- Unit tests for all above
All {{org.apache.cassandra.cql3.validation.operations}} tests pass
To do:
- -Index support-
- NOT LIKE
was (Author: pkolaczk):
Implemented:
- NOT CONTANS, NOT CONTAINS KEY, NOT IN, non-equals != anywhere with ALLOW
FILTERING
- Fast NOT IN and non-equals on clustering columns (w/o ALLOW FILTERING)
- Ability to use equality with other slice operators (including NOT IN and !=).
- Unit tests for all above
All {{org.apache.cassandra.cql3.validation.operations}} tests pass
To do:
- Index support
- NOT LIKE
> CEP-29: NOT operator
>
>
> Key: CASSANDRA-18584
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18584
> Project: Cassandra
> Issue Type: New Feature
> Components: CQL/Interpreter, CQL/Semantics, CQL/Syntax, Feature/SAI
>Reporter: Piotr Kolaczkowski
>Assignee: Piotr Kolaczkowski
>Priority: Normal
>
> Implement new CQL operators:
> - NOT CONTAINS,
> - NOT CONTAINS KEY,
> - NOT IN
> - NOT LIKE
> https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-29%3A+CQL+NOT+operator
--
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-18723) bcprov-jdk15on-1.70.jar vulnerability: CVE-2023-33201
[
https://issues.apache.org/jira/browse/CASSANDRA-18723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18723:
-
Status: Open (was: Patch Available)
> bcprov-jdk15on-1.70.jar vulnerability: CVE-2023-33201
> -
>
> Key: CASSANDRA-18723
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18723
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 5.x
>
>
> https://nvd.nist.gov/vuln/detail/CVE-2023-33201
> {quote}
> Bouncy Castle For Java before 1.74 is affected by an LDAP injection
> vulnerability. The vulnerability only affects applications that use an LDAP
> CertStore from Bouncy Castle to validate X.509 certificates. During the
> certificate validation process, Bouncy Castle inserts the certificate's
> Subject Name into an LDAP search filter without any escaping, which leads to
> an LDAP injection vulnerability.
> {quote}
--
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-18723) bcprov-jdk15on-1.70.jar vulnerability: CVE-2023-33201
[
https://issues.apache.org/jira/browse/CASSANDRA-18723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18723:
-
Fix Version/s: 5.0
(was: 5.x)
> bcprov-jdk15on-1.70.jar vulnerability: CVE-2023-33201
> -
>
> Key: CASSANDRA-18723
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18723
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 5.0
>
>
> https://nvd.nist.gov/vuln/detail/CVE-2023-33201
> {quote}
> Bouncy Castle For Java before 1.74 is affected by an LDAP injection
> vulnerability. The vulnerability only affects applications that use an LDAP
> CertStore from Bouncy Castle to validate X.509 certificates. During the
> certificate validation process, Bouncy Castle inserts the certificate's
> Subject Name into an LDAP search filter without any escaping, which leads to
> an LDAP injection vulnerability.
> {quote}
--
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-18723) bcprov-jdk15on-1.70.jar vulnerability: CVE-2023-33201
[
https://issues.apache.org/jira/browse/CASSANDRA-18723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18723:
-
Resolution: Fixed
Status: Resolved (was: Open)
Works for me.
> bcprov-jdk15on-1.70.jar vulnerability: CVE-2023-33201
> -
>
> Key: CASSANDRA-18723
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18723
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 5.x
>
>
> https://nvd.nist.gov/vuln/detail/CVE-2023-33201
> {quote}
> Bouncy Castle For Java before 1.74 is affected by an LDAP injection
> vulnerability. The vulnerability only affects applications that use an LDAP
> CertStore from Bouncy Castle to validate X.509 certificates. During the
> certificate validation process, Bouncy Castle inserts the certificate's
> Subject Name into an LDAP search filter without any escaping, which leads to
> an LDAP injection vulnerability.
> {quote}
--
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-18724) Investigate unmatched suppressions
[
https://issues.apache.org/jira/browse/CASSANDRA-18724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-18724:
--
Status: Ready to Commit (was: Review In Progress)
> Investigate unmatched suppressions
> --
>
> Key: CASSANDRA-18724
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18724
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
>
> Since we upgraded OWASP, it now reports unmatched suppressions ("Suppression
> Rule had zero matches") we should investigate and possibly remove.
--
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-18724) Investigate unmatched suppressions
[
https://issues.apache.org/jira/browse/CASSANDRA-18724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752080#comment-17752080
]
Andres de la Peña commented on CASSANDRA-18724:
---
I have tested the patches with {{ant dependency-check}} and seen how the
unmatched suppressions are gone. Only {{trunk}} fails due to CASSANDRA-18723,
which is not related to the unmatched suppressions.
We are missing a patch for the newly created 5.0 branch, but I assume it will
be identical to {{{}trunk{}}}. +1.
> Investigate unmatched suppressions
> --
>
> Key: CASSANDRA-18724
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18724
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
>
> Since we upgraded OWASP, it now reports unmatched suppressions ("Suppression
> Rule had zero matches") we should investigate and possibly remove.
--
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-18723) bcprov-jdk15on-1.70.jar vulnerability: CVE-2023-33201
[
https://issues.apache.org/jira/browse/CASSANDRA-18723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752079#comment-17752079
]
Ekaterina Dimitrova edited comment on CASSANDRA-18723 at 8/8/23 2:56 PM:
-
{quote}Can confirm OWASP passes with that patch.
{quote}
I am +1 to close the ticket in favor of CASSANDRA-18729 (assuming I did not see
anyone complaining during review about the pointed change, and it will be
committed soon)
was (Author: e.dimitrova):
{quote}Can confirm OWASP passes with that patch.
{quote}
I am +1 to close the ticket in favor of CASSANDRA-18729 (assuming I did not see
anyone complaining during review about the pointed change)
> bcprov-jdk15on-1.70.jar vulnerability: CVE-2023-33201
> -
>
> Key: CASSANDRA-18723
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18723
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 5.x
>
>
> https://nvd.nist.gov/vuln/detail/CVE-2023-33201
> {quote}
> Bouncy Castle For Java before 1.74 is affected by an LDAP injection
> vulnerability. The vulnerability only affects applications that use an LDAP
> CertStore from Bouncy Castle to validate X.509 certificates. During the
> certificate validation process, Bouncy Castle inserts the certificate's
> Subject Name into an LDAP search filter without any escaping, which leads to
> an LDAP injection vulnerability.
> {quote}
--
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-18723) bcprov-jdk15on-1.70.jar vulnerability: CVE-2023-33201
[
https://issues.apache.org/jira/browse/CASSANDRA-18723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752079#comment-17752079
]
Ekaterina Dimitrova commented on CASSANDRA-18723:
-
{quote}Can confirm OWASP passes with that patch.
{quote}
I am +1 to close the ticket in favor of CASSANDRA-18729 (assuming I did not see
anyone complaining during review about the pointed change)
> bcprov-jdk15on-1.70.jar vulnerability: CVE-2023-33201
> -
>
> Key: CASSANDRA-18723
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18723
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 5.x
>
>
> https://nvd.nist.gov/vuln/detail/CVE-2023-33201
> {quote}
> Bouncy Castle For Java before 1.74 is affected by an LDAP injection
> vulnerability. The vulnerability only affects applications that use an LDAP
> CertStore from Bouncy Castle to validate X.509 certificates. During the
> certificate validation process, Bouncy Castle inserts the certificate's
> Subject Name into an LDAP search filter without any escaping, which leads to
> an LDAP injection vulnerability.
> {quote}
--
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-18730) Add guardrail for vector dimensions
[ https://issues.apache.org/jira/browse/CASSANDRA-18730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18730: - Status: Ready to Commit (was: Review In Progress) > Add guardrail for vector dimensions > --- > > Key: CASSANDRA-18730 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18730 > Project: Cassandra > Issue Type: New Feature > Components: Feature/Vector Search >Reporter: Andres de la Peña >Assignee: Andres de la Peña >Priority: Normal > Fix For: 5.x > > Time Spent: 20m > Remaining Estimate: 0h > > Add a guardrail limiting the number of dimensions of vector columns. It would > be analogous to the current guardrails limiting the number of items per > collection and the number of fields per UDT. -- 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-18730) Add guardrail for vector dimensions
[ https://issues.apache.org/jira/browse/CASSANDRA-18730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752076#comment-17752076 ] Brandon Williams commented on CASSANDRA-18730: -- +1 > Add guardrail for vector dimensions > --- > > Key: CASSANDRA-18730 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18730 > Project: Cassandra > Issue Type: New Feature > Components: Feature/Vector Search >Reporter: Andres de la Peña >Assignee: Andres de la Peña >Priority: Normal > Fix For: 5.x > > Time Spent: 20m > Remaining Estimate: 0h > > Add a guardrail limiting the number of dimensions of vector columns. It would > be analogous to the current guardrails limiting the number of items per > collection and the number of fields per UDT. -- 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-18724) Investigate unmatched suppressions
[
https://issues.apache.org/jira/browse/CASSANDRA-18724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752074#comment-17752074
]
Brandon Williams commented on CASSANDRA-18724:
--
bq. So this is new for OWASP? To report suppressions that are not needed
anymore?
I believe so, I haven't seen it in previous versions.
> Investigate unmatched suppressions
> --
>
> Key: CASSANDRA-18724
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18724
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
>
> Since we upgraded OWASP, it now reports unmatched suppressions ("Suppression
> Rule had zero matches") we should investigate and possibly remove.
--
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-18724) Investigate unmatched suppressions
[
https://issues.apache.org/jira/browse/CASSANDRA-18724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-18724:
Reviewers: Andres de la Peña, Ekaterina Dimitrova, Ekaterina Dimitrova
(was: Andres de la Peña)
Andres de la Peña, Ekaterina Dimitrova, Ekaterina Dimitrova
(was: Andres de la Peña, Ekaterina Dimitrova)
Status: Review In Progress (was: Patch Available)
> Investigate unmatched suppressions
> --
>
> Key: CASSANDRA-18724
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18724
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
>
> Since we upgraded OWASP, it now reports unmatched suppressions ("Suppression
> Rule had zero matches") we should investigate and possibly remove.
--
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
