[jira] [Updated] (CASSANDRA-19467) Deprecate Python 3.7 and earlier, but allow cqlsh to run with Python 3.6+
[
https://issues.apache.org/jira/browse/CASSANDRA-19467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-19467:
Attachment: ci_summary.html
> Deprecate Python 3.7 and earlier, but allow cqlsh to run with Python 3.6+
> -
>
> Key: CASSANDRA-19467
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19467
> Project: Cassandra
> Issue Type: Task
> Components: Tool/cqlsh
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 5.0-rc, 5.1
>
> Attachments: ci_summary.html
>
>
> In 4.0, we introduced Python 3.6 support. In CASSANDRA-19245, for the 5.0
> release, we dropped Python 3.6 and 3.7 support since Python 3.8 was the
> minimum supported version for version 3.29.0 of the Python driver, which we
> needed to support vectors. Unfortunately, that may break existing users of
> RHEL 7, which natively only supports Python 3.6.
> We should deprecate Python 3.6-3.7 (which are all either EOL or will be soon)
> and mention this in NEWS.txt/appropriate warnings at {{cqlsh}} startup, but
> we don't need to have cqlsh refuse to start entirely with 3.6-3.7 until our
> 6.0 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19467) Deprecate Python 3.7 and earlier, but allow cqlsh to run with Python 3.6+
[
https://issues.apache.org/jira/browse/CASSANDRA-19467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-19467:
-
Reviewers: Brandon Williams
Status: Review In Progress (was: Patch Available)
> Deprecate Python 3.7 and earlier, but allow cqlsh to run with Python 3.6+
> -
>
> Key: CASSANDRA-19467
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19467
> Project: Cassandra
> Issue Type: Task
> Components: Tool/cqlsh
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 5.0-rc, 5.1
>
>
> In 4.0, we introduced Python 3.6 support. In CASSANDRA-19245, for the 5.0
> release, we dropped Python 3.6 and 3.7 support since Python 3.8 was the
> minimum supported version for version 3.29.0 of the Python driver, which we
> needed to support vectors. Unfortunately, that may break existing users of
> RHEL 7, which natively only supports Python 3.6.
> We should deprecate Python 3.6-3.7 (which are all either EOL or will be soon)
> and mention this in NEWS.txt/appropriate warnings at {{cqlsh}} startup, but
> we don't need to have cqlsh refuse to start entirely with 3.6-3.7 until our
> 6.0 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19467) Deprecate Python 3.7 and earlier, but allow cqlsh to run with Python 3.6+
[
https://issues.apache.org/jira/browse/CASSANDRA-19467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-19467:
-
Status: Ready to Commit (was: Review In Progress)
> Deprecate Python 3.7 and earlier, but allow cqlsh to run with Python 3.6+
> -
>
> Key: CASSANDRA-19467
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19467
> Project: Cassandra
> Issue Type: Task
> Components: Tool/cqlsh
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 5.0-rc, 5.1
>
>
> In 4.0, we introduced Python 3.6 support. In CASSANDRA-19245, for the 5.0
> release, we dropped Python 3.6 and 3.7 support since Python 3.8 was the
> minimum supported version for version 3.29.0 of the Python driver, which we
> needed to support vectors. Unfortunately, that may break existing users of
> RHEL 7, which natively only supports Python 3.6.
> We should deprecate Python 3.6-3.7 (which are all either EOL or will be soon)
> and mention this in NEWS.txt/appropriate warnings at {{cqlsh}} startup, but
> we don't need to have cqlsh refuse to start entirely with 3.6-3.7 until our
> 6.0 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19467) Deprecate Python 3.7 and earlier, but allow cqlsh to run with Python 3.6+
[
https://issues.apache.org/jira/browse/CASSANDRA-19467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827634#comment-17827634
]
Brandon Williams commented on CASSANDRA-19467:
--
The updated run
[here|https://app.circleci.com/pipelines/github/driftx/cassandra/1528/workflows/89fb0401-a32d-4edf-b2f0-75307f769b3a/jobs/78374]
has only one failure which is CASSANDRA-19471
> Deprecate Python 3.7 and earlier, but allow cqlsh to run with Python 3.6+
> -
>
> Key: CASSANDRA-19467
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19467
> Project: Cassandra
> Issue Type: Task
> Components: Tool/cqlsh
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 5.0-rc, 5.1
>
>
> In 4.0, we introduced Python 3.6 support. In CASSANDRA-19245, for the 5.0
> release, we dropped Python 3.6 and 3.7 support since Python 3.8 was the
> minimum supported version for version 3.29.0 of the Python driver, which we
> needed to support vectors. Unfortunately, that may break existing users of
> RHEL 7, which natively only supports Python 3.6.
> We should deprecate Python 3.6-3.7 (which are all either EOL or will be soon)
> and mention this in NEWS.txt/appropriate warnings at {{cqlsh}} startup, but
> we don't need to have cqlsh refuse to start entirely with 3.6-3.7 until our
> 6.0 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19467) Deprecate Python 3.7 and earlier, but allow cqlsh to run with Python 3.6+
[
https://issues.apache.org/jira/browse/CASSANDRA-19467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-19467:
Description:
In 4.0, we introduced Python 3.6 support. In CASSANDRA-19245, for the 5.0
release, we dropped Python 3.6 and 3.7 support since Python 3.8 was the minimum
supported version for version 3.29.0 of the Python driver, which we needed to
support vectors. Unfortunately, that may break existing users of RHEL 7, which
natively only supports Python 3.6.
We should deprecate Python 3.6-3.7 (which are all either EOL or will be soon)
and mention this in NEWS.txt/appropriate warnings at {{cqlsh}} startup, but we
don't need to have cqlsh refuse to start entirely with 3.6-3.7 until our 6.0
release.
was:
In 4.0, we introduced Python 3.6 support. In CASSANDRA-19245, for the 5.0
release, we dropped Python 3.6 and 3.7 support since Python 3.8 was the minimum
supported version for version 3.29.0 of the Python driver, which we needed to
support vectors. Unfortunately, that may break existing users of RHEL 7, which
natively only supports Python 3.6.
We should deprecate Python 3.6-3.8 (which are all either EOL or will be soon)
and mention this in NEWS.txt/appropriate warnings at {{cqlsh}} startup, but we
don't need to have cqlsh refuse to start entirely with 3.6-3.8 until our 6.0
release.
> Deprecate Python 3.7 and earlier, but allow cqlsh to run with Python 3.6+
> -
>
> Key: CASSANDRA-19467
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19467
> Project: Cassandra
> Issue Type: Task
> Components: Tool/cqlsh
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 5.0-rc, 5.1
>
>
> In 4.0, we introduced Python 3.6 support. In CASSANDRA-19245, for the 5.0
> release, we dropped Python 3.6 and 3.7 support since Python 3.8 was the
> minimum supported version for version 3.29.0 of the Python driver, which we
> needed to support vectors. Unfortunately, that may break existing users of
> RHEL 7, which natively only supports Python 3.6.
> We should deprecate Python 3.6-3.7 (which are all either EOL or will be soon)
> and mention this in NEWS.txt/appropriate warnings at {{cqlsh}} startup, but
> we don't need to have cqlsh refuse to start entirely with 3.6-3.7 until our
> 6.0 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19467) Deprecate Python 3.8 and earlier, but allow cqlsh to run with Python 3.6+
[
https://issues.apache.org/jira/browse/CASSANDRA-19467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-19467:
Test and Documentation Plan: As long as this doesn't break existing CI
tooling, it should be fine.
Status: Patch Available (was: In Progress)
5.0 patch: [https://github.com/apache/cassandra/pull/3179]
Anyone w/ a paid CircleCI account willing to put this through a quick smoke
test?
> Deprecate Python 3.8 and earlier, but allow cqlsh to run with Python 3.6+
> -
>
> Key: CASSANDRA-19467
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19467
> Project: Cassandra
> Issue Type: Task
> Components: Tool/cqlsh
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 5.0-rc, 5.1
>
>
> In 4.0, we introduced Python 3.6 support. In CASSANDRA-19245, for the 5.0
> release, we dropped Python 3.6 and 3.7 support since Python 3.8 was the
> minimum supported version for version 3.29.0 of the Python driver, which we
> needed to support vectors. Unfortunately, that may break existing users of
> RHEL 7, which natively only supports Python 3.6.
> We should deprecate Python 3.6-3.8 (which are all either EOL or will be soon)
> and mention this in NEWS.txt/appropriate warnings at {{cqlsh}} startup, but
> we don't need to have cqlsh refuse to start entirely with 3.6-3.8 until our
> 6.0 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-19467) Deprecate Python 3.8 and earlier, but allow cqlsh to run with Python 3.6+
[
https://issues.apache.org/jira/browse/CASSANDRA-19467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827619#comment-17827619
]
Caleb Rackliffe edited comment on CASSANDRA-19467 at 3/15/24 11:47 PM:
---
5.0 patch: [https://github.com/apache/cassandra/pull/3179]
Anyone w/ a paid CircleCI account willing to put this through a quick smoke
test?
(I'll have my 5.0 CI results shortly...)
was (Author: maedhroz):
5.0 patch: [https://github.com/apache/cassandra/pull/3179]
Anyone w/ a paid CircleCI account willing to put this through a quick smoke
test?
> Deprecate Python 3.8 and earlier, but allow cqlsh to run with Python 3.6+
> -
>
> Key: CASSANDRA-19467
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19467
> Project: Cassandra
> Issue Type: Task
> Components: Tool/cqlsh
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 5.0-rc, 5.1
>
>
> In 4.0, we introduced Python 3.6 support. In CASSANDRA-19245, for the 5.0
> release, we dropped Python 3.6 and 3.7 support since Python 3.8 was the
> minimum supported version for version 3.29.0 of the Python driver, which we
> needed to support vectors. Unfortunately, that may break existing users of
> RHEL 7, which natively only supports Python 3.6.
> We should deprecate Python 3.6-3.8 (which are all either EOL or will be soon)
> and mention this in NEWS.txt/appropriate warnings at {{cqlsh}} startup, but
> we don't need to have cqlsh refuse to start entirely with 3.6-3.8 until our
> 6.0 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19469) python dtest packages should pin versions
[ https://issues.apache.org/jira/browse/CASSANDRA-19469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-19469: - Status: Patch Available (was: Open) > python dtest packages should pin versions > - > > Key: CASSANDRA-19469 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19469 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 3.0.30, 3.11.17, 4.0.13, 4.1.5, 5.0, 5.1 > > Time Spent: 20m > Remaining Estimate: 0h > > We have for example in CASSANDRA-19464 seen how allowing modules to > automatically upgrade themselves causes us problems. We should pin all of > these to specific versions so that the environment is entirely reproducible. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19476) CQL Management API
[ https://issues.apache.org/jira/browse/CASSANDRA-19476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated CASSANDRA-19476: Labels: CEP-38 (was: ) > CQL Management API > -- > > Key: CASSANDRA-19476 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19476 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Syntax >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: High > Labels: CEP-38 > Fix For: 5.x > > > We want to run management commands via CQL. > The goals are: > * To provide a way to run predefined management commands via CQL; > * To provide a mechanism for retrieving command definitions and metadata via > CQL; > * To provide information on all available management commands via virtual > tables; > * To provide a registry that stores all C* commands and their metadata > accordingly; > * To internal instrumentation and a reasonable plan for migrating cluster > management from JMX to CQL, taking into account backward compatibility and > adopted deprecation policies; > The discussion on the ML: > https://lists.apache.org/thread/pow83q92m666nqtwyw4m3b18nnkgj2y8 > The design document: > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-38%3A+CQL+Management+API -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19469) python dtest packages should pin versions
[ https://issues.apache.org/jira/browse/CASSANDRA-19469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827586#comment-17827586 ] Brandon Williams commented on CASSANDRA-19469: -- Note that my dtest branch doesn't have CASSANDRA-19474 so the describe failures should be expected. > python dtest packages should pin versions > - > > Key: CASSANDRA-19469 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19469 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 3.0.30, 3.11.17, 4.0.13, 4.1.5, 5.0, 5.1 > > Time Spent: 20m > Remaining Estimate: 0h > > We have for example in CASSANDRA-19464 seen how allowing modules to > automatically upgrade themselves causes us problems. We should pin all of > these to specific versions so that the environment is entirely reproducible. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19469) python dtest packages should pin versions
[ https://issues.apache.org/jira/browse/CASSANDRA-19469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827581#comment-17827581 ] Brandon Williams commented on CASSANDRA-19469: -- Updated to the 3.6 deps [here|https://github.com/driftx/cassandra-dtest/commit/33058bdfad26b799ef2f751b6010b074d3fdd8b0], with CI for [4.1|https://app.circleci.com/pipelines/github/driftx/cassandra/1523/workflows/3349b8f6-eb58-4788-8521-9d6fecfd86ae] and [5.0|https://app.circleci.com/pipelines/github/driftx/cassandra/1524/workflows/74676b19-c57e-488e-8f0c-2e25b40c5479]. > python dtest packages should pin versions > - > > Key: CASSANDRA-19469 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19469 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 3.0.30, 3.11.17, 4.0.13, 4.1.5, 5.0, 5.1 > > Time Spent: 20m > Remaining Estimate: 0h > > We have for example in CASSANDRA-19464 seen how allowing modules to > automatically upgrade themselves causes us problems. We should pin all of > these to specific versions so that the environment is entirely reproducible. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19469) python dtest packages should pin versions
[ https://issues.apache.org/jira/browse/CASSANDRA-19469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-19469: - Resolution: (was: Fixed) Status: Open (was: Resolved) Whoops, 5.0 isn't running 3.6 right now, we'll need to adjust these for that. > python dtest packages should pin versions > - > > Key: CASSANDRA-19469 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19469 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 3.0.30, 3.11.17, 4.0.13, 4.1.5, 5.0, 5.1 > > Time Spent: 20m > Remaining Estimate: 0h > > We have for example in CASSANDRA-19464 seen how allowing modules to > automatically upgrade themselves causes us problems. We should pin all of > these to specific versions so that the environment is entirely reproducible. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19476) CQL Management API
[ https://issues.apache.org/jira/browse/CASSANDRA-19476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated CASSANDRA-19476: Change Category: Operability Complexity: Challenging Fix Version/s: 5.x Priority: High (was: Normal) Status: Open (was: Triage Needed) > CQL Management API > -- > > Key: CASSANDRA-19476 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19476 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Syntax >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: High > Fix For: 5.x > > > We want to run management commands via CQL. > The goals are: > * To provide a way to run predefined management commands via CQL; > * To provide a mechanism for retrieving command definitions and metadata via > CQL; > * To provide information on all available management commands via virtual > tables; > * To provide a registry that stores all C* commands and their metadata > accordingly; > * To internal instrumentation and a reasonable plan for migrating cluster > management from JMX to CQL, taking into account backward compatibility and > adopted deprecation policies; > The discussion on the ML: > https://lists.apache.org/thread/pow83q92m666nqtwyw4m3b18nnkgj2y8 > The design document: > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-38%3A+CQL+Management+API -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19474) Fix cqlsh_tests/test_cqlsh.py
[ https://issues.apache.org/jira/browse/CASSANDRA-19474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-19474: -- Fix Version/s: 5.0-beta2 5.1 (was: 5.x) (was: 5.0-rc) Since Version: NA Source Control Link: https://github.com/apache/cassandra-dtest/commit/e377ac1239f0461ef25dcbafedbc931accfe563c Resolution: Fixed Status: Resolved (was: Ready to Commit) > Fix cqlsh_tests/test_cqlsh.py > - > > Key: CASSANDRA-19474 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19474 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Testing >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.0-beta2, 5.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > https://app.circleci.com/pipelines/github/driftx/cassandra/1522/workflows/f1cd6321-9a48-4a43-92b3-aed0b610fe5e/jobs/77610/tests -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra-dtest) branch trunk updated: fix cqlsh_tests/test_cqlsh.py to cope with cassandra_latest.yaml
This is an automated email from the ASF dual-hosted git repository.
smiklosovic pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-dtest.git
The following commit(s) were added to refs/heads/trunk by this push:
new e377ac12 fix cqlsh_tests/test_cqlsh.py to cope with
cassandra_latest.yaml
e377ac12 is described below
commit e377ac1239f0461ef25dcbafedbc931accfe563c
Author: Stefan Miklosovic
AuthorDate: Fri Mar 15 12:48:45 2024 +0100
fix cqlsh_tests/test_cqlsh.py to cope with cassandra_latest.yaml
patch by Stefan Miklosovic; reviewed by Brandon Williams for CASSANDRA-19474
---
cqlsh_tests/test_cqlsh.py | 26 +++---
dtest_config.py | 4
2 files changed, 23 insertions(+), 7 deletions(-)
diff --git a/cqlsh_tests/test_cqlsh.py b/cqlsh_tests/test_cqlsh.py
index 4452f153..012f3442 100644
--- a/cqlsh_tests/test_cqlsh.py
+++ b/cqlsh_tests/test_cqlsh.py
@@ -127,6 +127,13 @@ class TestCqlsh(Tester, CqlshMixin):
os.unlink(self.tempfile.name)
super(TestCqlsh, self).tearDown()
+
+def get_compaction(self):
+stcs = "AND compaction = {'class':
'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
'max_threshold': '32', 'min_threshold': '4'}"
+ucs = "AND compaction = {'class':
'org.apache.cassandra.db.compaction.UnifiedCompactionStrategy',
'max_sstables_to_compact': '64', 'min_sstable_size': '100MiB',
'scaling_parameters': 'T4', 'sstable_growth': '0.',
'target_sstable_size': '1GiB'}"
+return ucs if self.dtest_config.latest_config else stcs
+
+
@pytest.mark.depends_cqlshlib
@since('2.1.9')
def test_pycodestyle_compliance(self):
@@ -1147,6 +1154,7 @@ CREATE TYPE test.address_type (
self.execute(cql='USE test; DESCRIBE MATERIALIZED VIEW
"users_by_state"', expected_output=self.get_users_by_state_mv_output())
self.execute(cql='USE test; DESCRIBE "users_by_state"',
expected_output=self.get_users_by_state_mv_output())
+
def get_keyspace_output(self):
return ["CREATE KEYSPACE test WITH replication = {'class':
'SimpleStrategy', 'replication_factor': '1'} AND durable_writes = true;",
self.get_test_table_output(),
@@ -1179,7 +1187,7 @@ CREATE TYPE test.address_type (
AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
AND cdc = false
AND comment = ''
-AND compaction = {'class':
'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
'max_threshold': '32', 'min_threshold': '4'}
+%s
AND compression = {'chunk_length_in_kb': '16', 'class':
'org.apache.cassandra.io.compress.LZ4Compressor'}
AND memtable = 'default'
AND crc_check_chance = 1.0
@@ -1192,7 +1200,7 @@ CREATE TYPE test.address_type (
AND min_index_interval = 128
AND read_repair = 'BLOCKING'
AND speculative_retry = '99p';
-"""
+""" % self.get_compaction()
elif self.cluster.version() >= LooseVersion('4.1'):
create_table += """
) WITH CLUSTERING ORDER BY (col ASC)
@@ -1312,7 +1320,7 @@ CREATE TYPE test.address_type (
AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
AND cdc = false
AND comment = ''
-AND compaction = {'class':
'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
'max_threshold': '32', 'min_threshold': '4'}
+%s
AND compression = {'chunk_length_in_kb': '16', 'class':
'org.apache.cassandra.io.compress.LZ4Compressor'}
AND memtable = 'default'
AND crc_check_chance = 1.0
@@ -1325,7 +1333,7 @@ CREATE TYPE test.address_type (
AND min_index_interval = 128
AND read_repair = 'BLOCKING'
AND speculative_retry = '99p';
-"""
+""" % self.get_compaction()
elif self.cluster.version() >= LooseVersion('4.1'):
create_table = """
CREATE TABLE test.users (
@@ -1453,7 +1461,11 @@ CREATE TYPE test.address_type (
pass
else:
index = index[1:-1]
-return "CREATE INDEX {} ON {}.{} ({});".format(index, ks, table, col)
+
+if self.dtest_config.latest_config:
+return "CREATE CUSTOM INDEX {} ON {}.{} ({}) USING
'sai';".format(index, ks, table, col)
+else:
+return "CREATE INDEX {} ON {}.{} ({});".format(index, ks, table,
col)
def get_users_by_state_mv_output(self):
@@ -1471,7 +1483,7 @@ CREATE TYPE test.address_type (
AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
AND cdc = false
AND comment = ''
-AND compaction = {'class':
'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
'max_threshold': '32', 'min_threshold': '4'}
+
[jira] [Created] (CASSANDRA-19476) CQL Management API
Maxim Muzafarov created CASSANDRA-19476: --- Summary: CQL Management API Key: CASSANDRA-19476 URL: https://issues.apache.org/jira/browse/CASSANDRA-19476 Project: Cassandra Issue Type: Improvement Components: CQL/Syntax Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov We want to run management commands via CQL. The goals are: * To provide a way to run predefined management commands via CQL; * To provide a mechanism for retrieving command definitions and metadata via CQL; * To provide information on all available management commands via virtual tables; * To provide a registry that stores all C* commands and their metadata accordingly; * To internal instrumentation and a reasonable plan for migrating cluster management from JMX to CQL, taking into account backward compatibility and adopted deprecation policies; The discussion on the ML: https://lists.apache.org/thread/pow83q92m666nqtwyw4m3b18nnkgj2y8 The design document: https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-38%3A+CQL+Management+API -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19474) Fix cqlsh_tests/test_cqlsh.py
[ https://issues.apache.org/jira/browse/CASSANDRA-19474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-19474: - Reviewers: Brandon Williams (was: Brandon Williams, Brandon Williams) > Fix cqlsh_tests/test_cqlsh.py > - > > Key: CASSANDRA-19474 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19474 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Testing >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.0-rc, 5.x > > Time Spent: 20m > Remaining Estimate: 0h > > https://app.circleci.com/pipelines/github/driftx/cassandra/1522/workflows/f1cd6321-9a48-4a43-92b3-aed0b610fe5e/jobs/77610/tests -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19474) Fix cqlsh_tests/test_cqlsh.py
[ https://issues.apache.org/jira/browse/CASSANDRA-19474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-19474: - Status: Ready to Commit (was: Review In Progress) > Fix cqlsh_tests/test_cqlsh.py > - > > Key: CASSANDRA-19474 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19474 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Testing >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.0-rc, 5.x > > Time Spent: 20m > Remaining Estimate: 0h > > https://app.circleci.com/pipelines/github/driftx/cassandra/1522/workflows/f1cd6321-9a48-4a43-92b3-aed0b610fe5e/jobs/77610/tests -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19474) Fix cqlsh_tests/test_cqlsh.py
[ https://issues.apache.org/jira/browse/CASSANDRA-19474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827530#comment-17827530 ] Brandon Williams commented on CASSANDRA-19474: -- Left a comment that you can take or leave, otherwise +1 > Fix cqlsh_tests/test_cqlsh.py > - > > Key: CASSANDRA-19474 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19474 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Testing >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.0-rc, 5.x > > Time Spent: 20m > Remaining Estimate: 0h > > https://app.circleci.com/pipelines/github/driftx/cassandra/1522/workflows/f1cd6321-9a48-4a43-92b3-aed0b610fe5e/jobs/77610/tests -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19474) Fix cqlsh_tests/test_cqlsh.py
[ https://issues.apache.org/jira/browse/CASSANDRA-19474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-19474: - Reviewers: Brandon Williams, Brandon Williams Brandon Williams, Brandon Williams (was: Brandon Williams, Brandon Williams) Status: Review In Progress (was: Patch Available) > Fix cqlsh_tests/test_cqlsh.py > - > > Key: CASSANDRA-19474 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19474 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Testing >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.0-rc, 5.x > > Time Spent: 20m > Remaining Estimate: 0h > > https://app.circleci.com/pipelines/github/driftx/cassandra/1522/workflows/f1cd6321-9a48-4a43-92b3-aed0b610fe5e/jobs/77610/tests -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19474) Fix cqlsh_tests/test_cqlsh.py
[
https://issues.apache.org/jira/browse/CASSANDRA-19474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827529#comment-17827529
]
Stefan Miklosovic commented on CASSANDRA-19474:
---
[CASSANDRA-19474|https://github.com/instaclustr/cassandra/tree/CASSANDRA-19474]
{noformat}
java11_separate_tests
✓ j11_build7m 46s
✓ j11_cqlsh_dtests_py311 9m 24s
✓ j11_cqlsh_dtests_py311_latest10m 6s
✓ j11_cqlsh_dtests_py311_vnode 9m 49s
✓ j11_cqlsh_dtests_py386m 12s
✓ j11_cqlsh_dtests_py38_latest 9m 30s
✓ j11_cqlsh_dtests_py38_vnode 6m 7s
✓ j11_cqlshlib_tests 9m 19s
✓ j11_dtests 35m 17s
✓ j17_cqlsh_dtests_py311 5m 57s
✓ j17_cqlsh_dtests_py311_latest7m 19s
✓ j17_cqlsh_dtests_py311_vnode 6m 3s
✓ j17_cqlsh_dtests_py38 6m 4s
✓ j17_cqlsh_dtests_py38_latest 6m 18s
✓ j17_cqlsh_dtests_py38_vnode 6m 11s
✓ j17_dtests 34m 48s
✕ j11_dtests_latest 37m 15s
configuration_test.TestConfiguration test_change_durable_writes
✕ j17_dtests_latest 33m 18s
configuration_test.TestConfiguration test_change_durable_writes
{noformat}
[java11_separate_tests|https://app.circleci.com/pipelines/github/instaclustr/cassandra/4013/workflows/e4f9b639-9592-47e0-8184-1066c075dde8]
> Fix cqlsh_tests/test_cqlsh.py
> -
>
> Key: CASSANDRA-19474
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19474
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Testing
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 5.0-rc, 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://app.circleci.com/pipelines/github/driftx/cassandra/1522/workflows/f1cd6321-9a48-4a43-92b3-aed0b610fe5e/jobs/77610/tests
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19475) system_views.settings incorrectly handle array types
[
https://issues.apache.org/jira/browse/CASSANDRA-19475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-19475:
--
Description:
4.1+ gives
{noformat}
cqlsh> select value from system_views.settings where name =
'data_file_directories';
value
--
[Ljava.lang.String;@21b4c4bb
{noformat}
should be
{noformat}
cqlsh> select value from system_views.settings where name =
'data_file_directories';
value
[/home/fermat/dev/cassandra/cassandra-instaclustr/cassandra-4.1/data/data]
{noformat}
was:
4.1+ gives
{noformat}
cqlsh> select value from system_views.settings where name =
'data_file_directories'; value
--
[Ljava.lang.String;@21b4c4bb
{noformat}
should be
{noformat}
cqlsh> select value from system_views.settings where name =
'data_file_directories'; value
[/home/fermat/dev/cassandra/cassandra-instaclustr/cassandra-4.1/data/data]
{noformat}
> system_views.settings incorrectly handle array types
>
>
> Key: CASSANDRA-19475
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19475
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Virtual Tables
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.1.x, 5.0-rc, 5.x
>
>
> 4.1+ gives
> {noformat}
> cqlsh> select value from system_views.settings where name =
> 'data_file_directories';
> value
> --
> [Ljava.lang.String;@21b4c4bb
> {noformat}
>
> should be
>
> {noformat}
> cqlsh> select value from system_views.settings where name =
> 'data_file_directories';
> value
>
> [/home/fermat/dev/cassandra/cassandra-instaclustr/cassandra-4.1/data/data]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19475) system_views.settings incorrectly handle array types
[
https://issues.apache.org/jira/browse/CASSANDRA-19475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-19475:
--
Bug Category: Parent values: Code(13163)Level 1 values: Bug - Unclear
Impact(13164)
Complexity: Low Hanging Fruit
Discovered By: Adhoc Test
Fix Version/s: 4.1.x
5.0-rc
5.x
Severity: Low
Status: Open (was: Triage Needed)
> system_views.settings incorrectly handle array types
>
>
> Key: CASSANDRA-19475
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19475
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Virtual Tables
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.1.x, 5.0-rc, 5.x
>
>
> 4.1+ gives
> {noformat}
> cqlsh> select value from system_views.settings where name =
> 'data_file_directories'; value
> --
> [Ljava.lang.String;@21b4c4bb
> {noformat}
>
> should be
>
> {noformat}
> cqlsh> select value from system_views.settings where name =
> 'data_file_directories'; value
>
> [/home/fermat/dev/cassandra/cassandra-instaclustr/cassandra-4.1/data/data]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19475) system_views.settings incorrectly handle array types
Stefan Miklosovic created CASSANDRA-19475:
-
Summary: system_views.settings incorrectly handle array types
Key: CASSANDRA-19475
URL: https://issues.apache.org/jira/browse/CASSANDRA-19475
Project: Cassandra
Issue Type: Bug
Components: Feature/Virtual Tables
Reporter: Stefan Miklosovic
Assignee: Stefan Miklosovic
4.1+ gives
{noformat}
cqlsh> select value from system_views.settings where name =
'data_file_directories'; value
--
[Ljava.lang.String;@21b4c4bb
{noformat}
should be
{noformat}
cqlsh> select value from system_views.settings where name =
'data_file_directories'; value
[/home/fermat/dev/cassandra/cassandra-instaclustr/cassandra-4.1/data/data]
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19474) Fix cqlsh_tests/test_cqlsh.py
[ https://issues.apache.org/jira/browse/CASSANDRA-19474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-19474: - Summary: Fix cqlsh_tests/test_cqlsh.py (was: Fix cqlsh_tests/test_cqlsh.py for cassandra_latest.yaml) > Fix cqlsh_tests/test_cqlsh.py > - > > Key: CASSANDRA-19474 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19474 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Testing >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.0-rc, 5.x > > Time Spent: 10m > Remaining Estimate: 0h > > https://app.circleci.com/pipelines/github/driftx/cassandra/1522/workflows/f1cd6321-9a48-4a43-92b3-aed0b610fe5e/jobs/77610/tests -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19474) Fix cqlsh_tests/test_cqlsh.py for cassandra_latest.yaml
[ https://issues.apache.org/jira/browse/CASSANDRA-19474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-19474: -- Test and Documentation Plan: CI Status: Patch Available (was: In Progress) https://github.com/apache/cassandra-dtest/pull/258 > Fix cqlsh_tests/test_cqlsh.py for cassandra_latest.yaml > --- > > Key: CASSANDRA-19474 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19474 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Testing >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.0-rc, 5.x > > Time Spent: 10m > Remaining Estimate: 0h > > https://app.circleci.com/pipelines/github/driftx/cassandra/1522/workflows/f1cd6321-9a48-4a43-92b3-aed0b610fe5e/jobs/77610/tests -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19474) Fix cqlsh_tests/test_cqlsh.py for cassandra_latest.yaml
[ https://issues.apache.org/jira/browse/CASSANDRA-19474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-19474: -- Bug Category: Parent values: Correctness(12982)Level 1 values: Test Failure(12990) Complexity: Low Hanging Fruit Component/s: Legacy/Testing Discovered By: Adhoc Test Fix Version/s: 5.0-rc 5.x Severity: Low Status: Open (was: Triage Needed) > Fix cqlsh_tests/test_cqlsh.py for cassandra_latest.yaml > --- > > Key: CASSANDRA-19474 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19474 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Testing >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.0-rc, 5.x > > > https://app.circleci.com/pipelines/github/driftx/cassandra/1522/workflows/f1cd6321-9a48-4a43-92b3-aed0b610fe5e/jobs/77610/tests -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19474) Fix cqlsh_tests/test_cqlsh.py for cassandra_latest.yaml
[ https://issues.apache.org/jira/browse/CASSANDRA-19474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-19474: -- Description: https://app.circleci.com/pipelines/github/driftx/cassandra/1522/workflows/f1cd6321-9a48-4a43-92b3-aed0b610fe5e/jobs/77610/tests > Fix cqlsh_tests/test_cqlsh.py for cassandra_latest.yaml > --- > > Key: CASSANDRA-19474 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19474 > Project: Cassandra > Issue Type: Bug >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > > https://app.circleci.com/pipelines/github/driftx/cassandra/1522/workflows/f1cd6321-9a48-4a43-92b3-aed0b610fe5e/jobs/77610/tests -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19474) Fix cqlsh_tests/test_cqlsh.py for cassandra_latest.yaml
Stefan Miklosovic created CASSANDRA-19474: - Summary: Fix cqlsh_tests/test_cqlsh.py for cassandra_latest.yaml Key: CASSANDRA-19474 URL: https://issues.apache.org/jira/browse/CASSANDRA-19474 Project: Cassandra Issue Type: Bug Reporter: Stefan Miklosovic Assignee: Stefan Miklosovic -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-19471) Commitlog with direct io fails test_change_durable_writes
[
https://issues.apache.org/jira/browse/CASSANDRA-19471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827464#comment-17827464
]
Brandon Williams edited comment on CASSANDRA-19471 at 3/15/24 10:39 AM:
The IAE seems to be caused by the segment size being set to 1MB, at 2MB it
hasn't occurred but we still write the commitlog when we shouldn't and fail.
was (Author: brandon.williams):
The IAE seems to be caused by the segment size being set to 1MB, at 2MB it
doesn't hasn't occurred but we still write the commitlog when we shouldn't and
fail.
> Commitlog with direct io fails test_change_durable_writes
> -
>
> Key: CASSANDRA-19471
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19471
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Commit Log
>Reporter: Brandon Williams
>Priority: Normal
> Fix For: 5.0-rc, 5.x
>
>
> With the commitlog_disk_access_mode set to direct, and the improved
> configuration_test.py::TestConfiguration::test_change_durable_writes from
> CASSANDRA-19465, this fails with either:
> {noformat}
> AssertionError: Commitlog was written with durable writes disabled
> {noformat}
> Or what appears to be the original exception reported in CASSANDRA-19465:
> {noformat}
> node1: ERROR [PERIODIC-COMMIT-LOG-SYNCER] 2024-03-14 17:16:08,465
> StorageService.java:631 - Stopping native transport
> node1: ERROR [MutationStage-5] 2024-03-14 17:16:08,465
> StorageProxy.java:1670 - Failed to apply mutation locally :
> java.lang.IllegalArgumentException: newPosition > limit: (1048634 > 1048576)
> at java.base/java.nio.Buffer.createPositionException(Buffer.java:341)
> at java.base/java.nio.Buffer.position(Buffer.java:316)
> at java.base/java.nio.ByteBuffer.position(ByteBuffer.java:1516)
> at
> java.base/java.nio.MappedByteBuffer.position(MappedByteBuffer.java:321)
> at
> java.base/java.nio.MappedByteBuffer.position(MappedByteBuffer.java:73)
> at
> org.apache.cassandra.db.commitlog.CommitLogSegment.allocate(CommitLogSegment.java:216)
> at
> org.apache.cassandra.db.commitlog.CommitLogSegmentManagerStandard.allocate(CommitLogSegmentManagerStandard.java:52)
> at org.apache.cassandra.db.commitlog.CommitLog.add(CommitLog.java:307)
> at
> org.apache.cassandra.db.CassandraKeyspaceWriteHandler.addToCommitLog(CassandraKeyspaceWriteHandler.java:99)
> at
> org.apache.cassandra.db.CassandraKeyspaceWriteHandler.beginWrite(CassandraKeyspaceWriteHandler.java:53)
> at org.apache.cassandra.db.Keyspace.applyInternal(Keyspace.java:612)
> at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:497)
> at org.apache.cassandra.db.Mutation.apply(Mutation.java:244)
> at org.apache.cassandra.db.Mutation.apply(Mutation.java:264)
> at
> org.apache.cassandra.service.StorageProxy$4.runMayThrow(StorageProxy.java:1664)
> at
> org.apache.cassandra.service.StorageProxy$LocalMutationRunnable.run(StorageProxy.java:2624)
> at
> org.apache.cassandra.concurrent.ExecutionFailure$2.run(ExecutionFailure.java:163)
> at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:143)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:833)
> node1: ERROR [PERIODIC-COMMIT-LOG-SYNCER] 2024-03-14 17:16:08,470
> StorageService.java:636 - Stopping gossiper
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19471) Commitlog with direct io fails test_change_durable_writes
[
https://issues.apache.org/jira/browse/CASSANDRA-19471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827464#comment-17827464
]
Brandon Williams commented on CASSANDRA-19471:
--
The IAE seems to be caused by the segment size being set to 1MB, at 2MB it
doesn't hasn't occurred but we still write the commitlog when we shouldn't and
fail.
> Commitlog with direct io fails test_change_durable_writes
> -
>
> Key: CASSANDRA-19471
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19471
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Commit Log
>Reporter: Brandon Williams
>Priority: Normal
> Fix For: 5.0-rc, 5.x
>
>
> With the commitlog_disk_access_mode set to direct, and the improved
> configuration_test.py::TestConfiguration::test_change_durable_writes from
> CASSANDRA-19465, this fails with either:
> {noformat}
> AssertionError: Commitlog was written with durable writes disabled
> {noformat}
> Or what appears to be the original exception reported in CASSANDRA-19465:
> {noformat}
> node1: ERROR [PERIODIC-COMMIT-LOG-SYNCER] 2024-03-14 17:16:08,465
> StorageService.java:631 - Stopping native transport
> node1: ERROR [MutationStage-5] 2024-03-14 17:16:08,465
> StorageProxy.java:1670 - Failed to apply mutation locally :
> java.lang.IllegalArgumentException: newPosition > limit: (1048634 > 1048576)
> at java.base/java.nio.Buffer.createPositionException(Buffer.java:341)
> at java.base/java.nio.Buffer.position(Buffer.java:316)
> at java.base/java.nio.ByteBuffer.position(ByteBuffer.java:1516)
> at
> java.base/java.nio.MappedByteBuffer.position(MappedByteBuffer.java:321)
> at
> java.base/java.nio.MappedByteBuffer.position(MappedByteBuffer.java:73)
> at
> org.apache.cassandra.db.commitlog.CommitLogSegment.allocate(CommitLogSegment.java:216)
> at
> org.apache.cassandra.db.commitlog.CommitLogSegmentManagerStandard.allocate(CommitLogSegmentManagerStandard.java:52)
> at org.apache.cassandra.db.commitlog.CommitLog.add(CommitLog.java:307)
> at
> org.apache.cassandra.db.CassandraKeyspaceWriteHandler.addToCommitLog(CassandraKeyspaceWriteHandler.java:99)
> at
> org.apache.cassandra.db.CassandraKeyspaceWriteHandler.beginWrite(CassandraKeyspaceWriteHandler.java:53)
> at org.apache.cassandra.db.Keyspace.applyInternal(Keyspace.java:612)
> at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:497)
> at org.apache.cassandra.db.Mutation.apply(Mutation.java:244)
> at org.apache.cassandra.db.Mutation.apply(Mutation.java:264)
> at
> org.apache.cassandra.service.StorageProxy$4.runMayThrow(StorageProxy.java:1664)
> at
> org.apache.cassandra.service.StorageProxy$LocalMutationRunnable.run(StorageProxy.java:2624)
> at
> org.apache.cassandra.concurrent.ExecutionFailure$2.run(ExecutionFailure.java:163)
> at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:143)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:833)
> node1: ERROR [PERIODIC-COMMIT-LOG-SYNCER] 2024-03-14 17:16:08,470
> StorageService.java:636 - Stopping gossiper
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19471) Commitlog with direct io fails test_change_durable_writes
[
https://issues.apache.org/jira/browse/CASSANDRA-19471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827446#comment-17827446
]
Stefan Miklosovic commented on CASSANDRA-19471:
---
[~blambov] I tried to make the sense of it here (1). It is very suspicious
that we are so far in the control flow, on face value one would say that if it
is not possible to allocate required space in the current segment, it would
return null and it would keep trying until it does. It just should not go so
far at all ...
(1)
https://issues.apache.org/jira/browse/CASSANDRA-19465?focusedCommentId=17827038&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17827038
> Commitlog with direct io fails test_change_durable_writes
> -
>
> Key: CASSANDRA-19471
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19471
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Commit Log
>Reporter: Brandon Williams
>Priority: Normal
> Fix For: 5.0-rc, 5.x
>
>
> With the commitlog_disk_access_mode set to direct, and the improved
> configuration_test.py::TestConfiguration::test_change_durable_writes from
> CASSANDRA-19465, this fails with either:
> {noformat}
> AssertionError: Commitlog was written with durable writes disabled
> {noformat}
> Or what appears to be the original exception reported in CASSANDRA-19465:
> {noformat}
> node1: ERROR [PERIODIC-COMMIT-LOG-SYNCER] 2024-03-14 17:16:08,465
> StorageService.java:631 - Stopping native transport
> node1: ERROR [MutationStage-5] 2024-03-14 17:16:08,465
> StorageProxy.java:1670 - Failed to apply mutation locally :
> java.lang.IllegalArgumentException: newPosition > limit: (1048634 > 1048576)
> at java.base/java.nio.Buffer.createPositionException(Buffer.java:341)
> at java.base/java.nio.Buffer.position(Buffer.java:316)
> at java.base/java.nio.ByteBuffer.position(ByteBuffer.java:1516)
> at
> java.base/java.nio.MappedByteBuffer.position(MappedByteBuffer.java:321)
> at
> java.base/java.nio.MappedByteBuffer.position(MappedByteBuffer.java:73)
> at
> org.apache.cassandra.db.commitlog.CommitLogSegment.allocate(CommitLogSegment.java:216)
> at
> org.apache.cassandra.db.commitlog.CommitLogSegmentManagerStandard.allocate(CommitLogSegmentManagerStandard.java:52)
> at org.apache.cassandra.db.commitlog.CommitLog.add(CommitLog.java:307)
> at
> org.apache.cassandra.db.CassandraKeyspaceWriteHandler.addToCommitLog(CassandraKeyspaceWriteHandler.java:99)
> at
> org.apache.cassandra.db.CassandraKeyspaceWriteHandler.beginWrite(CassandraKeyspaceWriteHandler.java:53)
> at org.apache.cassandra.db.Keyspace.applyInternal(Keyspace.java:612)
> at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:497)
> at org.apache.cassandra.db.Mutation.apply(Mutation.java:244)
> at org.apache.cassandra.db.Mutation.apply(Mutation.java:264)
> at
> org.apache.cassandra.service.StorageProxy$4.runMayThrow(StorageProxy.java:1664)
> at
> org.apache.cassandra.service.StorageProxy$LocalMutationRunnable.run(StorageProxy.java:2624)
> at
> org.apache.cassandra.concurrent.ExecutionFailure$2.run(ExecutionFailure.java:163)
> at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:143)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:833)
> node1: ERROR [PERIODIC-COMMIT-LOG-SYNCER] 2024-03-14 17:16:08,470
> StorageService.java:636 - Stopping gossiper
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19473) Latency Spike on NTR startup
[
https://issues.apache.org/jira/browse/CASSANDRA-19473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827443#comment-17827443
]
Stefan Miklosovic commented on CASSANDRA-19473:
---
Thanks Cam, I think that this qualifies as an improvement, not a bug fix, as
you correctly assumed when you created this ticket. That means that this will
be targetted for trunk branch if we ever reach a consensus this is a sensible
thing to do.
> Latency Spike on NTR startup
>
>
> Key: CASSANDRA-19473
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19473
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Cameron Zemek
>Priority: Normal
>
> Firstly you need the patch from
> https://issues.apache.org/jira/browse/CASSANDRA-18845 to solve consistency
> query errors on startup. With that patch there is still a further issue we
> see on some clusters where the latency spikes too high when initially
> starting. I see pending compactions and hints metrics increased during this
> time.
> I tried lowering the hint delivery threshold across the cluster thinking it
> was overloading the node starting up, but this didn't resolve the issue. So
> at this time I am not sure what the root cause (I still think its combination
> of the compactions and hints).
> As workaround I have this small code change:
> {code:java}
> int START_NATIVE_DELAY =
> Integer.getInteger("cassandra.start_native_transport_delay_secs", 120);
> if (START_NATIVE_DELAY > 0)
> {
> logger.info("Waiting an extra {} seconds before enabling
> NTR", START_NATIVE_DELAY);
> Uninterruptibles.sleepUninterruptibly(START_NATIVE_DELAY,
> TimeUnit.SECONDS);
> }
> startNativeTransport();
> {code}
> Where wait an configurable time before starting native transport. Delaying
> NTR startup resolved the issue.
> A better solution would be to wait for hints/compactions or whatever is root
> cause to complete.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
