[jira] [Updated] (CASSANDRA-16039) FQL replay should have options to ignore DDL statements
[ https://issues.apache.org/jira/browse/CASSANDRA-16039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-16039: Reviewers: David Capwell, Marcus Eriksson > FQL replay should have options to ignore DDL statements > --- > > Key: CASSANDRA-16039 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16039 > Project: Cassandra > Issue Type: Improvement > Components: Tool/fql >Reporter: David Capwell >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 4.0-rc > > Time Spent: 20m > Remaining Estimate: 0h > > FQL logs will contain DDL statements made on the host, and the replay tool > will attempt to replay them; this can be unsafe in general so should have an > option to filter them out. > Thinking about it, since DDL replay isn’t obvious, we should most likely > default to false and have a flag to allow DDL replay as well. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16039) FQL replay should have options to ignore DDL statements
[ https://issues.apache.org/jira/browse/CASSANDRA-16039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179273#comment-17179273 ] David Capwell commented on CASSANDRA-16039: --- [~marcuse] would you be able to review? > FQL replay should have options to ignore DDL statements > --- > > Key: CASSANDRA-16039 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16039 > Project: Cassandra > Issue Type: Improvement > Components: Tool/fql >Reporter: David Capwell >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 4.0-rc > > Time Spent: 20m > Remaining Estimate: 0h > > FQL logs will contain DDL statements made on the host, and the replay tool > will attempt to replay them; this can be unsafe in general so should have an > option to filter them out. > Thinking about it, since DDL replay isn’t obvious, we should most likely > default to false and have a flag to allow DDL replay as well. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16039) FQL replay should have options to ignore DDL statements
[ https://issues.apache.org/jira/browse/CASSANDRA-16039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179272#comment-17179272 ] David Capwell commented on CASSANDRA-16039: --- Overall LGTM, only smaller comments in the cassandra PR. > FQL replay should have options to ignore DDL statements > --- > > Key: CASSANDRA-16039 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16039 > Project: Cassandra > Issue Type: Improvement > Components: Tool/fql >Reporter: David Capwell >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 4.0-rc > > Time Spent: 20m > Remaining Estimate: 0h > > FQL logs will contain DDL statements made on the host, and the replay tool > will attempt to replay them; this can be unsafe in general so should have an > option to filter them out. > Thinking about it, since DDL replay isn’t obvious, we should most likely > default to false and have a flag to allow DDL replay as well. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16054) Regression Test for Compact Storage Upgrades When Table Has Clustering and Value Column
[ https://issues.apache.org/jira/browse/CASSANDRA-16054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan West updated CASSANDRA-16054: Test and Documentation Plan: Patch is a test Status: Patch Available (was: Open) [branch | https://github.com/jrwest/cassandra/tree/jwest/16054] [tests | https://app.circleci.com/pipelines/github/jrwest/cassandra?branch=jwest%2F16054] > Regression Test for Compact Storage Upgrades When Table Has Clustering and > Value Column > > > Key: CASSANDRA-16054 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16054 > Project: Cassandra > Issue Type: Task > Components: Legacy/CQL >Reporter: Jordan West >Assignee: Jordan West >Priority: Normal > > Add a regression test that shows that dropping compact storage on tables that > have clustering columns and a value column defined are safe after upgrading > sstables in 3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16054) Regression Test for Compact Storage Upgrades When Table Has Clustering and Value Column
[ https://issues.apache.org/jira/browse/CASSANDRA-16054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan West updated CASSANDRA-16054: Change Category: Quality Assurance Complexity: Normal Component/s: Legacy/CQL Status: Open (was: Triage Needed) > Regression Test for Compact Storage Upgrades When Table Has Clustering and > Value Column > > > Key: CASSANDRA-16054 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16054 > Project: Cassandra > Issue Type: Task > Components: Legacy/CQL >Reporter: Jordan West >Assignee: Jordan West >Priority: Normal > > Add a regression test that shows that dropping compact storage on tables that > have clustering columns and a value column defined are safe after upgrading > sstables in 3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16055) StorageService exposes ensureTraceKeyspace that is used by jvm-dtest, but it should be removed and use MigrationManager.evolveSystemKeyspace instead
[ https://issues.apache.org/jira/browse/CASSANDRA-16055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-16055: -- Bug Category: Parent values: Correctness(12982)Level 1 values: API / Semantic Implementation(12988) Complexity: Low Hanging Fruit Discovered By: Code Inspection Severity: Low Status: Open (was: Triage Needed) > StorageService exposes ensureTraceKeyspace that is used by jvm-dtest, but it > should be removed and use MigrationManager.evolveSystemKeyspace instead > > > Key: CASSANDRA-16055 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16055 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > > Jvm dtest uses StorageService.ensureTraceKeyspace to register the tracing > keyspace, but doesn’t register the other distributed key spaces. This method > should not be used by dtest and instead should use > MigrationManager.evolveSystemKeyspace as it registers all keyspaces -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-16055) StorageService exposes ensureTraceKeyspace that is used by jvm-dtest, but it should be removed and use MigrationManager.evolveSystemKeyspace instead
David Capwell created CASSANDRA-16055: - Summary: StorageService exposes ensureTraceKeyspace that is used by jvm-dtest, but it should be removed and use MigrationManager.evolveSystemKeyspace instead Key: CASSANDRA-16055 URL: https://issues.apache.org/jira/browse/CASSANDRA-16055 Project: Cassandra Issue Type: Bug Components: Test/dtest Reporter: David Capwell Assignee: David Capwell Jvm dtest uses StorageService.ensureTraceKeyspace to register the tracing keyspace, but doesn’t register the other distributed key spaces. This method should not be used by dtest and instead should use MigrationManager.evolveSystemKeyspace as it registers all keyspaces -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-16054) Regression Test for Compact Storage Upgrades When Table Has Clustering and Value Column
Jordan West created CASSANDRA-16054: --- Summary: Regression Test for Compact Storage Upgrades When Table Has Clustering and Value Column Key: CASSANDRA-16054 URL: https://issues.apache.org/jira/browse/CASSANDRA-16054 Project: Cassandra Issue Type: Improvement Reporter: Jordan West Assignee: Jordan West Add a regression test that shows that dropping compact storage on tables that have clustering columns and a value column defined are safe after upgrading sstables in 3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16054) Regression Test for Compact Storage Upgrades When Table Has Clustering and Value Column
[ https://issues.apache.org/jira/browse/CASSANDRA-16054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan West updated CASSANDRA-16054: Issue Type: Task (was: Improvement) > Regression Test for Compact Storage Upgrades When Table Has Clustering and > Value Column > > > Key: CASSANDRA-16054 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16054 > Project: Cassandra > Issue Type: Task >Reporter: Jordan West >Assignee: Jordan West >Priority: Normal > > Add a regression test that shows that dropping compact storage on tables that > have clustering columns and a value column defined are safe after upgrading > sstables in 3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16053) cqlsh COPY functions broken in Python 3.8 on Mac
[
https://issues.apache.org/jira/browse/CASSANDRA-16053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Holmberg updated CASSANDRA-16053:
--
Test and Documentation Plan: I ran the repro script from the previous
ticket 500+ times, restarting C* (which was said to make it happen more) each
time.
Status: Patch Available (was: In Progress)
> cqlsh COPY functions broken in Python 3.8 on Mac
>
>
> Key: CASSANDRA-16053
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16053
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: Adam Holmberg
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta2
>
>
> {noformat}
> aholmberg-rmbp16:cassandra adamholmberg$ pyenv shell
> 3.8.2
> aholmberg-rmbp16:cassandra adamholmberg$ bin/cqlsh --debug
> Using CQL driver: '/Users/adamholmberg/code/cassandra/bin/../lib/cassandra-driver-internal-only-3.23.0.post0-1a184b99.zip/cassandra-driver-3.23.0.post0-1a184b99/cassandra/__init__.py'>
> Using connect timeout: 5 seconds
> Using 'utf-8' encoding
> Using ssl: False
> Connected to Test Cluster at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 4.0-beta2-SNAPSHOT | CQL spec 3.4.5 | Native
> protocol v4]
> Use HELP for help.
> cqlsh> copy test.testcopyto to 'asdf';
> Detected 12 core(s)
> Using 11 child processes
> Starting copy of test.testcopyto with columns [a, b, c, d].
> Traceback (most recent call last):
> File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 937, in onecmd
> self.handle_statement(st, statementtext)
> File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 974, in
> handle_statement
> return custom_handler(parsed)
> File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 1563, in
> do_copy
> task.run()
> File
> "/Users/adamholmberg/code/cassandra/bin/../pylib/cqlshlib/copyutil.py", line
> 669, in run
> self.start_processes()
> File
> "/Users/adamholmberg/code/cassandra/bin/../pylib/cqlshlib/copyutil.py", line
> 471, in start_processes
> process.start()
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/process.py",
> line 121, in start
> self._popen = self._Popen(self)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/context.py",
> line 224, in _Popen
> return _default_context.get_context().Process._Popen(process_obj)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/context.py",
> line 283, in _Popen
> return Popen(process_obj)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/popen_spawn_posix.py",
> line 32, in __init__
> super().__init__(process_obj)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/popen_fork.py",
> line 19, in __init__
> self._launch(process_obj)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/popen_spawn_posix.py",
> line 47, in _launch
> reduction.dump(process_obj, fp)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/reduction.py",
> line 60, in dump
> ForkingPickler(file, protocol).dump(obj)
> TypeError: cannot pickle '_thread.lock' object
> cqlsh>
> {noformat}
> multiprocessing uses a different default start method on Mac, and pickling
> fails trying to serialize the Cluster object.
> https://github.com/python/cpython/blob/db098bc1f05bd0773943e59f83489f05f28dedf8/Lib/multiprocessing/context.py#L313-L318
> https://bugs.python.org/issue33725
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16053) cqlsh COPY functions broken in Python 3.8 on Mac
[
https://issues.apache.org/jira/browse/CASSANDRA-16053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179246#comment-17179246
]
Adam Holmberg commented on CASSANDRA-16053:
---
[ci|https://app.circleci.com/pipelines/github/aholmberg/cassandra?branch=CASSANDRA-16053]
Everything failed so far is known to be flaky.
> cqlsh COPY functions broken in Python 3.8 on Mac
>
>
> Key: CASSANDRA-16053
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16053
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: Adam Holmberg
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta2
>
>
> {noformat}
> aholmberg-rmbp16:cassandra adamholmberg$ pyenv shell
> 3.8.2
> aholmberg-rmbp16:cassandra adamholmberg$ bin/cqlsh --debug
> Using CQL driver: '/Users/adamholmberg/code/cassandra/bin/../lib/cassandra-driver-internal-only-3.23.0.post0-1a184b99.zip/cassandra-driver-3.23.0.post0-1a184b99/cassandra/__init__.py'>
> Using connect timeout: 5 seconds
> Using 'utf-8' encoding
> Using ssl: False
> Connected to Test Cluster at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 4.0-beta2-SNAPSHOT | CQL spec 3.4.5 | Native
> protocol v4]
> Use HELP for help.
> cqlsh> copy test.testcopyto to 'asdf';
> Detected 12 core(s)
> Using 11 child processes
> Starting copy of test.testcopyto with columns [a, b, c, d].
> Traceback (most recent call last):
> File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 937, in onecmd
> self.handle_statement(st, statementtext)
> File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 974, in
> handle_statement
> return custom_handler(parsed)
> File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 1563, in
> do_copy
> task.run()
> File
> "/Users/adamholmberg/code/cassandra/bin/../pylib/cqlshlib/copyutil.py", line
> 669, in run
> self.start_processes()
> File
> "/Users/adamholmberg/code/cassandra/bin/../pylib/cqlshlib/copyutil.py", line
> 471, in start_processes
> process.start()
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/process.py",
> line 121, in start
> self._popen = self._Popen(self)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/context.py",
> line 224, in _Popen
> return _default_context.get_context().Process._Popen(process_obj)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/context.py",
> line 283, in _Popen
> return Popen(process_obj)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/popen_spawn_posix.py",
> line 32, in __init__
> super().__init__(process_obj)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/popen_fork.py",
> line 19, in __init__
> self._launch(process_obj)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/popen_spawn_posix.py",
> line 47, in _launch
> reduction.dump(process_obj, fp)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/reduction.py",
> line 60, in dump
> ForkingPickler(file, protocol).dump(obj)
> TypeError: cannot pickle '_thread.lock' object
> cqlsh>
> {noformat}
> multiprocessing uses a different default start method on Mac, and pickling
> fails trying to serialize the Cluster object.
> https://github.com/python/cpython/blob/db098bc1f05bd0773943e59f83489f05f28dedf8/Lib/multiprocessing/context.py#L313-L318
> https://bugs.python.org/issue33725
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16048) Safely Ignore Compact Storage Tables Where Users Have Defined Clustering and Value Columns
[ https://issues.apache.org/jira/browse/CASSANDRA-16048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan West updated CASSANDRA-16048: Test and Documentation Plan: Added new in-jvm dtest upgrade test. Currently, the test requires at least the preliminary patch in CASSNADRA-15946 in order to pass. Status: Patch Available (was: Open) [branch | https://github.com/jrwest/cassandra/tree/jwest/16048] [tests | https://app.circleci.com/pipelines/github/jrwest/cassandra?branch=jwest%2F16048] > Safely Ignore Compact Storage Tables Where Users Have Defined Clustering and > Value Columns > -- > > Key: CASSANDRA-16048 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16048 > Project: Cassandra > Issue Type: Improvement > Components: Legacy/CQL >Reporter: Jordan West >Assignee: Jordan West >Priority: Normal > Fix For: 4.0-beta > > > Some compact storage tables, specifically those where the user has defined > both at least one clustering and the value column, can be safely handled in > 4.0 because besides the DENSE flag they are not materially different post 3.0 > and there is no visible change to the user facing schema after dropping > compact storage. We can detect this case and allow these tables to silently > drop the DENSE flag while still throwing a start-up error for COMPACT STORAGE > tables that don’t meet the criteria. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16039) FQL replay should have options to ignore DDL statements
[ https://issues.apache.org/jira/browse/CASSANDRA-16039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179219#comment-17179219 ] Stefan Miklosovic commented on CASSANDRA-16039: --- PR: [https://github.com/apache/cassandra/pull/714] dtest PR: [https://github.com/apache/cassandra-dtest/pull/90] build: [https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/246/] > FQL replay should have options to ignore DDL statements > --- > > Key: CASSANDRA-16039 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16039 > Project: Cassandra > Issue Type: Improvement > Components: Tool/fql >Reporter: David Capwell >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 4.0-rc > > > FQL logs will contain DDL statements made on the host, and the replay tool > will attempt to replay them; this can be unsafe in general so should have an > option to filter them out. > Thinking about it, since DDL replay isn’t obvious, we should most likely > default to false and have a flag to allow DDL replay as well. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16053) cqlsh COPY functions broken in Python 3.8 on Mac
[
https://issues.apache.org/jira/browse/CASSANDRA-16053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179209#comment-17179209
]
Adam Holmberg commented on CASSANDRA-16053:
---
CASSANDRA-11749 introduced passing the cluster to clean up sockets in forked
child processes. That patch assumed that forking would be used everywhere but
Windows.
Instead of making the parameter passing logic more complex to account for
platform and runtime variations, I suggest we rely on the underlying driver fix
which was later introduced, and stop trying to pass the Cluster.
[PYTHON-577|https://datastax-oss.atlassian.net/browse/PYTHON-577]
[patch|https://github.com/apache/cassandra/compare/trunk...aholmberg:CASSANDRA-16053?expand=1]
I've run the repro script from CASSANDRA-11749 several hundred times. Stefania
indicated that it would previously reproduce within around a half dozen
iterations.
> cqlsh COPY functions broken in Python 3.8 on Mac
>
>
> Key: CASSANDRA-16053
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16053
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: Adam Holmberg
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta2
>
>
> {noformat}
> aholmberg-rmbp16:cassandra adamholmberg$ pyenv shell
> 3.8.2
> aholmberg-rmbp16:cassandra adamholmberg$ bin/cqlsh --debug
> Using CQL driver: '/Users/adamholmberg/code/cassandra/bin/../lib/cassandra-driver-internal-only-3.23.0.post0-1a184b99.zip/cassandra-driver-3.23.0.post0-1a184b99/cassandra/__init__.py'>
> Using connect timeout: 5 seconds
> Using 'utf-8' encoding
> Using ssl: False
> Connected to Test Cluster at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 4.0-beta2-SNAPSHOT | CQL spec 3.4.5 | Native
> protocol v4]
> Use HELP for help.
> cqlsh> copy test.testcopyto to 'asdf';
> Detected 12 core(s)
> Using 11 child processes
> Starting copy of test.testcopyto with columns [a, b, c, d].
> Traceback (most recent call last):
> File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 937, in onecmd
> self.handle_statement(st, statementtext)
> File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 974, in
> handle_statement
> return custom_handler(parsed)
> File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 1563, in
> do_copy
> task.run()
> File
> "/Users/adamholmberg/code/cassandra/bin/../pylib/cqlshlib/copyutil.py", line
> 669, in run
> self.start_processes()
> File
> "/Users/adamholmberg/code/cassandra/bin/../pylib/cqlshlib/copyutil.py", line
> 471, in start_processes
> process.start()
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/process.py",
> line 121, in start
> self._popen = self._Popen(self)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/context.py",
> line 224, in _Popen
> return _default_context.get_context().Process._Popen(process_obj)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/context.py",
> line 283, in _Popen
> return Popen(process_obj)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/popen_spawn_posix.py",
> line 32, in __init__
> super().__init__(process_obj)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/popen_fork.py",
> line 19, in __init__
> self._launch(process_obj)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/popen_spawn_posix.py",
> line 47, in _launch
> reduction.dump(process_obj, fp)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/reduction.py",
> line 60, in dump
> ForkingPickler(file, protocol).dump(obj)
> TypeError: cannot pickle '_thread.lock' object
> cqlsh>
> {noformat}
> multiprocessing uses a different default start method on Mac, and pickling
> fails trying to serialize the Cluster object.
> https://github.com/python/cpython/blob/db098bc1f05bd0773943e59f83489f05f28dedf8/Lib/multiprocessing/context.py#L313-L318
> https://bugs.python.org/issue33725
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16039) FQL replay should have options to ignore DDL statements
[ https://issues.apache.org/jira/browse/CASSANDRA-16039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179208#comment-17179208 ] Stefan Miklosovic commented on CASSANDRA-16039: --- one of dtest fails, I need to fix it and make a PR against cassandra-dtest too > FQL replay should have options to ignore DDL statements > --- > > Key: CASSANDRA-16039 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16039 > Project: Cassandra > Issue Type: Improvement > Components: Tool/fql >Reporter: David Capwell >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 4.0-rc > > > FQL logs will contain DDL statements made on the host, and the replay tool > will attempt to replay them; this can be unsafe in general so should have an > option to filter them out. > Thinking about it, since DDL replay isn’t obvious, we should most likely > default to false and have a flag to allow DDL replay as well. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15406) Show the progress of data streaming and index build
[ https://issues.apache.org/jira/browse/CASSANDRA-15406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179185#comment-17179185 ] David Capwell commented on CASSANDRA-15406: --- left a few comments, need to still review closer > Show the progress of data streaming and index build > > > Key: CASSANDRA-15406 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15406 > Project: Cassandra > Issue Type: Improvement > Components: Consistency/Streaming, Legacy/Streaming and Messaging, > Tool/nodetool >Reporter: maxwellguo >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 4.0, 4.x > > Time Spent: 1h 50m > Remaining Estimate: 0h > > I found that we should supply a command to show the progress of streaming > when we do the operation of bootstrap/move/decommission/removenode. For when > do data streaming , noboday knows which steps there program are in , so I > think a command to show the joing/leaving node's is needed . > > PR [https://github.com/apache/cassandra/pull/558] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16053) cqlsh COPY functions broken in Python 3.8 on Mac
[
https://issues.apache.org/jira/browse/CASSANDRA-16053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Holmberg updated CASSANDRA-16053:
--
Description:
{noformat}
aholmberg-rmbp16:cassandra adamholmberg$ pyenv shell
3.8.2
aholmberg-rmbp16:cassandra adamholmberg$ bin/cqlsh --debug
Using CQL driver:
Using connect timeout: 5 seconds
Using 'utf-8' encoding
Using ssl: False
Connected to Test Cluster at 127.0.0.1:9042.
[cqlsh 5.0.1 | Cassandra 4.0-beta2-SNAPSHOT | CQL spec 3.4.5 | Native protocol
v4]
Use HELP for help.
cqlsh> copy test.testcopyto to 'asdf';
Detected 12 core(s)
Using 11 child processes
Starting copy of test.testcopyto with columns [a, b, c, d].
Traceback (most recent call last):
File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 937, in onecmd
self.handle_statement(st, statementtext)
File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 974, in
handle_statement
return custom_handler(parsed)
File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 1563, in do_copy
task.run()
File "/Users/adamholmberg/code/cassandra/bin/../pylib/cqlshlib/copyutil.py",
line 669, in run
self.start_processes()
File "/Users/adamholmberg/code/cassandra/bin/../pylib/cqlshlib/copyutil.py",
line 471, in start_processes
process.start()
File
"/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/process.py",
line 121, in start
self._popen = self._Popen(self)
File
"/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/context.py",
line 224, in _Popen
return _default_context.get_context().Process._Popen(process_obj)
File
"/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/context.py",
line 283, in _Popen
return Popen(process_obj)
File
"/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/popen_spawn_posix.py",
line 32, in __init__
super().__init__(process_obj)
File
"/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/popen_fork.py",
line 19, in __init__
self._launch(process_obj)
File
"/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/popen_spawn_posix.py",
line 47, in _launch
reduction.dump(process_obj, fp)
File
"/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/reduction.py",
line 60, in dump
ForkingPickler(file, protocol).dump(obj)
TypeError: cannot pickle '_thread.lock' object
cqlsh>
{noformat}
multiprocessing uses a different default start method on Mac, and pickling
fails trying to serialize the Cluster object.
https://github.com/python/cpython/blob/db098bc1f05bd0773943e59f83489f05f28dedf8/Lib/multiprocessing/context.py#L313-L318
https://bugs.python.org/issue33725
was:
{noformat}
aholmberg-rmbp16:cassandra adamholmberg$ pyenv shell
3.8.2
aholmberg-rmbp16:cassandra adamholmberg$ bin/cqlsh --debug
Using CQL driver:
Using connect timeout: 5 seconds
Using 'utf-8' encoding
Using ssl: False
Connected to Test Cluster at 127.0.0.1:9042.
[cqlsh 5.0.1 | Cassandra 4.0-beta2-SNAPSHOT | CQL spec 3.4.5 | Native protocol
v4]
Use HELP for help.
cqlsh> copy test.testcopyto to 'asdf';
Detected 12 core(s)
Using 11 child processes
Starting copy of test.testcopyto with columns [a, b, c, d].
Traceback (most recent call last):
File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 937, in onecmd
self.handle_statement(st, statementtext)
File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 974, in
handle_statement
return custom_handler(parsed)
File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 1563, in do_copy
task.run()
File "/Users/adamholmberg/code/cassandra/bin/../pylib/cqlshlib/copyutil.py",
line 669, in run
self.start_processes()
File "/Users/adamholmberg/code/cassandra/bin/../pylib/cqlshlib/copyutil.py",
line 471, in start_processes
process.start()
File
"/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/process.py",
line 121, in start
self._popen = self._Popen(self)
File
"/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/context.py",
line 224, in _Popen
return _default_context.get_context().Process._Popen(process_obj)
File
"/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/context.py",
line 283, in _Popen
return Popen(process_obj)
File
"/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/popen_spawn_posix.py",
line 32, in __init__
super().__init__(process_obj)
File
"/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/popen_fork.py",
line 19, in __init__
self._launch(process_obj)
File
"/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/popen_spawn_posix.py",
line 47, in _launch
reduction.dump(process_obj, fp)
File
[jira] [Updated] (CASSANDRA-16053) cqlsh COPY functions broken in Python 3.8 on Mac
[
https://issues.apache.org/jira/browse/CASSANDRA-16053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Holmberg updated CASSANDRA-16053:
--
Bug Category: Parent values: Code(13163)Level 1 values: Bug - Unclear
Impact(13164)
Complexity: Normal
Discovered By: Unit Test
Fix Version/s: 4.0-beta2
Platform: (was: All)
Severity: Low
Status: Open (was: Triage Needed)
> cqlsh COPY functions broken in Python 3.8 on Mac
>
>
> Key: CASSANDRA-16053
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16053
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: Adam Holmberg
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta2
>
>
> {noformat}
> aholmberg-rmbp16:cassandra adamholmberg$ pyenv shell
> 3.8.2
> aholmberg-rmbp16:cassandra adamholmberg$ bin/cqlsh --debug
> Using CQL driver: '/Users/adamholmberg/code/cassandra/bin/../lib/cassandra-driver-internal-only-3.23.0.post0-1a184b99.zip/cassandra-driver-3.23.0.post0-1a184b99/cassandra/__init__.py'>
> Using connect timeout: 5 seconds
> Using 'utf-8' encoding
> Using ssl: False
> Connected to Test Cluster at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 4.0-beta2-SNAPSHOT | CQL spec 3.4.5 | Native
> protocol v4]
> Use HELP for help.
> cqlsh> copy test.testcopyto to 'asdf';
> Detected 12 core(s)
> Using 11 child processes
> Starting copy of test.testcopyto with columns [a, b, c, d].
> Traceback (most recent call last):
> File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 937, in onecmd
> self.handle_statement(st, statementtext)
> File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 974, in
> handle_statement
> return custom_handler(parsed)
> File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 1563, in
> do_copy
> task.run()
> File
> "/Users/adamholmberg/code/cassandra/bin/../pylib/cqlshlib/copyutil.py", line
> 669, in run
> self.start_processes()
> File
> "/Users/adamholmberg/code/cassandra/bin/../pylib/cqlshlib/copyutil.py", line
> 471, in start_processes
> process.start()
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/process.py",
> line 121, in start
> self._popen = self._Popen(self)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/context.py",
> line 224, in _Popen
> return _default_context.get_context().Process._Popen(process_obj)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/context.py",
> line 283, in _Popen
> return Popen(process_obj)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/popen_spawn_posix.py",
> line 32, in __init__
> super().__init__(process_obj)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/popen_fork.py",
> line 19, in __init__
> self._launch(process_obj)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/popen_spawn_posix.py",
> line 47, in _launch
> reduction.dump(process_obj, fp)
> File
> "/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/reduction.py",
> line 60, in dump
> ForkingPickler(file, protocol).dump(obj)
> TypeError: cannot pickle '_thread.lock' object
> cqlsh>
> {noformat}
> `multiprocessing` uses a different start method on Mac.
> https://github.com/python/cpython/blob/db098bc1f05bd0773943e59f83489f05f28dedf8/Lib/multiprocessing/context.py#L313-L318
> https://bugs.python.org/issue33725
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-16053) cqlsh COPY functions broken in Python 3.8 on Mac
Adam Holmberg created CASSANDRA-16053:
-
Summary: cqlsh COPY functions broken in Python 3.8 on Mac
Key: CASSANDRA-16053
URL: https://issues.apache.org/jira/browse/CASSANDRA-16053
Project: Cassandra
Issue Type: Bug
Components: Tool/cqlsh
Reporter: Adam Holmberg
Assignee: Adam Holmberg
{noformat}
aholmberg-rmbp16:cassandra adamholmberg$ pyenv shell
3.8.2
aholmberg-rmbp16:cassandra adamholmberg$ bin/cqlsh --debug
Using CQL driver:
Using connect timeout: 5 seconds
Using 'utf-8' encoding
Using ssl: False
Connected to Test Cluster at 127.0.0.1:9042.
[cqlsh 5.0.1 | Cassandra 4.0-beta2-SNAPSHOT | CQL spec 3.4.5 | Native protocol
v4]
Use HELP for help.
cqlsh> copy test.testcopyto to 'asdf';
Detected 12 core(s)
Using 11 child processes
Starting copy of test.testcopyto with columns [a, b, c, d].
Traceback (most recent call last):
File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 937, in onecmd
self.handle_statement(st, statementtext)
File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 974, in
handle_statement
return custom_handler(parsed)
File "/Users/adamholmberg/code/cassandra/bin/cqlsh.py", line 1563, in do_copy
task.run()
File "/Users/adamholmberg/code/cassandra/bin/../pylib/cqlshlib/copyutil.py",
line 669, in run
self.start_processes()
File "/Users/adamholmberg/code/cassandra/bin/../pylib/cqlshlib/copyutil.py",
line 471, in start_processes
process.start()
File
"/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/process.py",
line 121, in start
self._popen = self._Popen(self)
File
"/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/context.py",
line 224, in _Popen
return _default_context.get_context().Process._Popen(process_obj)
File
"/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/context.py",
line 283, in _Popen
return Popen(process_obj)
File
"/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/popen_spawn_posix.py",
line 32, in __init__
super().__init__(process_obj)
File
"/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/popen_fork.py",
line 19, in __init__
self._launch(process_obj)
File
"/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/popen_spawn_posix.py",
line 47, in _launch
reduction.dump(process_obj, fp)
File
"/Users/adamholmberg/.pyenv/versions/3.8.2/lib/python3.8/multiprocessing/reduction.py",
line 60, in dump
ForkingPickler(file, protocol).dump(obj)
TypeError: cannot pickle '_thread.lock' object
cqlsh>
{noformat}
`multiprocessing` uses a different start method on Mac.
https://github.com/python/cpython/blob/db098bc1f05bd0773943e59f83489f05f28dedf8/Lib/multiprocessing/context.py#L313-L318
https://bugs.python.org/issue33725
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15406) Show the progress of data streaming and index build
[ https://issues.apache.org/jira/browse/CASSANDRA-15406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15406: -- Reviewers: Benjamin Lerer, Berenguer Blasi, David Capwell, David Capwell (was: Benjamin Lerer, Berenguer Blasi, David Capwell) Benjamin Lerer, Berenguer Blasi, David Capwell, David Capwell (was: Benjamin Lerer, Berenguer Blasi) Status: Review In Progress (was: Patch Available) > Show the progress of data streaming and index build > > > Key: CASSANDRA-15406 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15406 > Project: Cassandra > Issue Type: Improvement > Components: Consistency/Streaming, Legacy/Streaming and Messaging, > Tool/nodetool >Reporter: maxwellguo >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 4.0, 4.x > > Time Spent: 1h 40m > Remaining Estimate: 0h > > I found that we should supply a command to show the progress of streaming > when we do the operation of bootstrap/move/decommission/removenode. For when > do data streaming , noboday knows which steps there program are in , so I > think a command to show the joing/leaving node's is needed . > > PR [https://github.com/apache/cassandra/pull/558] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15990) Running CQL command with non-ASCII values raises UnicodeDecodeError
[
https://issues.apache.org/jira/browse/CASSANDRA-15990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179170#comment-17179170
]
David Capwell commented on CASSANDRA-15990:
---
Thanks. code LGTM +1.
[~djoshi] can you review as well?
> Running CQL command with non-ASCII values raises UnicodeDecodeError
> ---
>
> Key: CASSANDRA-15990
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15990
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: Joseph Chu
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.0-beta
>
>
> There are INSERT statements that contains non-ASCII values that have run fine
> in Cassandra 3.11, but now raises a UnicodeDecodeError when I try executing
> them in 4.0-alpha4 and 4.0-beta1.
> Example input and output:
> {code:java}
> echo $LANG
> en_US.UTF-8
> $ cqlsh --debug
> Using CQL driver: '/usr/share/cassandra/bin/../lib/cassandra-driver-internal-only-3.23.0.post0-1a184b99.zip/cassandra-driver-3.23.0.post0-1a184b99/cassandra/__init__.py'>
> Using connect timeout: 5 seconds
> Using 'utf-8' encoding
> Using ssl: False
> Connected to Cassandra Cluster at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 4.0-beta1 | CQL spec 3.4.5 | Native protocol v4]
> Use HELP for help.
> cqlsh> CREATE KEYSPACE killr_video WITH replication = {'class':
> 'NetworkTopologyStrategy', 'DC-Houston': 1};
> cqlsh> USE killr_video;
> cqlsh:killr_video> CREATE TABLE movies_by_genre ( genre TEXT, title TEXT,
> year INT, duration INT, avg_rating FLOAT, country TEXT, PRIMARY KEY ((genre),
> title, year));
> cqlsh:killr_video> INSERT INTO movies_by_genre (genre, title, year, duration,
> avg_rating, country)
> ... VALUES ('Action', 'The Extraordinary Adventures of Adèle Blanc-Sec',
> 2010, 107, 6.30, 'France');
> Traceback (most recent call last):
> File "/usr/share/cassandra/bin/cqlsh.py", line 937, in onecmd
> self.handle_statement(st, statementtext)
> File "/usr/share/cassandra/bin/cqlsh.py", line 962, in handle_statement
> readline.add_history(new_hist)
> UnicodeEncodeError: 'ascii' codec can't encode character u'\xe8' in position
> 134: ordinal not in range(128){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15828) Remove jackson-mapper-asl-1.9.13 to address CVE
[ https://issues.apache.org/jira/browse/CASSANDRA-15828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179164#comment-17179164 ] Kevin Eveker commented on CASSANDRA-15828: -- [~mdenihan] Thanks. Should I close this ticket? > Remove jackson-mapper-asl-1.9.13 to address CVE > --- > > Key: CASSANDRA-15828 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15828 > Project: Cassandra > Issue Type: Improvement >Reporter: Kevin Eveker >Priority: Normal > > Recent scan results identified the following CVE that require this upgrade to > address > [https://nvd.nist.gov/vuln/detail/CVE-2019-10172] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15762) Update Bundled Python Driver to the latest release
[ https://issues.apache.org/jira/browse/CASSANDRA-15762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179137#comment-17179137 ] Alexandre Dutra commented on CASSANDRA-15762: - See my comment on CASSANDRA-13951. At a minimum we need a Python driver release with support for: # CASSANDRA-10786 (result set metadata changes, first released in 3.12, see [PYTHON-808|https://datastax-oss.atlassian.net/browse/PYTHON-808]) # CASSANDRA-10145 (keyspace per query, first released in 3.12, see [PYTHON-678|https://datastax-oss.atlassian.net/browse/PYTHON-678]) # --CASSANDRA-7622 (virtual tables, first released in 3.15, see [PYTHON-992|https://datastax-oss.atlassian.net/browse/PYTHON-992]) # CASSANDRA-7544 (different ports per node, first released in 3.23, see [PYTHON-700|https://datastax-oss.atlassian.net/browse/PYTHON-700]) # CASSANDRA-15299 (protocol checksumming changes, currently under development for 3.25) To summarize, if 15299 lands we need to wait for 3.25; otherwise, 3.23 or higher will do. > Update Bundled Python Driver to the latest release > -- > > Key: CASSANDRA-15762 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15762 > Project: Cassandra > Issue Type: Task > Components: Tool/cqlsh >Reporter: Alan Boudreault >Priority: Normal > Fix For: 4.0-beta > > > This is not urgent for now since there are some missing 4.x features that > need to be implemented on the driver (checksum). This ticket is to make sure > we update the bundled driver before GA. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16039) FQL replay should have options to ignore DDL statements
[ https://issues.apache.org/jira/browse/CASSANDRA-16039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179136#comment-17179136 ] Stefan Miklosovic commented on CASSANDRA-16039: --- PR: [https://github.com/apache/cassandra/pull/714] test: [https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/245/] > FQL replay should have options to ignore DDL statements > --- > > Key: CASSANDRA-16039 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16039 > Project: Cassandra > Issue Type: Improvement > Components: Tool/fql >Reporter: David Capwell >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 4.0-rc > > > FQL logs will contain DDL statements made on the host, and the replay tool > will attempt to replay them; this can be unsafe in general so should have an > option to filter them out. > Thinking about it, since DDL replay isn’t obvious, we should most likely > default to false and have a flag to allow DDL replay as well. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15762) Update Bundled Python Driver to the latest release
[ https://issues.apache.org/jira/browse/CASSANDRA-15762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179137#comment-17179137 ] Alexandre Dutra edited comment on CASSANDRA-15762 at 8/17/20, 5:11 PM: --- See my comment on CASSANDRA-13951. At a minimum we need a Python driver release with support for: # CASSANDRA-10786 (result set metadata changes, first released in 3.12, see [PYTHON-808|https://datastax-oss.atlassian.net/browse/PYTHON-808]) # CASSANDRA-10145 (keyspace per query, first released in 3.12, see [PYTHON-678|https://datastax-oss.atlassian.net/browse/PYTHON-678]) # CASSANDRA-7622 (virtual tables, first released in 3.15, see [PYTHON-992|https://datastax-oss.atlassian.net/browse/PYTHON-992]) # CASSANDRA-7544 (different ports per node, first released in 3.23, see [PYTHON-700|https://datastax-oss.atlassian.net/browse/PYTHON-700]) # CASSANDRA-15299 (protocol checksumming changes, currently under development for 3.25) To summarize, if 15299 lands we need to wait for 3.25; otherwise, 3.23 or higher will do. was (Author: adutra): See my comment on CASSANDRA-13951. At a minimum we need a Python driver release with support for: # CASSANDRA-10786 (result set metadata changes, first released in 3.12, see [PYTHON-808|https://datastax-oss.atlassian.net/browse/PYTHON-808]) # CASSANDRA-10145 (keyspace per query, first released in 3.12, see [PYTHON-678|https://datastax-oss.atlassian.net/browse/PYTHON-678]) # --CASSANDRA-7622 (virtual tables, first released in 3.15, see [PYTHON-992|https://datastax-oss.atlassian.net/browse/PYTHON-992]) # CASSANDRA-7544 (different ports per node, first released in 3.23, see [PYTHON-700|https://datastax-oss.atlassian.net/browse/PYTHON-700]) # CASSANDRA-15299 (protocol checksumming changes, currently under development for 3.25) To summarize, if 15299 lands we need to wait for 3.25; otherwise, 3.23 or higher will do. > Update Bundled Python Driver to the latest release > -- > > Key: CASSANDRA-15762 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15762 > Project: Cassandra > Issue Type: Task > Components: Tool/cqlsh >Reporter: Alan Boudreault >Priority: Normal > Fix For: 4.0-beta > > > This is not urgent for now since there are some missing 4.x features that > need to be implemented on the driver (checksum). This ticket is to make sure > we update the bundled driver before GA. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13951) Release Java and Python drivers and re-enable build.xml driver dep
[
https://issues.apache.org/jira/browse/CASSANDRA-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179112#comment-17179112
]
Alexandre Dutra commented on CASSANDRA-13951:
-
Support for CASSANDRA-10786 has been released already:
# Java driver: released in 3.3.2 (see
[JAVA-1196|https://datastax-oss.atlassian.net/browse/JAVA-1196])
# Python driver: released in 3.12.0 (see
[PYTHON-808|https://datastax-oss.atlassian.net/browse/PYTHON-808])
If protocol v5 ships as is in C* 4.0 then any driver version equal to or higher
than the above will do – except for Java driver versions >= 3.10 (see below).
_However_: if CASSANDRA-15299 is merged and included in the final 4.0 GA, then
we have a totally different story to handle: we need to wait for Java driver
3.11.0 and Python driver 3.25.0. These versions are currently being prepared
and they will provide full & definitive support for both 10786 and 15299.
> Release Java and Python drivers and re-enable build.xml driver dep
> --
>
> Key: CASSANDRA-13951
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13951
> Project: Cassandra
> Issue Type: Task
> Components: Build, Dependencies
>Reporter: Alex Petrov
>Assignee: Alex Petrov
>Priority: Urgent
> Fix For: 4.0, 4.x
>
>
> During [CASSANDRA-10786], driver changes were introduced that required a
> snapshot release of both drivers.
> When the stable driver version is published, we have to update the driver
> dependencies in {{lib}} and un-comment {{build.xml}} sections with
> {{java-driver}} information for correct publish of 4.0. This manipulation was
> required in order to account for the chicken-or-egg problem between Cassandra
> itself and the drivers.
> This absolutely has to be done before 4.0 & there should be no release
> without making sure right drivers are in place.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update
[ https://issues.apache.org/jira/browse/CASSANDRA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever reassigned CASSANDRA-16046: -- Assignee: Michael Semb Wever (was: Mick Semb Wever) > BLOG - Post about Cassandra & Kubernetes - SIG Update > - > > Key: CASSANDRA-16046 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16046 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Michael Semb Wever >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-beta2 > > > We're getting a blog post out before/coinciding with Kubecon 2020. Content > code is mostly ready > > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update
[ https://issues.apache.org/jira/browse/CASSANDRA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16046: --- Authors: Michael Semb Wever (was: Mick Semb Wever) > BLOG - Post about Cassandra & Kubernetes - SIG Update > - > > Key: CASSANDRA-16046 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16046 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Mick Semb Wever >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-beta2 > > > We're getting a blog post out before/coinciding with Kubecon 2020. Content > code is mostly ready > > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update
[
https://issues.apache.org/jira/browse/CASSANDRA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179094#comment-17179094
]
Michael Semb Wever commented on CASSANDRA-16046:
After
[some|https://the-asf.slack.com/archives/CK23JSY2K/p1597679760024000?thread_ts=1597668205.021700=CK23JSY2K]
peer-review, it is now pushed to the {{asf-site}} branch and published.
> BLOG - Post about Cassandra & Kubernetes - SIG Update
> -
>
> Key: CASSANDRA-16046
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16046
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Mick Semb Wever
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-beta2
>
>
> We're getting a blog post out before/coinciding with Kubecon 2020. Content
> code is mostly ready
>
>
> [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-site updated (47d20f0 -> 1aff090)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch asf-site in repository https://gitbox.apache.org/repos/asf/cassandra-website.git. discard 47d20f0 generate docs for b4337fbb add ecb519d Blog post about Cassandra & Kubernetes - SIG Update add 1aff090 generate docs for ecb519dc 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 (47d20f0) \ N -- N -- N refs/heads/asf-site (1aff090) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. No new revisions were added by this update. Summary of changes: .../08/14/cassandra-and-kubernetes-sig-update.html | 229 + content/blog/index.html| 18 +- content/blog/page2/index.html | 9 + .../configuration/cassandra_config_file.html | 9 + content/doc/3.11.8/operating/metrics.html | 219 content/doc/3.11.8/searchindex.js | 2 +- .../3.11/configuration/cassandra_config_file.html | 9 + content/doc/3.11/operating/metrics.html| 219 content/doc/3.11/searchindex.js| 2 +- .../configuration/cassandra_config_file.html | 8 + content/doc/4.0-beta2/cql/ddl.html | 36 +-- content/doc/4.0-beta2/cql/types.html | 2 + content/doc/4.0-beta2/development/testing.html | 2 +- content/doc/4.0-beta2/objects.inv | Bin 9809 -> 9803 bytes content/doc/4.0-beta2/operating/metrics.html | 279 - content/doc/4.0-beta2/searchindex.js | 2 +- .../configuration/cassandra_config_file.html | 8 + content/doc/latest/cql/ddl.html| 36 +-- content/doc/latest/cql/types.html | 2 + content/doc/latest/development/testing.html| 2 +- content/doc/latest/objects.inv | Bin 9809 -> 9803 bytes content/doc/latest/operating/metrics.html | 279 - content/doc/latest/searchindex.js | 2 +- .../configuration/cassandra_config_file.html | 9 + content/doc/stable/operating/metrics.html | 219 content/doc/stable/searchindex.js | 2 +- content/feed.xml | 78 +- .../operator-capabilities.png | Bin 0 -> 48785 bytes .../single-region-multi-datacenter.png | Bin 0 -> 156440 bytes .../single-region-single-datacenter.png| Bin 0 -> 117544 bytes ...14-cassandra-and-kubernetes-sig-update.markdown | 67 + .../configuration/cassandra_config_file.rst.txt| 9 + src/doc/3.11.8/_sources/operating/metrics.rst.txt | 114 + .../configuration/cassandra_config_file.html | 9 + src/doc/3.11.8/operating/metrics.html | 219 src/doc/3.11.8/searchindex.js | 2 +- .../configuration/cassandra_config_file.rst.txt| 9 + src/doc/4.0-beta2/_sources/cql/ddl.rst.txt | 35 +-- src/doc/4.0-beta2/_sources/cql/types.rst.txt | 3 + .../4.0-beta2/_sources/development/testing.rst.txt | 2 +- .../4.0-beta2/_sources/operating/metrics.rst.txt | 144 +-- .../configuration/cassandra_config_file.html | 8 + src/doc/4.0-beta2/cql/ddl.html | 36 +-- src/doc/4.0-beta2/cql/types.html | 2 + src/doc/4.0-beta2/development/testing.html | 2 +- src/doc/4.0-beta2/objects.inv | Bin 9809 -> 9803 bytes src/doc/4.0-beta2/operating/metrics.html | 279 - src/doc/4.0-beta2/searchindex.js | 2 +- .../.placeholder | 1 + .../operator-capabilities.png | Bin 0 -> 48785 bytes .../single-region-multi-datacenter.png | Bin 0 -> 156440 bytes .../single-region-single-datacenter.png| Bin 0 -> 117544 bytes 52 files changed, 652 insertions(+), 1973 deletions(-) create mode 100644 content/blog/2020/08/14/cassandra-and-kubernetes-sig-update.html create mode 100644 content/img/blog-post-cassandra-and-kubernetes-sig-update/operator-capabilities.png create mode 100644 content/img/blog-post-cassandra-and-kubernetes-sig-update/single-region-multi-datacenter.png create mode 100644
[cassandra-website] branch asf-staging updated (47d20f0 -> 1aff090)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git. omit 47d20f0 generate docs for b4337fbb add ecb519d Blog post about Cassandra & Kubernetes - SIG Update new 1aff090 generate docs for ecb519dc 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 (47d20f0) \ N -- N -- N refs/heads/asf-staging (1aff090) 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: .../08/14/cassandra-and-kubernetes-sig-update.html | 229 + content/blog/index.html| 18 +- content/blog/page2/index.html | 9 + .../configuration/cassandra_config_file.html | 9 + content/doc/3.11.8/operating/metrics.html | 219 content/doc/3.11.8/searchindex.js | 2 +- .../3.11/configuration/cassandra_config_file.html | 9 + content/doc/3.11/operating/metrics.html| 219 content/doc/3.11/searchindex.js| 2 +- .../configuration/cassandra_config_file.html | 8 + content/doc/4.0-beta2/cql/ddl.html | 36 +-- content/doc/4.0-beta2/cql/types.html | 2 + content/doc/4.0-beta2/development/testing.html | 2 +- content/doc/4.0-beta2/objects.inv | Bin 9809 -> 9803 bytes content/doc/4.0-beta2/operating/metrics.html | 279 - content/doc/4.0-beta2/searchindex.js | 2 +- .../configuration/cassandra_config_file.html | 8 + content/doc/latest/cql/ddl.html| 36 +-- content/doc/latest/cql/types.html | 2 + content/doc/latest/development/testing.html| 2 +- content/doc/latest/objects.inv | Bin 9809 -> 9803 bytes content/doc/latest/operating/metrics.html | 279 - content/doc/latest/searchindex.js | 2 +- .../configuration/cassandra_config_file.html | 9 + content/doc/stable/operating/metrics.html | 219 content/doc/stable/searchindex.js | 2 +- content/feed.xml | 78 +- .../operator-capabilities.png | Bin 0 -> 48785 bytes .../single-region-multi-datacenter.png | Bin 0 -> 156440 bytes .../single-region-single-datacenter.png| Bin 0 -> 117544 bytes ...14-cassandra-and-kubernetes-sig-update.markdown | 67 + .../configuration/cassandra_config_file.rst.txt| 9 + src/doc/3.11.8/_sources/operating/metrics.rst.txt | 114 + .../configuration/cassandra_config_file.html | 9 + src/doc/3.11.8/operating/metrics.html | 219 src/doc/3.11.8/searchindex.js | 2 +- .../configuration/cassandra_config_file.rst.txt| 9 + src/doc/4.0-beta2/_sources/cql/ddl.rst.txt | 35 +-- src/doc/4.0-beta2/_sources/cql/types.rst.txt | 3 + .../4.0-beta2/_sources/development/testing.rst.txt | 2 +- .../4.0-beta2/_sources/operating/metrics.rst.txt | 144 +-- .../configuration/cassandra_config_file.html | 8 + src/doc/4.0-beta2/cql/ddl.html | 36 +-- src/doc/4.0-beta2/cql/types.html | 2 + src/doc/4.0-beta2/development/testing.html | 2 +- src/doc/4.0-beta2/objects.inv | Bin 9809 -> 9803 bytes src/doc/4.0-beta2/operating/metrics.html | 279 - src/doc/4.0-beta2/searchindex.js | 2 +- .../.placeholder | 1 + .../operator-capabilities.png | Bin 0 -> 48785 bytes .../single-region-multi-datacenter.png | Bin 0 -> 156440 bytes .../single-region-single-datacenter.png| Bin 0 -> 117544 bytes 52 files changed, 652 insertions(+), 1973 deletions(-) create mode 100644 content/blog/2020/08/14/cassandra-and-kubernetes-sig-update.html create mode 100644
[jira] [Updated] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update
[ https://issues.apache.org/jira/browse/CASSANDRA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16046: --- Fix Version/s: 4.0-beta2 Source Control Link: https://github.com/apache/cassandra-website/commit/ecb519dc1cb84477d1be604a0d88628911807001 Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed as [ecb519dc1cb84477d1be604a0d88628911807001|https://github.com/apache/cassandra-website/commit/ecb519dc1cb84477d1be604a0d88628911807001] > BLOG - Post about Cassandra & Kubernetes - SIG Update > - > > Key: CASSANDRA-16046 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16046 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Mick Semb Wever >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-beta2 > > > We're getting a blog post out before/coinciding with Kubecon 2020. Content > code is mostly ready > > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch master updated: Blog post about Cassandra & Kubernetes - SIG Update
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/cassandra-website.git The following commit(s) were added to refs/heads/master by this push: new ecb519d Blog post about Cassandra & Kubernetes - SIG Update ecb519d is described below commit ecb519dc1cb84477d1be604a0d88628911807001 Author: Rahul Singh AuthorDate: Wed Aug 12 18:30:12 2020 -0400 Blog post about Cassandra & Kubernetes - SIG Update patch by Rahul Singh; reviewed by Melissa Logan, John Sanda, Mick Semb Wever, Christopher Bradford, Cyril Scetbon, Francisca Fanucchi, Jim Dickinson for CASSANDRA-16046 --- ...14-cassandra-and-kubernetes-sig-update.markdown | 67 + .../.placeholder | 1 + .../operator-capabilities.png | Bin 0 -> 48785 bytes .../single-region-multi-datacenter.png | Bin 0 -> 156440 bytes .../single-region-single-datacenter.png| Bin 0 -> 117544 bytes 5 files changed, 68 insertions(+) diff --git a/src/_posts/2020-08-14-cassandra-and-kubernetes-sig-update.markdown b/src/_posts/2020-08-14-cassandra-and-kubernetes-sig-update.markdown new file mode 100644 index 000..992472b --- /dev/null +++ b/src/_posts/2020-08-14-cassandra-and-kubernetes-sig-update.markdown @@ -0,0 +1,67 @@ +--- +layout: post +title: "Cassandra and Kubernetes: SIG Update and Survey" +date: 2020-08-14 05:00:00 +0200 +author: the Apache Cassandra Community +categories: blog +--- + +Five operators for Apache Cassandra have been created that have made it easier to run containerized Cassandra on Kubernetes. Recently the major contributors to these operators came together to discuss the creation of a community-based operator with the intent of making one that makes it easy to run C* on K8s. One of the project’s organizational goals is that the end result will eventually become part of the Apache Software Foundation or the Apache Cassandra project. + +The community created a special interest group (SIG) to set goals for what the operator should do at different levels to find a path for creating a standard community-based operator. The Operator Framework suggests five maturity levels for [operator capabilities](https://operatorframework.io/operator-capabilities/) starting from basic installation to auto-pilot. + + + +(Source: [OperatorFramework.io](https://operatorframework.io/operator-capabilities/)) + +The five Cassandra Kubernetes operators all come from different backgrounds, so the first major goal is to develop a common understanding as to what an operator needs to do and at which level. This first step involves collaborating on a Custom Resource Definition (CRD) that will set the syntax / schema which will be used to create Cassandra clusters on Kubernetes. Once this is done, a software extension can be developed in a variety of languages including Go, Java, or using the Operator [...] + +We’re not starting from zero, as the creators of the five operators are actively participating in the SIG. Hopefully much of the decided upon CRD will have code fragments that can be leveraged from the other projects. The [major operators out publicly today](https://github.com/Anant/awesome-cassandra/blob/master/README.md#deploying-cassandra-on-kubernetes--kubernetized-cassandra) are those by Sky UK, Orange Telecom, Instaclustr, Elassandra, and DataStax (list sourced from the [awesome-ca [...] + +* [CassKop - Cassandra Kubernetes Operator](https://github.com/Orange-OpenSource/cassandra-k8s-operator) - This Kubernetes operator by Orange automates Cassandra operations such as deploying a new rack aware cluster, adding/removing nodes, configuring the C and JVM parameters, upgrading JVM and C versions. Written in Go. This one was also one of the first ones out and is the only one that can support multiple Kubernetes clusters using [Multi-CassKop](https://orange-opensource.github.io/c [...] +* [Cassandra Operator](https://github.com/sky-uk/cassandra-operator) - A Kubernetes operator by SkyUK that manages Cassandra clusters inside Kubernetes. Well designed and organized. This was among the first operators to be released. +* [Instaclustr - Kubernetes Operator for Cassandra operator](https://github.com/instaclustr/cassandra-operator) - The Cassandra operator by Instaclustr manages Cassandra clusters deployed to Kubernetes and automates tasks related to operating an Cassandra cluster. +* [Cass Operator](https://github.com/datastax/cass-operator) - DataStax's Kubernetes Operator supports Apache Cassandra as well as DSE containers on Kubernetes. Cassandra configuration is managed directly in the CRD, and Cassandra nodes are managed via a RESTful management API. +* [Elassandra
[jira] [Updated] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update
[ https://issues.apache.org/jira/browse/CASSANDRA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16046: --- Status: Ready to Commit (was: Review In Progress) > BLOG - Post about Cassandra & Kubernetes - SIG Update > - > > Key: CASSANDRA-16046 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16046 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Mick Semb Wever >Priority: Normal > Labels: pull-request-available > > We're getting a blog post out before/coinciding with Kubecon 2020. Content > code is mostly ready > > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update
[ https://issues.apache.org/jira/browse/CASSANDRA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179048#comment-17179048 ] Michael Semb Wever commented on CASSANDRA-16046: The new PR is [here|https://github.com/apache/cassandra-website/pull/16]. > BLOG - Post about Cassandra & Kubernetes - SIG Update > - > > Key: CASSANDRA-16046 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16046 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Mick Semb Wever >Priority: Normal > Labels: pull-request-available > > We're getting a blog post out before/coinciding with Kubecon 2020. Content > code is mostly ready > > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update
[ https://issues.apache.org/jira/browse/CASSANDRA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16046: --- Reviewers: Michael Semb Wever, Michael Semb Wever (was: Michael Semb Wever) Michael Semb Wever, Michael Semb Wever Status: Review In Progress (was: Patch Available) > BLOG - Post about Cassandra & Kubernetes - SIG Update > - > > Key: CASSANDRA-16046 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16046 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Mick Semb Wever >Priority: Normal > Labels: pull-request-available > > We're getting a blog post out before/coinciding with Kubecon 2020. Content > code is mostly ready > > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15828) Remove jackson-mapper-asl-1.9.13 to address CVE
[ https://issues.apache.org/jira/browse/CASSANDRA-15828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179040#comment-17179040 ] Brandon Williams commented on CASSANDRA-15828: -- bq. Will this fix be implemented on 2.2 / 3.0 versions as well? I'm open to backports if you'd like to submit a patch. > Remove jackson-mapper-asl-1.9.13 to address CVE > --- > > Key: CASSANDRA-15828 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15828 > Project: Cassandra > Issue Type: Improvement >Reporter: Kevin Eveker >Priority: Normal > > Recent scan results identified the following CVE that require this upgrade to > address > [https://nvd.nist.gov/vuln/detail/CVE-2019-10172] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15828) Remove jackson-mapper-asl-1.9.13 to address CVE
[
https://issues.apache.org/jira/browse/CASSANDRA-15828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179031#comment-17179031
]
Mark Denihan commented on CASSANDRA-15828:
--
[~c3-keveker] It's been removed, as I listed above, apparently as part of
CASSANDRA-15867
{code}
Author: Stefan Miklosovic 2020-06-13
16:09:00
Committer: Brandon Williams 2020-06-17 17:21:35
Parent: e49853914bd407827093cebf5151db0ebe2eba9e (Merge branch 'cassandra-3.0'
into cassandra-3.11)
Child: ac289270f2bb3bb7251319f7f71d6c66a4272db4 (Merge branch 'cassandra-3.0'
into cassandra-3.11)
Branches: 3.11.7, cassandra-3.11, remotes/origin/cassandra-3.11,
remotes/origin/trunk, trunk
Follows: cassandra-3.11.6
Precedes: cassandra-3.11.7
update Jackson to 2.9.10
Patch by Stefan Miklosovic, reviewed by brandonwilliams for
CASSANDRA-15867
-- build.xml --
index 0724dbb29c..25a47335b9 100644
@@ -406,8 +406,9 @@
-
-
+
+
+
@@ -627,8 +628,9 @@
-
-
+
+
+
{code}
This will result in the issue no longer being detected in your security scans.
Please re-run them to confirm.
Will this fix be implemented on 2.2 / 3.0 versions as well?
> Remove jackson-mapper-asl-1.9.13 to address CVE
> ---
>
> Key: CASSANDRA-15828
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15828
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Kevin Eveker
>Priority: Normal
>
> Recent scan results identified the following CVE that require this upgrade to
> address
> [https://nvd.nist.gov/vuln/detail/CVE-2019-10172]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15852) Handle errors in StreamSession#prepare
[
https://issues.apache.org/jira/browse/CASSANDRA-15852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179026#comment-17179026
]
Caleb Rackliffe commented on CASSANDRA-15852:
-
+1
> Handle errors in StreamSession#prepare
> --
>
> Key: CASSANDRA-15852
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15852
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Streaming
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 4.0-beta
>
>
> Since CASSANDRA-12229 we don't handle errors in {{StreamSession#prepare}} -
> this makes a stream initiator hang forever if an error is thrown.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15852) Handle errors in StreamSession#prepare
[
https://issues.apache.org/jira/browse/CASSANDRA-15852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-15852:
Status: Review In Progress (was: Changes Suggested)
> Handle errors in StreamSession#prepare
> --
>
> Key: CASSANDRA-15852
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15852
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Streaming
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 4.0-beta
>
>
> Since CASSANDRA-12229 we don't handle errors in {{StreamSession#prepare}} -
> this makes a stream initiator hang forever if an error is thrown.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update
[ https://issues.apache.org/jira/browse/CASSANDRA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Singh updated CASSANDRA-16046: Test and Documentation Plan: Ran locally in docker and tested edits. Looks good. Status: Patch Available (was: In Progress) > BLOG - Post about Cassandra & Kubernetes - SIG Update > - > > Key: CASSANDRA-16046 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16046 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Rahul Singh >Priority: Normal > Labels: pull-request-available > > We're getting a blog post out before/coinciding with Kubecon 2020. Content > code is mostly ready > > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update
[ https://issues.apache.org/jira/browse/CASSANDRA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Singh reassigned CASSANDRA-16046: --- Assignee: Mick Semb Wever (was: Rahul Singh) > BLOG - Post about Cassandra & Kubernetes - SIG Update > - > > Key: CASSANDRA-16046 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16046 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Mick Semb Wever >Priority: Normal > Labels: pull-request-available > > We're getting a blog post out before/coinciding with Kubecon 2020. Content > code is mostly ready > > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update
[ https://issues.apache.org/jira/browse/CASSANDRA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Singh reassigned CASSANDRA-16046: --- Assignee: Rahul Singh (was: Anthony Grasso) > BLOG - Post about Cassandra & Kubernetes - SIG Update > - > > Key: CASSANDRA-16046 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16046 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Rahul Singh >Priority: Normal > Labels: pull-request-available > > We're getting a blog post out before/coinciding with Kubecon 2020. Content > code is mostly ready > > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update
[ https://issues.apache.org/jira/browse/CASSANDRA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Singh updated CASSANDRA-16046: Authors: Rahul Singh (was: Anthony Grasso) > BLOG - Post about Cassandra & Kubernetes - SIG Update > - > > Key: CASSANDRA-16046 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16046 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Anthony Grasso >Priority: Normal > Labels: pull-request-available > > We're getting a blog post out before/coinciding with Kubecon 2020. Content > code is mostly ready > > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15828) Remove jackson-mapper-asl-1.9.13 to address CVE
[ https://issues.apache.org/jira/browse/CASSANDRA-15828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17178989#comment-17178989 ] Kevin Eveker commented on CASSANDRA-15828: -- [~mdenihan] we will upgrade to the latest version 3.11.7, can you confirm that org.codehaus.jackson:jackson-mapper-asl:1.9.2 has been removed from the distribution and will thus no longer show up in scans? > Remove jackson-mapper-asl-1.9.13 to address CVE > --- > > Key: CASSANDRA-15828 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15828 > Project: Cassandra > Issue Type: Improvement >Reporter: Kevin Eveker >Priority: Normal > > Recent scan results identified the following CVE that require this upgrade to > address > [https://nvd.nist.gov/vuln/detail/CVE-2019-10172] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update
[ https://issues.apache.org/jira/browse/CASSANDRA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17178987#comment-17178987 ] Michael Semb Wever commented on CASSANDRA-16046: If this is good to go, [~xingh] could you please… - remove the “merge” commit in your PR, - make sure the PR is updated and the correct/latest version, - squash your commit down to one - move the ticket to “patch submitted” > BLOG - Post about Cassandra & Kubernetes - SIG Update > - > > Key: CASSANDRA-16046 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16046 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Anthony Grasso >Priority: Normal > Labels: pull-request-available > > We're getting a blog post out before/coinciding with Kubecon 2020. Content > code is mostly ready > > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16052) CEP-7 Storage Attached Index for Apache Cassandra
[ https://issues.apache.org/jira/browse/CASSANDRA-16052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhaoYang updated CASSANDRA-16052: - Summary: CEP-7 Storage Attached Index for Apache Cassandra (was: Storage Attached Index for Apache Cassandra) > CEP-7 Storage Attached Index for Apache Cassandra > - > > Key: CASSANDRA-16052 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16052 > Project: Cassandra > Issue Type: Epic > Components: Feature/2i Index >Reporter: ZhaoYang >Priority: Normal > > [CEP|https://docs.google.com/document/d/1V830eAMmQAspjJdjviVZIaSolVGvZ1hVsqOLWyV0DS4/edit#heading=h.67ap6rr1mxr] > - A new index implementation, called Storage > Attached Index(SAI), based on the advancement made by SASI. > * disk usage by sharing of common data between multiple column indexes on > the same table and better compression of on-disk structures. > * numeric range query performance with modified KDTree and collection type > support. > * compaction performance and stability for larger data set. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-16052) Storage Attached Index for Apache Cassandra
ZhaoYang created CASSANDRA-16052: Summary: Storage Attached Index for Apache Cassandra Key: CASSANDRA-16052 URL: https://issues.apache.org/jira/browse/CASSANDRA-16052 Project: Cassandra Issue Type: Epic Components: Feature/2i Index Reporter: ZhaoYang [CEP|https://docs.google.com/document/d/1V830eAMmQAspjJdjviVZIaSolVGvZ1hVsqOLWyV0DS4/edit#heading=h.67ap6rr1mxr] - A new index implementation, called Storage Attached Index(SAI), based on the advancement made by SASI. * disk usage by sharing of common data between multiple column indexes on the same table and better compression of on-disk structures. * numeric range query performance with modified KDTree and collection type support. * compaction performance and stability for larger data set. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update
[ https://issues.apache.org/jira/browse/CASSANDRA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Singh reassigned CASSANDRA-16046: --- Assignee: Anthony Grasso (was: Rahul Singh) > BLOG - Post about Cassandra & Kubernetes - SIG Update > - > > Key: CASSANDRA-16046 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16046 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Anthony Grasso >Priority: Normal > Labels: pull-request-available > > We're getting a blog post out before/coinciding with Kubecon 2020. Content > code is mostly ready > > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16051) sstablemetadata line 44: : command not found
[
https://issues.apache.org/jira/browse/CASSANDRA-16051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17178926#comment-17178926
]
Robert Stupp commented on CASSANDRA-16051:
--
The chance is correct. The code went into {{cassandra.in.sh}}.
> sstablemetadata line 44: : command not found
>
>
> Key: CASSANDRA-16051
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16051
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/sstable
>Reporter: Arvinder Singh
>Priority: Normal
> Fix For: 4.0-beta2
>
>
> sstablemetadata shipped with
> [4.0-beta|https://issues.apache.org/jira/issues/?jql=project+%3D+CASSANDRA+AND+fixVersion+%3D+4.0-beta]
> is missing the code "#Use JAVA_HOME if set, otherwise look for java in PATH"
> and report error:
> sstablemetadata: line 44: : command not found
>
> The fix is to merge below code from 3.x:
> ^# Use JAVA_HOME if set, otherwise look for java in PATH^
> ^if [ -x "$JAVA_HOME/bin/java" ]; then^
> ^JAVA="$JAVA_HOME/bin/java"^
> ^else^
> ^JAVA="`which java`"^
> ^fi^
> ^if [ "x$JAVA" = "x" ]; then^
> ^echo "Java executable not found (hint: set JAVA_HOME)" >&2^
> ^exit 1^
> ^fi^
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15852) Handle errors in StreamSession#prepare
[
https://issues.apache.org/jira/browse/CASSANDRA-15852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17178913#comment-17178913
]
Marcus Eriksson edited comment on CASSANDRA-15852 at 8/17/20, 11:42 AM:
pushed an update
Can't change the exception type since this is thrown on replica side and we
don't re-throw the same exception on the stream coordinator, we only know that
it failed, not why. Added a boolean in the bytebuddy redefine to make sure we
have thrown the correct exception on the replica.
was (Author: krummas):
pushed an update
Can't change the exception type since this is thrown on replica side and we
don't re-throw the same exception on the stream coordinator, we only know that
it failed, now why. Added a boolean in the bytebuddy redefine to make sure we
have thrown the correct exception on the replica.
> Handle errors in StreamSession#prepare
> --
>
> Key: CASSANDRA-15852
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15852
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Streaming
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 4.0-beta
>
>
> Since CASSANDRA-12229 we don't handle errors in {{StreamSession#prepare}} -
> this makes a stream initiator hang forever if an error is thrown.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15852) Handle errors in StreamSession#prepare
[
https://issues.apache.org/jira/browse/CASSANDRA-15852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17178913#comment-17178913
]
Marcus Eriksson commented on CASSANDRA-15852:
-
pushed an update
Can't change the exception type since this is thrown on replica side and we
don't re-throw the same exception on the stream coordinator, we only know that
it failed, now why. Added a boolean in the bytebuddy redefine to make sure we
have thrown the correct exception on the replica.
> Handle errors in StreamSession#prepare
> --
>
> Key: CASSANDRA-15852
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15852
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Streaming
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 4.0-beta
>
>
> Since CASSANDRA-12229 we don't handle errors in {{StreamSession#prepare}} -
> this makes a stream initiator hang forever if an error is thrown.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-13994) Remove dead compact storage code before 4.0 release
[
https://issues.apache.org/jira/browse/CASSANDRA-13994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-13994:
-
Fix Version/s: (was: 4.0-beta)
(was: 4.0)
4.0-beta2
Impacts: None
Platform: All
Source Control Link:
https://github.com/apache/cassandra/commit/cba0c27ce9f135ded45beaa27a913a0be03b2afb
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Great work [~e.dimitrova], thanks. Committed.
> Remove dead compact storage code before 4.0 release
> ---
>
> Key: CASSANDRA-13994
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13994
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Local Write-Read Paths
>Reporter: Alex Petrov
>Assignee: Ekaterina Dimitrova
>Priority: Low
> Fix For: 4.0-beta2
>
>
> 4.0 comes without thrift (after [CASSANDRA-5]) and COMPACT STORAGE (after
> [CASSANDRA-10857]), and since Compact Storage flags are now disabled, all of
> the related functionality is useless.
> There are still some things to consider:
> 1. One of the system tables (built indexes) was compact. For now, we just
> added {{value}} column to it to make sure it's backwards-compatible, but we
> might want to make sure it's just a "normal" table and doesn't have redundant
> columns.
> 2. Compact Tables were building indexes in {{KEYS}} mode. Removing it is
> trivial, but this would mean that all built indexes will be defunct. We could
> log a warning for now and ask users to migrate off those for now and
> completely remove it from future releases. It's just a couple of classes
> though.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-13994) Remove dead compact storage code before 4.0 release
[
https://issues.apache.org/jira/browse/CASSANDRA-13994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-13994:
-
Status: Ready to Commit (was: Review In Progress)
> Remove dead compact storage code before 4.0 release
> ---
>
> Key: CASSANDRA-13994
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13994
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Local Write-Read Paths
>Reporter: Alex Petrov
>Assignee: Ekaterina Dimitrova
>Priority: Low
> Fix For: 4.0, 4.0-beta
>
>
> 4.0 comes without thrift (after [CASSANDRA-5]) and COMPACT STORAGE (after
> [CASSANDRA-10857]), and since Compact Storage flags are now disabled, all of
> the related functionality is useless.
> There are still some things to consider:
> 1. One of the system tables (built indexes) was compact. For now, we just
> added {{value}} column to it to make sure it's backwards-compatible, but we
> might want to make sure it's just a "normal" table and doesn't have redundant
> columns.
> 2. Compact Tables were building indexes in {{KEYS}} mode. Removing it is
> trivial, but this would mean that all built indexes will be defunct. We could
> log a warning for now and ask users to migrate off those for now and
> completely remove it from future releases. It's just a couple of classes
> though.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15432) The "read defragmentation" optimization does not work
[
https://issues.apache.org/jira/browse/CASSANDRA-15432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-15432:
-
Fix Version/s: (was: 3.11.x)
(was: 4.x)
(was: 3.0.x)
4.0-beta2
3.11.8
3.0.22
Since Version: 1.1.0
Source Control Link:
3.0:https://github.com/apache/cassandra/commit/e2ecdf268a82fa3ac0f4c9fe77ab35bca33cc72a,
3.11:https://github.com/apache/cassandra/commit/ecd23f1da5894511cccac6c8445f962f3b73f733,
trunk:https://github.com/apache/cassandra/commit/efce6b39fb557314fad0cb56b0
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Thanks for the review. CI doesn't seem to show anything new broken so committed.
> The "read defragmentation" optimization does not work
> -
>
> Key: CASSANDRA-15432
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15432
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
>Reporter: Sylvain Lebresne
>Assignee: Sylvain Lebresne
>Priority: Normal
> Fix For: 3.0.22, 3.11.8, 4.0-beta2
>
>
> The so-called "read defragmentation" that has been added way back with
> CASSANDRA-2503 actually does not work, and never has. That is, the
> defragmentation writes do happen, but they only additional load on the nodes
> without helping anything, and are thus a clear negative.
> The "read defragmentation" (which only impact so-called "names queries")
> kicks in when a read hits "too many" sstables (> 4 by default), and when it
> does, it writes down the result of that read. The assumption being that the
> next read for that data would only read the newly written data, which if not
> still in memtable would at least be in a single sstable, thus speeding that
> next read.
> Unfortunately, this is not how this work. When we defrag and write the result
> of our original read, we do so with the timestamp of the data read (as we
> should, changing the timestamp would be plain wrong). And as a result,
> following reads will read that data first, but will have no way to tell that
> no more sstables should be read. Technically, the
> [{{reduceFilter}}|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/SinglePartitionReadCommand.java#L830]
> call will not return {{null}} because the {{currentMaxTs}} will be higher
> than at least some of the data in the result, and this until we've read from
> as many sstables than in the original read.
> I see no easy way to fix this. It might be possible to make it work with
> additional per-sstable metadata, but nothing sufficiently simple and cheap to
> be worth it comes to mind. And I thus suggest simply removing that code.
> For the record, I'll note that there is actually a 2nd problem with that
> code: currently, we "defrag" a read even if we didn't got data for everything
> that the query requests. This also is "wrong" even if we ignore the first
> issue: a following read that would read the defragmented data would also have
> no way to know to not read more sstables to try to get the missing parts.
> This problem would be fixeable, but is obviously overshadowed by the previous
> one anyway.
> Anyway, as mentioned, I suggest to just remove the "optimization" (which
> again, never optimized anything) altogether, and happy to provide the simple
> patch.
> The only question might be in which versions? This impact all versions, but
> this isn't a correction bug either, "just" a performance one. So do we want
> 4.0 only or is there appetite for earlier?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-3.11' into trunk
This is an automated email from the ASF dual-hosted git repository. slebresne pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit efce6b39fb557314fad0cb56b07a1919d26b84fc Merge: 139ad44 ecd23f1 Author: Sylvain Lebresne AuthorDate: Mon Aug 17 11:39:24 2020 +0200 Merge branch 'cassandra-3.11' into trunk CHANGES.txt| 1 + .../cassandra/db/SinglePartitionReadCommand.java | 25 -- .../db/compaction/AbstractCompactionStrategy.java | 5 - .../db/compaction/CompactionStrategyManager.java | 7 -- .../compaction/SizeTieredCompactionStrategy.java | 6 -- 5 files changed, 1 insertion(+), 43 deletions(-) diff --cc CHANGES.txt index 58239c9,a6bc9d9..7298e0c --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,20 -1,14 +1,21 @@@ -3.11.8 +4.0-beta2 + * Make TimestampSerializer accept fractional seconds of varying precision (CASSANDRA-15976) + * Improve cassandra-stress logging when using a profile file that doesn't exist (CASSANDRA-14425) + * Improve logging for socket connection/disconnection (CASSANDRA-15980) + * Throw FSWriteError upon write failures in order to apply DiskFailurePolicy (CASSANDRA-15928) + * Forbid altering UDTs used in partition keys (CASSANDRA-15933) + * Fix version parsing logic when upgrading from 3.0 (CASSANDRA-15973) + * Optimize NoSpamLogger use in hot paths (CASSANDRA-15766) + * Verify sstable components on startup (CASSANDRA-15945) +Merged from 3.11: * Fix short read protection for GROUP BY queries (CASSANDRA-15459) + * stop_paranoid disk failure policy is ignored on CorruptSSTableException after node is up (CASSANDRA-15191) * Frozen RawTuple is not annotated with frozen in the toString method (CASSANDRA-15857) Merged from 3.0: + * Remove broken 'defrag-on-read' optimization (CASSANDRA-15432) * Check for endpoint collision with hibernating nodes (CASSANDRA-14599) * Operational improvements and hardening for replica filtering protection (CASSANDRA-15907) - * stop_paranoid disk failure policy is ignored on CorruptSSTableException after node is up (CASSANDRA-15191) - * Forbid altering UDTs used in partition keys (CASSANDRA-15933) * Fix empty/null json string representation (CASSANDRA-15896) - * 3.x fails to start if commit log has range tombstones from a column which is also deleted (CASSANDRA-15970) Merged from 2.2: * Fix CQL parsing of collections when the column type is reversed (CASSANDRA-15814) diff --cc src/java/org/apache/cassandra/db/SinglePartitionReadCommand.java index 6fbe523,c5de444..e581be5 --- a/src/java/org/apache/cassandra/db/SinglePartitionReadCommand.java +++ b/src/java/org/apache/cassandra/db/SinglePartitionReadCommand.java @@@ -28,10 -28,15 +28,9 @@@ import com.google.common.collect.Sets import org.apache.cassandra.cache.IRowCacheEntry; import org.apache.cassandra.cache.RowCacheKey; import org.apache.cassandra.cache.RowCacheSentinel; --import org.apache.cassandra.concurrent.Stage; -import org.apache.cassandra.concurrent.StageManager; -import org.apache.cassandra.config.CFMetaData; -import org.apache.cassandra.config.ColumnDefinition; import org.apache.cassandra.config.DatabaseDescriptor; -import org.apache.cassandra.db.lifecycle.*; import org.apache.cassandra.db.filter.*; +import org.apache.cassandra.db.lifecycle.*; import org.apache.cassandra.db.partitions.*; import org.apache.cassandra.db.rows.*; import org.apache.cassandra.db.transform.RTBoundValidator; @@@ -889,11 -992,8 +887,8 @@@ public class SinglePartitionReadComman if (iter.isEmpty()) continue; - if (sstable.isRepaired()) - onlyUnrepaired = false; - result = add( -RTBoundValidator.validate(isForThrift() ? ThriftResultsMerger.maybeWrap(iter, nowInSec()) : iter, RTBoundValidator.Stage.SSTABLE, false), +RTBoundValidator.validate(iter, RTBoundValidator.Stage.SSTABLE, false), result, filter, sstable.isRepaired() @@@ -907,29 -1007,9 +902,9 @@@ return EmptyIterators.unfilteredRow(metadata(), partitionKey(), false); DecoratedKey key = result.partitionKey(); - cfs.metric.samplers.get(TableMetrics.Sampler.READS).addSample(key.getKey(), key.hashCode(), 1); -StorageHook.instance.reportRead(cfs.metadata.cfId, partitionKey()); +cfs.metric.topReadPartitionFrequency.addSample(key.getKey(), 1); +StorageHook.instance.reportRead(cfs.metadata.id, partitionKey()); - // "hoist up" the requested data into a more recent sstable - if (metricsCollector.getMergedSSTables() > cfs.getMinimumCompactionThreshold() - && onlyUnrepaired - && !cfs.isAutoCompactionDisabled() - &&
[cassandra] branch trunk updated (139ad44 -> efce6b3)
This is an automated email from the ASF dual-hosted git repository. slebresne pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git. from 139ad44 Update docs regarding timestamp precision new e2ecdf2 Remove broken "defragment-on-read" optimization new ecd23f1 Merge commit 'e2ecdf268a82fa3ac0f4c9fe77ab35bca33cc72a' into cassandra-3.11 new efce6b3 Merge branch 'cassandra-3.11' into trunk The 3 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: CHANGES.txt| 1 + .../cassandra/db/SinglePartitionReadCommand.java | 25 -- .../db/compaction/AbstractCompactionStrategy.java | 5 - .../db/compaction/CompactionStrategyManager.java | 7 -- .../compaction/SizeTieredCompactionStrategy.java | 6 -- 5 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-3.11 updated (2beebbb -> ecd23f1)
This is an automated email from the ASF dual-hosted git repository. slebresne pushed a change to branch cassandra-3.11 in repository https://gitbox.apache.org/repos/asf/cassandra.git. from 2beebbb Merge branch 'cassandra-3.0' into cassandra-3.11 new e2ecdf2 Remove broken "defragment-on-read" optimization new ecd23f1 Merge commit 'e2ecdf268a82fa3ac0f4c9fe77ab35bca33cc72a' 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: CHANGES.txt| 1 + .../cassandra/db/SinglePartitionReadCommand.java | 24 -- .../db/compaction/AbstractCompactionStrategy.java | 5 - .../db/compaction/CompactionStrategyManager.java | 7 --- .../compaction/SizeTieredCompactionStrategy.java | 6 -- 5 files changed, 1 insertion(+), 42 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15802) Commented-out lines that end in a semicolon cause an error.
[ https://issues.apache.org/jira/browse/CASSANDRA-15802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17178871#comment-17178871 ] Michael Semb Wever commented on CASSANDRA-15802: A number of the dtests are broken from this patch. See [here|https://ci-cassandra.apache.org/job/Cassandra-devbranch/244/testReport/] compared to [trunk|https://ci-cassandra.apache.org/job/Cassandra-trunk/lastCompletedBuild/testReport/]. One example is [cqlsh_tests.test_cqlsh.TestCqlsh.test_describe|https://ci-cassandra.apache.org/job/Cassandra-devbranch/244/testReport/dtest.cqlsh_tests.test_cqlsh/TestCqlsh/test_describe/] > Commented-out lines that end in a semicolon cause an error. > --- > > Key: CASSANDRA-15802 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15802 > Project: Cassandra > Issue Type: Bug > Components: CQL/Interpreter, CQL/Syntax >Reporter: null >Assignee: Rens Groothuijsen >Priority: Normal > Attachments: cqlsh.png > > Time Spent: 40m > Remaining Estimate: 0h > > Commented-out lines that end in a semicolon cause an error. > For example: > /* > describe keyspaces; > */ > > This produces an error: > SyntaxException: line 2:22 no viable alternative at input ' (...* > describe keyspaces;...) > > It works as expected if you use syntax: > -- describe keyspaces; > > Environment: > python:3.7.7-slim-stretch (docker image) > > I found that this was first seen here, and was patched, but the bug appears > to have resurfaced: > https://issues.apache.org/jira/browse/CASSANDRA-2488 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge commit 'e2ecdf268a82fa3ac0f4c9fe77ab35bca33cc72a' into cassandra-3.11
This is an automated email from the ASF dual-hosted git repository.
slebresne pushed a commit to branch cassandra-3.11
in repository https://gitbox.apache.org/repos/asf/cassandra.git
commit ecd23f1da5894511cccac6c8445f962f3b73f733
Merge: 2beebbb e2ecdf2
Author: Sylvain Lebresne
AuthorDate: Mon Aug 17 11:32:46 2020 +0200
Merge commit 'e2ecdf268a82fa3ac0f4c9fe77ab35bca33cc72a' into cassandra-3.11
CHANGES.txt| 1 +
.../cassandra/db/SinglePartitionReadCommand.java | 24 --
.../db/compaction/AbstractCompactionStrategy.java | 5 -
.../db/compaction/CompactionStrategyManager.java | 7 ---
.../compaction/SizeTieredCompactionStrategy.java | 6 --
5 files changed, 1 insertion(+), 42 deletions(-)
diff --cc CHANGES.txt
index 5168acb,9b4f8c3..a6bc9d9
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,7 -1,5 +1,8 @@@
-3.0.22:
+3.11.8
+ * Fix short read protection for GROUP BY queries (CASSANDRA-15459)
+ * Frozen RawTuple is not annotated with frozen in the toString method
(CASSANDRA-15857)
+Merged from 3.0:
+ * Remove broken 'defrag-on-read' optimization (CASSANDRA-15432)
* Check for endpoint collision with hibernating nodes (CASSANDRA-14599)
* Operational improvements and hardening for replica filtering protection
(CASSANDRA-15907)
* stop_paranoid disk failure policy is ignored on CorruptSSTableException
after node is up (CASSANDRA-15191)
diff --cc src/java/org/apache/cassandra/db/SinglePartitionReadCommand.java
index a820a89,ca4e8e3..c5de444
--- a/src/java/org/apache/cassandra/db/SinglePartitionReadCommand.java
+++ b/src/java/org/apache/cassandra/db/SinglePartitionReadCommand.java
@@@ -918,8 -882,7 +918,7 @@@ public class SinglePartitionReadComman
}
/* add the SSTables on disk */
-Collections.sort(view.sstables, SSTableReader.maxTimestampComparator);
+Collections.sort(view.sstables, SSTableReader.maxTimestampDescending);
- boolean onlyUnrepaired = true;
// read sorted sstables
SSTableReadMetricsCollector metricsCollector = new
SSTableReadMetricsCollector();
for (SSTableReader sstable : view.sstables)
@@@ -1012,28 -967,7 +1008,8 @@@
DecoratedKey key = result.partitionKey();
cfs.metric.samplers.get(TableMetrics.Sampler.READS).addSample(key.getKey(),
key.hashCode(), 1);
+StorageHook.instance.reportRead(cfs.metadata.cfId, partitionKey());
- // "hoist up" the requested data into a more recent sstable
- if (metricsCollector.getMergedSSTables() >
cfs.getMinimumCompactionThreshold()
- && onlyUnrepaired
- && !cfs.isAutoCompactionDisabled()
- && cfs.getCompactionStrategyManager().shouldDefragment())
- {
- // !!WARNING!! if we stop copying our data to a heap-managed
object,
- // we will need to track the lifetime of this
mutation as well
- Tracing.trace("Defragmenting requested data");
-
- try (UnfilteredRowIterator iter =
result.unfilteredIterator(columnFilter(), Slices.ALL, false))
- {
- final Mutation mutation = new
Mutation(PartitionUpdate.fromIterator(iter, columnFilter()));
- StageManager.getStage(Stage.MUTATION).execute(() -> {
- // skipping commitlog and index updates is fine since
we're just de-fragmenting existing data
- Keyspace.open(mutation.getKeyspaceName()).apply(mutation,
false, false);
- });
- }
- }
-
return result.unfilteredIterator(columnFilter(), Slices.ALL,
clusteringIndexFilter().isReversed());
}
diff --cc
src/java/org/apache/cassandra/db/compaction/CompactionStrategyManager.java
index 86170a1,5d4a254..d486679
--- a/src/java/org/apache/cassandra/db/compaction/CompactionStrategyManager.java
+++ b/src/java/org/apache/cassandra/db/compaction/CompactionStrategyManager.java
@@@ -102,11 -64,8 +102,10 @@@ public class CompactionStrategyManager
If a user changes the local compaction strategy and then later ALTERs
a compaction parameter,
we will use the new compaction parameters.
- */
-private CompactionParams schemaCompactionParams;
+ **/
+private volatile CompactionParams schemaCompactionParams;
- private boolean shouldDefragment;
+private boolean supportsEarlyOpen;
+private int fanout;
public CompactionStrategyManager(ColumnFamilyStore cfs)
{
@@@ -206,28 -129,13 +205,27 @@@
private void startup()
{
-for (SSTableReader sstable : cfs.getSSTables(SSTableSet.CANONICAL))
+writeLock.lock();
+try
{
-if (sstable.openReason != SSTableReader.OpenReason.EARLY)
-getCompactionStrategyFor(sstable).addSSTable(sstable);
+for (SSTableReader sstable :
[cassandra] branch cassandra-3.0 updated: Remove broken "defragment-on-read" optimization
This is an automated email from the ASF dual-hosted git repository.
slebresne 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 e2ecdf2 Remove broken "defragment-on-read" optimization
e2ecdf2 is described below
commit e2ecdf268a82fa3ac0f4c9fe77ab35bca33cc72a
Author: Sylvain Lebresne
AuthorDate: Wed Aug 12 16:29:43 2020 +0200
Remove broken "defragment-on-read" optimization
The read path for names queries has had a "defragment-on-read"
optimization for a while whereby if too many sstables are hit by the
read, the result is written back into memtable, in the hope that later
reads will only read that newly written data in a single sstable (or at
least fewer).
The principle of that optimisation does not work however as data is
written back with the same timestamp as it originally has and that means
future reads cannot know to skip older sstables (at least with the
metadata we currently store).
As such, this optimisation never saved anything and in fact added load.
The patch removes that broken code.
Patch by Sylvain Lebresne, reviewed by Aleksey Yeschenko for
CASSANDRA-15432
---
CHANGES.txt| 1 +
.../cassandra/db/SinglePartitionReadCommand.java | 28 --
.../db/compaction/AbstractCompactionStrategy.java | 5
.../db/compaction/CompactionStrategyManager.java | 6 -
.../compaction/SizeTieredCompactionStrategy.java | 6 -
5 files changed, 1 insertion(+), 45 deletions(-)
diff --git a/CHANGES.txt b/CHANGES.txt
index 7d4b7a9..9b4f8c3 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
3.0.22:
+ * Remove broken 'defrag-on-read' optimization (CASSANDRA-15432)
* Check for endpoint collision with hibernating nodes (CASSANDRA-14599)
* Operational improvements and hardening for replica filtering protection
(CASSANDRA-15907)
* stop_paranoid disk failure policy is ignored on CorruptSSTableException
after node is up (CASSANDRA-15191)
diff --git a/src/java/org/apache/cassandra/db/SinglePartitionReadCommand.java
b/src/java/org/apache/cassandra/db/SinglePartitionReadCommand.java
index 841c3b9..ca4e8e3 100644
--- a/src/java/org/apache/cassandra/db/SinglePartitionReadCommand.java
+++ b/src/java/org/apache/cassandra/db/SinglePartitionReadCommand.java
@@ -883,7 +883,6 @@ public class SinglePartitionReadCommand extends ReadCommand
/* add the SSTables on disk */
Collections.sort(view.sstables, SSTableReader.maxTimestampComparator);
-boolean onlyUnrepaired = true;
// read sorted sstables
SSTableReadMetricsCollector metricsCollector = new
SSTableReadMetricsCollector();
for (SSTableReader sstable : view.sstables)
@@ -952,9 +951,6 @@ public class SinglePartitionReadCommand extends ReadCommand
if (iter.isEmpty())
continue;
-if (sstable.isRepaired())
-onlyUnrepaired = false;
-
result = add(
RTBoundValidator.validate(isForThrift() ?
ThriftResultsMerger.maybeWrap(iter, nowInSec()) : iter,
RTBoundValidator.Stage.SSTABLE, false),
result,
@@ -972,30 +968,6 @@ public class SinglePartitionReadCommand extends ReadCommand
DecoratedKey key = result.partitionKey();
cfs.metric.samplers.get(TableMetrics.Sampler.READS).addSample(key.getKey(),
key.hashCode(), 1);
-// "hoist up" the requested data into a more recent sstable
-if (metricsCollector.getMergedSSTables() >
cfs.getMinimumCompactionThreshold()
-&& onlyUnrepaired
-&& !cfs.isAutoCompactionDisabled()
-&& cfs.getCompactionStrategyManager().shouldDefragment())
-{
-// !!WARNING!! if we stop copying our data to a heap-managed
object,
-// we will need to track the lifetime of this
mutation as well
-Tracing.trace("Defragmenting requested data");
-
-try (UnfilteredRowIterator iter =
result.unfilteredIterator(columnFilter(), Slices.ALL, false))
-{
-final Mutation mutation = new
Mutation(PartitionUpdate.fromIterator(iter));
-StageManager.getStage(Stage.MUTATION).execute(new Runnable()
-{
-public void run()
-{
-// skipping commitlog and index updates is fine since
we're just de-fragmenting existing data
-
Keyspace.open(mutation.getKeyspaceName()).apply(mutation, false, false);
-}
-});
-}
-}
-
return result.unfilteredIterator(columnFilter(), Slices.ALL,
clusteringIndexFilter().isReversed());
}
diff --git
[jira] [Commented] (CASSANDRA-15828) Remove jackson-mapper-asl-1.9.13 to address CVE
[ https://issues.apache.org/jira/browse/CASSANDRA-15828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17178864#comment-17178864 ] Mark Denihan commented on CASSANDRA-15828: -- [~c3-keveker] I was wondering if this could be classified as a false positive but it does look like the org.codehaus.jackson:jackson-mapper-asl:1.9.2 dependency is utilized in a number of functions in the following versions; 2.2.17 src\java\org\apache\cassandra\cql3\Json.java src\java\org\apache\cassandra\tools\SSTableExport.java src\java\org\apache\cassandra\tools\SSTableImport.java src\java\org\apache\cassandra\utils\FBUtilities.java 3.0.21 src\java\org\apache\cassandra\cql3\Json.java src\java\org\apache\cassandra\utils\FBUtilities.java 3.11.6 src\java\org\apache\cassandra\cql3\Json.java src\java\org\apache\cassandra\utils\FBUtilities.java 3.11.7 No use of org.codehaus.jackson:jackson-mapper-asl Considering CVE-2019-10172 has poor information as to what classes are vulnerable in org.codehaus.jackson:jackson-mapper-asl we must assume that if the version of Cassandra uses the library, it is vulnerable. So as far as I can see has been fixed in the latest version of 3.11.7. Is there any way that fix will be back ported to other versions? > Remove jackson-mapper-asl-1.9.13 to address CVE > --- > > Key: CASSANDRA-15828 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15828 > Project: Cassandra > Issue Type: Improvement >Reporter: Kevin Eveker >Priority: Normal > > Recent scan results identified the following CVE that require this upgrade to > address > [https://nvd.nist.gov/vuln/detail/CVE-2019-10172] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16050) Handle difference in timestamp precision between java8 and java11 in LogFIle.java
[ https://issues.apache.org/jira/browse/CASSANDRA-16050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-16050: Test and Documentation Plan: new test, cci runs Status: Patch Available (was: Open) | [3.0|https://github.com/krummas/cassandra/commits/marcuse/16050] | [unit tests|https://app.circleci.com/pipelines/github/krummas/cassandra/475/workflows/acc3b0a3-71b9-4816-9b10-0906d9d8c364/jobs/3514] | [jvm dtests|https://app.circleci.com/pipelines/github/krummas/cassandra/475/workflows/acc3b0a3-71b9-4816-9b10-0906d9d8c364/jobs/3515] | [novnodes|https://app.circleci.com/pipelines/github/krummas/cassandra/475/workflows/acc3b0a3-71b9-4816-9b10-0906d9d8c364/jobs/3520] | [vnodes|https://app.circleci.com/pipelines/github/krummas/cassandra/475/workflows/acc3b0a3-71b9-4816-9b10-0906d9d8c364/jobs/3521] | | [3.11|https://github.com/krummas/cassandra/commits/marcuse/16050-3.11] | [unit tests|https://app.circleci.com/pipelines/github/krummas/cassandra/473/workflows/a2ff42d2-6a01-410f-9b45-78ad51615e2f/jobs/3503] | [jvm dtests|https://app.circleci.com/pipelines/github/krummas/cassandra/473/workflows/a2ff42d2-6a01-410f-9b45-78ad51615e2f/jobs/3502] | [novodes |https://app.circleci.com/pipelines/github/krummas/cassandra/473/workflows/a2ff42d2-6a01-410f-9b45-78ad51615e2f/jobs/3516] | [vnodes|https://app.circleci.com/pipelines/github/krummas/cassandra/473/workflows/a2ff42d2-6a01-410f-9b45-78ad51615e2f/jobs/3517] | [trunk|https://github.com/krummas/cassandra/commits/marcuse/16050-trunk] | [unit tests|https://app.circleci.com/pipelines/github/krummas/cassandra/476/workflows/d1da56f3-ddde-48fb-b133-0a2a61133b63/jobs/3510] | [jvm dtests|https://app.circleci.com/pipelines/github/krummas/cassandra/476/workflows/d1da56f3-ddde-48fb-b133-0a2a61133b63/jobs/3509] | [novnodes|https://app.circleci.com/pipelines/github/krummas/cassandra/476/workflows/d1da56f3-ddde-48fb-b133-0a2a61133b63/jobs/3519] | [vnodes|https://app.circleci.com/pipelines/github/krummas/cassandra/476/workflows/d1da56f3-ddde-48fb-b133-0a2a61133b63/jobs/3518] | > Handle difference in timestamp precision between java8 and java11 in > LogFIle.java > - > > Key: CASSANDRA-16050 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16050 > Project: Cassandra > Issue Type: Bug > Components: Local/SSTable, Local/Startup and Shutdown >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 4.0, 3.0.x, 3.11.x > > > https://bugs.openjdk.java.net/browse/JDK-8177809 made File.lastModified > include milliseconds while java8 always has them as 000. > This causes problems in LogFile.java where we compare the timestamps with > what we have in the logfile: > [LogFile.java|https://github.com/apache/cassandra/blob/ffc8e407e087e942c4e5c40605743fe3b32d8fd5/src/java/org/apache/cassandra/db/lifecycle/LogFile.java#L234]. > This means that we can throw errors when changing between java11 and 8 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16044) Query SSTable Indexes lazily in token sorted runs for LCS, TWCS or RangeAwaredCompaction
[ https://issues.apache.org/jira/browse/CASSANDRA-16044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-16044: Change Category: Performance Complexity: Normal Status: Open (was: Triage Needed) > Query SSTable Indexes lazily in token sorted runs for LCS, TWCS or > RangeAwaredCompaction > > > Key: CASSANDRA-16044 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16044 > Project: Cassandra > Issue Type: Improvement > Components: Feature/SASI >Reporter: ZhaoYang >Priority: Normal > Fix For: 4.x > > > Currently SASI searches all SSTable indexes that may include the query > partition key and indexed term, but this will cause large IO overhead with > range index query (ie. age > 18) when sstable count is huge. > Proposed improvement: query sstable indexes in token-sorted-runs lazily. When > the data in the first few token ranges is sufficient for limit, SASI can > reduce the overhead of searching sstable indexes for the remaining ranges. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
