[jira] [Comment Edited] (CASSANDRA-15829) Upgrade to logback 1.2.3 to address CVE
[ https://issues.apache.org/jira/browse/CASSANDRA-15829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17260953#comment-17260953 ] Ivo Dujmovic edited comment on CASSANDRA-15829 at 1/8/21, 2:52 AM: --- Mark, can you please confirm this is a legit new issue and assign it to someone? was (Author: ivodujmovic): Maybe you can confirm this is a legit new issue and assign it to someone? > Upgrade to logback 1.2.3 to address CVE > --- > > Key: CASSANDRA-15829 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15829 > Project: Cassandra > Issue Type: Improvement >Reporter: Kevin Eveker >Assignee: Mark Denihan >Priority: Normal > > Recent scan results identified the following CVE that requires this upgrade > to address > [https://nvd.nist.gov/vuln/detail/CVE-2017-5929] -- 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-15829) Upgrade to logback 1.2.3 to address CVE
[ https://issues.apache.org/jira/browse/CASSANDRA-15829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivo Dujmovic reassigned CASSANDRA-15829: Assignee: Mark Denihan Maybe you can confirm this is a legit new issue and assign it to someone? > Upgrade to logback 1.2.3 to address CVE > --- > > Key: CASSANDRA-15829 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15829 > Project: Cassandra > Issue Type: Improvement >Reporter: Kevin Eveker >Assignee: Mark Denihan >Priority: Normal > > Recent scan results identified the following CVE that requires this upgrade > to address > [https://nvd.nist.gov/vuln/detail/CVE-2017-5929] -- 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-15829) Upgrade to logback 1.2.3 to address CVE
[ https://issues.apache.org/jira/browse/CASSANDRA-15829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17260952#comment-17260952 ] Ivo Dujmovic commented on CASSANDRA-15829: -- [~c3-keveker] I do not see why this is a clone of CASSANDRA-15828 which relates to removing jackson-core-asl-1.9.13.jar (successful in 3.11.7) bash-4.2$ find / -name 'jackson*' /opt/cassandra/lib/licenses/jackson-mapper-asl-1.9.13.txt /opt/cassandra/lib/licenses/jackson-core-asl-1.9.13.txt /opt/cassandra/lib/jackson-databind-2.9.10.4.jar /opt/cassandra/lib/jackson-annotations-2.9.10.jar /opt/cassandra/lib/jackson-core-2.9.10.jar However this Jira is for upgrade of logback core to 1.2.0 or later. Which is still open in cassandra 3.11.8: bash-4.2$ find / -name 'logback-core*' /opt/cassandra/lib/logback-core-1.1.3.jar /opt/cassandra/lib/licenses/logback-core-1.1.3.txt > Upgrade to logback 1.2.3 to address CVE > --- > > Key: CASSANDRA-15829 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15829 > Project: Cassandra > Issue Type: Improvement >Reporter: Kevin Eveker >Priority: Normal > > Recent scan results identified the following CVE that requires this upgrade > to address > [https://nvd.nist.gov/vuln/detail/CVE-2017-5929] -- 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-16347) Fix upgrade python dtest upgrade_tests/upgrade_through_versions_test.py
[
https://issues.apache.org/jira/browse/CASSANDRA-16347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17260915#comment-17260915
]
David Capwell commented on CASSANDRA-16347:
---
cool, ill wait for [~samt] to review the other one (as I don't know if it makes
sense), if so can merge this after.
Thanks for all the work [~aholmber]!
> Fix upgrade python dtest upgrade_tests/upgrade_through_versions_test.py
> ---
>
> Key: CASSANDRA-16347
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16347
> Project: Cassandra
> Issue Type: Bug
> Components: CI, Test/dtest/python
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/846/workflows/bee81d86-f720-4fc2-b3e7-7ed19ec3c9f0/jobs/4988/tests
> upgrade_tests/upgrade_through_versions_test.py seems to have a set of tests
> which fail with the following
> {code}
> > raise RuntimeError(message)
> E RuntimeError: A subprocess has terminated early. Subprocess
> statuses: Process-1 (is_alive: True), Process-2 (is_alive: False), attempting
> to terminate remaining subprocesses now.
> upgrade_tests/upgrade_through_versions_test.py:418: RuntimeError
> {code}
> The tests found to be failing were:
> test_rolling_upgrade_with_internode_ssl
> test_rolling_upgrade
--
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-16354) python dtest fails to talk to 2.2 using protocol 4 but cqlsh has no issue
[
https://issues.apache.org/jira/browse/CASSANDRA-16354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-16354:
--
Reviewers: David Capwell, David Capwell (was: David Capwell)
David Capwell, David Capwell
Status: Review In Progress (was: Patch Available)
> python dtest fails to talk to 2.2 using protocol 4 but cqlsh has no issue
> -
>
> Key: CASSANDRA-16354
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16354
> Project: Cassandra
> Issue Type: Bug
> Components: CI, Test/dtest/python
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/850/workflows/79486fdd-06d0-4d04-aa32-0fa648182356/jobs/5019/artifacts
> We see that upgrade tests which talk to 2.2 clusters fail with the following
> error
> {code}
> > ???
> E cassandra.cluster.NoHostAvailable: ('Unable to connect to any servers',
> {'127.0.0.1:9042': DriverException('ProtocolError returned from server while
> using explicitly set client protocol_version 4',)})
> {code}
> For some reason, setting protocol version 4 causes 2.2 to fail, but this does
> not happen when using cqlsh (from trunk)
> {code}
> ./bin/cqlsh --protocol-version=4
> Connected to Test Cluster at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 2.2.20-SNAPSHOT | CQL spec 3.3.1 | Native protocol
> v4]
> Use HELP for help.
> {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-16354) python dtest fails to talk to 2.2 using protocol 4 but cqlsh has no issue
[
https://issues.apache.org/jira/browse/CASSANDRA-16354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17260912#comment-17260912
]
David Capwell commented on CASSANDRA-16354:
---
[~samt] mind being a reviewer for this as you have more context?
bq. I'd prefer to add the override in tests rather making the suggested changes
on the server side, as the entire point of the capping is to make 2.x -> 3.x
upgrades safe, which this would subvert.
If the flag is enough for the test +1 from me, but don't know if this is a good
thing in general (hoping sam can approve that part =D).
Sam, if you are +1 to the dtest patch I can run ci/merge.
> python dtest fails to talk to 2.2 using protocol 4 but cqlsh has no issue
> -
>
> Key: CASSANDRA-16354
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16354
> Project: Cassandra
> Issue Type: Bug
> Components: CI, Test/dtest/python
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/850/workflows/79486fdd-06d0-4d04-aa32-0fa648182356/jobs/5019/artifacts
> We see that upgrade tests which talk to 2.2 clusters fail with the following
> error
> {code}
> > ???
> E cassandra.cluster.NoHostAvailable: ('Unable to connect to any servers',
> {'127.0.0.1:9042': DriverException('ProtocolError returned from server while
> using explicitly set client protocol_version 4',)})
> {code}
> For some reason, setting protocol version 4 causes 2.2 to fail, but this does
> not happen when using cqlsh (from trunk)
> {code}
> ./bin/cqlsh --protocol-version=4
> Connected to Test Cluster at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 2.2.20-SNAPSHOT | CQL spec 3.3.1 | Native protocol
> v4]
> Use HELP for help.
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16331) Fix upgrade python dtest test_keys_index_3_x_created - upgrade_tests.thrift_upgrade_test.TestUpgradeTo40
[
https://issues.apache.org/jira/browse/CASSANDRA-16331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-16331:
--
Fix Version/s: (was: 4.0-beta)
NA
Since Version: NA
Source Control Link:
https://github.com/apache/cassandra-dtest/commit/b6ca1c75d233872a13d519a03d2e3ab6a321e20e
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
committed, thanks!
> Fix upgrade python dtest test_keys_index_3_x_created -
> upgrade_tests.thrift_upgrade_test.TestUpgradeTo40
>
>
> Key: CASSANDRA-16331
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16331
> Project: Cassandra
> Issue Type: Bug
> Components: CI, Test/dtest/python
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: NA
>
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/843/workflows/9545f259-0a61-4ba8-8dea-485a33136032/jobs/4964
> {code}
> test setup failure
> file /home/cassandra/cassandra-dtest/upgrade_tests/thrift_upgrade_test.py,
> line 454
> def test_keys_index_3_x_created(self, from_version):
> E fixture 'from_version' not found
> > available fixtures: cache, capfd, capfdbinary, caplog, capsys,
> > capsysbinary, doctest_namespace, dtest_config, fixture_dtest_cluster_name,
> > fixture_dtest_create_cluster_func, fixture_dtest_setup,
> > fixture_dtest_setup_overrides, fixture_log_test_name_and_date,
> > fixture_logging_setup, fixture_maybe_skip_tests_requiring_novnodes,
> > fixture_ported_to_in_jvm, fixture_since, fixture_skip_version,
> > install_debugging_signal_handler, log_global_env_facts, monkeypatch,
> > pytestconfig, record_property, record_xml_attribute, record_xml_property,
> > recwarn, set_dtest_setup_on_function, tmpdir, tmpdir_factory
> > use 'pytest --fixtures [testpath]' for help on them.
> /home/cassandra/cassandra-dtest/upgrade_tests/thrift_upgrade_test.py:454
> {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
[cassandra-dtest] branch trunk updated: pytest is not meant to run internal parameterized test method
This is an automated email from the ASF dual-hosted git repository.
dcapwell 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 b6ca1c7 pytest is not meant to run internal parameterized test method
b6ca1c7 is described below
commit b6ca1c75d233872a13d519a03d2e3ab6a321e20e
Author: Adam Holmberg
AuthorDate: Tue Jan 5 16:24:08 2021 -0600
pytest is not meant to run internal parameterized test method
patch by Adam Holmberg; reviewed by David Capwell for CASSANDRA-16331
---
upgrade_tests/thrift_upgrade_test.py | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/upgrade_tests/thrift_upgrade_test.py
b/upgrade_tests/thrift_upgrade_test.py
index 878d265..cad1d7e 100644
--- a/upgrade_tests/thrift_upgrade_test.py
+++ b/upgrade_tests/thrift_upgrade_test.py
@@ -446,12 +446,12 @@ class TestUpgradeTo40(Tester):
return self._connect(self.cluster.nodelist()[0])
def test_keys_index_3_0_created(self):
-self.test_keys_index_3_x_created('github:apache/cassandra-3.0')
+self._test_keys_index_3_x_created('github:apache/cassandra-3.0')
def test_keys_index_3_11_created(self):
-self.test_keys_index_3_x_created('github:apache/cassandra-3.11')
+self._test_keys_index_3_x_created('github:apache/cassandra-3.11')
-def test_keys_index_3_x_created(self, from_version):
+def _test_keys_index_3_x_created(self, from_version):
cql, thrift = self.prepare(start_version=from_version,
num_nodes=3,
rf=3)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16331) Fix upgrade python dtest test_keys_index_3_x_created - upgrade_tests.thrift_upgrade_test.TestUpgradeTo40
[
https://issues.apache.org/jira/browse/CASSANDRA-16331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-16331:
--
Status: Ready to Commit (was: Review In Progress)
+1
> Fix upgrade python dtest test_keys_index_3_x_created -
> upgrade_tests.thrift_upgrade_test.TestUpgradeTo40
>
>
> Key: CASSANDRA-16331
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16331
> Project: Cassandra
> Issue Type: Bug
> Components: CI, Test/dtest/python
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/843/workflows/9545f259-0a61-4ba8-8dea-485a33136032/jobs/4964
> {code}
> test setup failure
> file /home/cassandra/cassandra-dtest/upgrade_tests/thrift_upgrade_test.py,
> line 454
> def test_keys_index_3_x_created(self, from_version):
> E fixture 'from_version' not found
> > available fixtures: cache, capfd, capfdbinary, caplog, capsys,
> > capsysbinary, doctest_namespace, dtest_config, fixture_dtest_cluster_name,
> > fixture_dtest_create_cluster_func, fixture_dtest_setup,
> > fixture_dtest_setup_overrides, fixture_log_test_name_and_date,
> > fixture_logging_setup, fixture_maybe_skip_tests_requiring_novnodes,
> > fixture_ported_to_in_jvm, fixture_since, fixture_skip_version,
> > install_debugging_signal_handler, log_global_env_facts, monkeypatch,
> > pytestconfig, record_property, record_xml_attribute, record_xml_property,
> > recwarn, set_dtest_setup_on_function, tmpdir, tmpdir_factory
> > use 'pytest --fixtures [testpath]' for help on them.
> /home/cassandra/cassandra-dtest/upgrade_tests/thrift_upgrade_test.py:454
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16331) Fix upgrade python dtest test_keys_index_3_x_created - upgrade_tests.thrift_upgrade_test.TestUpgradeTo40
[
https://issues.apache.org/jira/browse/CASSANDRA-16331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-16331:
--
Reviewers: David Capwell, David Capwell (was: David Capwell)
David Capwell, David Capwell
Status: Review In Progress (was: Patch Available)
> Fix upgrade python dtest test_keys_index_3_x_created -
> upgrade_tests.thrift_upgrade_test.TestUpgradeTo40
>
>
> Key: CASSANDRA-16331
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16331
> Project: Cassandra
> Issue Type: Bug
> Components: CI, Test/dtest/python
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/843/workflows/9545f259-0a61-4ba8-8dea-485a33136032/jobs/4964
> {code}
> test setup failure
> file /home/cassandra/cassandra-dtest/upgrade_tests/thrift_upgrade_test.py,
> line 454
> def test_keys_index_3_x_created(self, from_version):
> E fixture 'from_version' not found
> > available fixtures: cache, capfd, capfdbinary, caplog, capsys,
> > capsysbinary, doctest_namespace, dtest_config, fixture_dtest_cluster_name,
> > fixture_dtest_create_cluster_func, fixture_dtest_setup,
> > fixture_dtest_setup_overrides, fixture_log_test_name_and_date,
> > fixture_logging_setup, fixture_maybe_skip_tests_requiring_novnodes,
> > fixture_ported_to_in_jvm, fixture_since, fixture_skip_version,
> > install_debugging_signal_handler, log_global_env_facts, monkeypatch,
> > pytestconfig, record_property, record_xml_attribute, record_xml_property,
> > recwarn, set_dtest_setup_on_function, tmpdir, tmpdir_factory
> > use 'pytest --fixtures [testpath]' for help on them.
> /home/cassandra/cassandra-dtest/upgrade_tests/thrift_upgrade_test.py:454
> {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-16226) COMPACT STORAGE SSTables created before 3.0 are not correctly skipped by timestamp due to missing primary key liveness info
[
https://issues.apache.org/jira/browse/CASSANDRA-16226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17260886#comment-17260886
]
Caleb Rackliffe commented on CASSANDRA-16226:
-
Thanks [~mck]!
> COMPACT STORAGE SSTables created before 3.0 are not correctly skipped by
> timestamp due to missing primary key liveness info
> ---
>
> Key: CASSANDRA-16226
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16226
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Labels: perfomance, upgrade
> Fix For: 2.2.20, 3.0.24, 4.0-beta5, 4.0
>
> Time Spent: 5h 10m
> Remaining Estimate: 0h
>
> This was discovered while tracking down a spike in the number of SSTables
> per read for a COMPACT STORAGE table after a 2.1 -> 3.0 upgrade. Before 3.0,
> there is no direct analog of 3.0's primary key liveness info. When we upgrade
> 2.1 COMPACT STORAGE SSTables to the mf format, we simply don't write row
> timestamps, even if the original mutations were INSERTs. On read, when we
> look at SSTables in order from newest to oldest max timestamp, we expect to
> have this primary key liveness information to determine whether we can skip
> older SSTables after finding completely populated rows.
> ex. I have three SSTables in a COMPACT STORAGE table with max timestamps
> 1000, 2000, and 3000. There are many rows in a particular partition, making
> filtering on the min and max clustering effectively a no-op. All data is
> inserted, and there are no partial updates. A fully specified row with
> timestamp 2500 exists in the SSTable with a max timestamp of 3000. With a
> proper row timestamp in hand, we can easily ignore the SSTables w/ max
> timestamps of 1000 and 2000. Without it, we read 3 SSTables instead of 1,
> which likely means a significant performance regression.
> The following test illustrates this difference in behavior between 2.1 and
> 3.0:
> https://github.com/maedhroz/cassandra/commit/84ce9242bedd735ca79d4f06007d127de6a82800
> A solution here might be as simple as having
> {{SinglePartitionReadCommand#canRemoveRow()}} only inspect primary key
> liveness information for non-compact/CQL tables. Tombstones seem to be
> handled at a level above that anyway. (One potential problem with that is
> whether or not the distinction will continue to exist in 4.0, and dropping
> compact storage from a table doesn't magically make pk liveness information
> appear.)
--
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-16373) Deploy testing docker images to hub.docker.com/u/apache/
[ https://issues.apache.org/jira/browse/CASSANDRA-16373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16373: --- Fix Version/s: 4.0 > Deploy testing docker images to hub.docker.com/u/apache/ > - > > Key: CASSANDRA-16373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16373 > Project: Cassandra > Issue Type: Task > Components: Test/dtest/java, Test/dtest/python, Test/unit >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 2.2.20, 3.0.24, 3.11.10, 4.0-beta5, 4.0 > > > INFRA-21103 demonstrates PMC individuals can get access to the apache > organisation on dockerhub (and the dockerhub "cassandra" team). > We have a number of docker images (used in testing and CI) that are currently > deployed under individual user accounts on dockerhub. These can now be > deployed under https://hub.docker.com/u/apache -- 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-16226) COMPACT STORAGE SSTables created before 3.0 are not correctly skipped by timestamp due to missing primary key liveness info
[
https://issues.apache.org/jira/browse/CASSANDRA-16226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-16226:
---
Since Version: 3.0 alpha 1
Source Control Link:
https://github.com/apache/cassandra/commit/f8500ee911343eb8826f9c44bb6db2ab780f6327
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed as
[f8500ee911343eb8826f9c44bb6db2ab780f6327|https://github.com/apache/cassandra/commit/f8500ee911343eb8826f9c44bb6db2ab780f6327]
> COMPACT STORAGE SSTables created before 3.0 are not correctly skipped by
> timestamp due to missing primary key liveness info
> ---
>
> Key: CASSANDRA-16226
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16226
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Labels: perfomance, upgrade
> Fix For: 3.0.x, 3.11.x, 4.0-beta
>
> Time Spent: 5h 10m
> Remaining Estimate: 0h
>
> This was discovered while tracking down a spike in the number of SSTables
> per read for a COMPACT STORAGE table after a 2.1 -> 3.0 upgrade. Before 3.0,
> there is no direct analog of 3.0's primary key liveness info. When we upgrade
> 2.1 COMPACT STORAGE SSTables to the mf format, we simply don't write row
> timestamps, even if the original mutations were INSERTs. On read, when we
> look at SSTables in order from newest to oldest max timestamp, we expect to
> have this primary key liveness information to determine whether we can skip
> older SSTables after finding completely populated rows.
> ex. I have three SSTables in a COMPACT STORAGE table with max timestamps
> 1000, 2000, and 3000. There are many rows in a particular partition, making
> filtering on the min and max clustering effectively a no-op. All data is
> inserted, and there are no partial updates. A fully specified row with
> timestamp 2500 exists in the SSTable with a max timestamp of 3000. With a
> proper row timestamp in hand, we can easily ignore the SSTables w/ max
> timestamps of 1000 and 2000. Without it, we read 3 SSTables instead of 1,
> which likely means a significant performance regression.
> The following test illustrates this difference in behavior between 2.1 and
> 3.0:
> https://github.com/maedhroz/cassandra/commit/84ce9242bedd735ca79d4f06007d127de6a82800
> A solution here might be as simple as having
> {{SinglePartitionReadCommand#canRemoveRow()}} only inspect primary key
> liveness information for non-compact/CQL tables. Tombstones seem to be
> handled at a level above that anyway. (One potential problem with that is
> whether or not the distinction will continue to exist in 4.0, and dropping
> compact storage from a table doesn't magically make pk liveness information
> appear.)
--
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-16226) COMPACT STORAGE SSTables created before 3.0 are not correctly skipped by timestamp due to missing primary key liveness info
[
https://issues.apache.org/jira/browse/CASSANDRA-16226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-16226:
---
Fix Version/s: (was: 4.0-beta)
(was: 3.11.x)
(was: 3.0.x)
4.0
4.0-beta5
3.0.24
2.2.20
> COMPACT STORAGE SSTables created before 3.0 are not correctly skipped by
> timestamp due to missing primary key liveness info
> ---
>
> Key: CASSANDRA-16226
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16226
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Labels: perfomance, upgrade
> Fix For: 2.2.20, 3.0.24, 4.0-beta5, 4.0
>
> Time Spent: 5h 10m
> Remaining Estimate: 0h
>
> This was discovered while tracking down a spike in the number of SSTables
> per read for a COMPACT STORAGE table after a 2.1 -> 3.0 upgrade. Before 3.0,
> there is no direct analog of 3.0's primary key liveness info. When we upgrade
> 2.1 COMPACT STORAGE SSTables to the mf format, we simply don't write row
> timestamps, even if the original mutations were INSERTs. On read, when we
> look at SSTables in order from newest to oldest max timestamp, we expect to
> have this primary key liveness information to determine whether we can skip
> older SSTables after finding completely populated rows.
> ex. I have three SSTables in a COMPACT STORAGE table with max timestamps
> 1000, 2000, and 3000. There are many rows in a particular partition, making
> filtering on the min and max clustering effectively a no-op. All data is
> inserted, and there are no partial updates. A fully specified row with
> timestamp 2500 exists in the SSTable with a max timestamp of 3000. With a
> proper row timestamp in hand, we can easily ignore the SSTables w/ max
> timestamps of 1000 and 2000. Without it, we read 3 SSTables instead of 1,
> which likely means a significant performance regression.
> The following test illustrates this difference in behavior between 2.1 and
> 3.0:
> https://github.com/maedhroz/cassandra/commit/84ce9242bedd735ca79d4f06007d127de6a82800
> A solution here might be as simple as having
> {{SinglePartitionReadCommand#canRemoveRow()}} only inspect primary key
> liveness information for non-compact/CQL tables. Tombstones seem to be
> handled at a level above that anyway. (One potential problem with that is
> whether or not the distinction will continue to exist in 4.0, and dropping
> compact storage from a table doesn't magically make pk liveness information
> appear.)
--
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.0' into cassandra-3.11
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch cassandra-3.11 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 3e24c0349a1f091c20602b899d72a447a17d57b9 Merge: 2473ee3 f8500ee Author: Mick Semb Wever AuthorDate: Thu Jan 7 23:02:49 2021 +0100 Merge branch 'cassandra-3.0' into cassandra-3.11 CHANGES.txt| 1 + doc/source/cql/appendices.rst | 9 +- .../cassandra/db/SinglePartitionReadCommand.java | 37 +++- .../upgrade/CompactStorage2to3UpgradeTest.java | 6 +- .../miscellaneous/SSTablesIteratedTest.java| 236 - .../cql3/validation/operations/UpdateTest.java | 14 +- 6 files changed, 278 insertions(+), 25 deletions(-) diff --cc CHANGES.txt index c9602f1,54456c1..35129a2 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,8 -1,6 +1,9 @@@ -3.0.24: - * Fix skipping on pre-3.0 created compact storage sstables due to missing primary key liveness (CASSANDRA-16226) +3.11.10 * Fix DecimalDeserializer#toString OOM (CASSANDRA-14925) + * Rate limit validation compactions using compaction_throughput_mb_per_sec (CASSANDRA-16161) + * SASI's `max_compaction_flush_memory_in_mb` settings over 100GB revert to default of 1GB (CASSANDRA-16071) +Merged from 3.0: ++ * Fix skipping on pre-3.0 created compact storage sstables due to missing primary key liveness (CASSANDRA-16226) * Extend the exclusion of replica filtering protection to other indices instead of just SASI (CASSANDRA-16311) * Synchronize transaction logs for JBOD (CASSANDRA-16225) * Fix the counting of cells per partition (CASSANDRA-16259) diff --cc doc/source/cql/appendices.rst index 480b78e,000..456170d mode 100644,00..100644 --- a/doc/source/cql/appendices.rst +++ b/doc/source/cql/appendices.rst @@@ -1,330 -1,0 +1,333 @@@ +.. Licensed to the Apache Software Foundation (ASF) under one +.. or more contributor license agreements. See the NOTICE file +.. distributed with this work for additional information +.. regarding copyright ownership. The ASF licenses this file +.. to you under the Apache License, Version 2.0 (the +.. "License"); you may not use this file except in compliance +.. with the License. You may obtain a copy of the License at +.. +.. http://www.apache.org/licenses/LICENSE-2.0 +.. +.. Unless required by applicable law or agreed to in writing, software +.. distributed under the License is distributed on an "AS IS" BASIS, +.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +.. See the License for the specific language governing permissions and +.. limitations under the License. + +.. highlight:: cql + +Appendices +-- + +.. _appendix-A: + +Appendix A: CQL Keywords + + +CQL distinguishes between *reserved* and *non-reserved* keywords. +Reserved keywords cannot be used as identifier, they are truly reserved +for the language (but one can enclose a reserved keyword by +double-quotes to use it as an identifier). Non-reserved keywords however +only have a specific meaning in certain context but can used as +identifier otherwise. The only *raison d’être* of these non-reserved +keywords is convenience: some keyword are non-reserved when it was +always easy for the parser to decide whether they were used as keywords +or not. + +++-+ +| Keyword| Reserved? | +++=+ +| ``ADD``| yes | +++-+ +| ``AGGREGATE`` | no | +++-+ +| ``ALL``| no | +++-+ +| ``ALLOW`` | yes | +++-+ +| ``ALTER`` | yes | +++-+ +| ``AND``| yes | +++-+ +| ``APPLY`` | yes | +++-+ +| ``AS`` | no | +++-+ +| ``ASC``| yes | +++-+ +| ``ASCII`` | no | +++-+ +| ``AUTHORIZE`` | yes | +++-+ +| ``BATCH`` | yes | +++-+ +| ``BEGIN`` | yes | +++-+ +| ``BIGINT`` | no | +++-+ +| ``BLOB`` | no | +++-+ +| ``BOOLEAN``| no | +++-+ +| ``BY`` | yes | +++-+ +| ``CALLED`` | no | +++-+ +| ``CLUSTERING`` | no |
[cassandra] 01/01: Merge branch 'cassandra-3.11' into trunk
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 1596c37d03d9a6be4b72b1eee357f068ef650159 Merge: 7637acc 3e24c03 Author: Mick Semb Wever AuthorDate: Thu Jan 7 23:58:05 2021 +0100 Merge branch 'cassandra-3.11' into trunk CHANGES.txt| 5 +- doc/source/cql/appendices.rst | 9 +- .../cassandra/db/SinglePartitionReadCommand.java | 35 ++- .../miscellaneous/SSTablesIteratedTest.java| 238 - .../cql3/validation/operations/UpdateTest.java | 15 +- 5 files changed, 279 insertions(+), 23 deletions(-) diff --cc CHANGES.txt index 10e7a43,35129a2..46c1d13 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,41 -1,9 +1,44 @@@ -3.11.10 +4.0-beta5 ++ * SSLFactory should initialize SSLContext before setting protocols (CASSANDRA-16362) + * Restore sasi dependencies jflex, snowball-stemmer, and concurrent-trees, in the cassandra-all pom (CASSANDRA-16303) * Fix DecimalDeserializer#toString OOM (CASSANDRA-14925) - * SSLFactory should initialize SSLContext before setting protocols (CASSANDRA-16362) - * Rate limit validation compactions using compaction_throughput_mb_per_sec (CASSANDRA-16161) - * SASI's `max_compaction_flush_memory_in_mb` settings over 100GB revert to default of 1GB (CASSANDRA-16071) ++Merged from 3.11: + Merged from 3.0: + * Fix skipping on pre-3.0 created compact storage sstables due to missing primary key liveness (CASSANDRA-16226) + +4.0-beta4 + * DROP COMPACT STORAGE should invalidate prepared statements still using CompactTableMetadata (CASSANDRA-16361) + * Update default num_tokens to 16 and allocate_tokens_for_local_replication_factor to 3 (CASSANDRA-13701) + * Remove use of String.intern() (CASSANDRA-15810) + * Fix the missing bb position in ByteBufferAccessor.getUnsignedShort (CASSANDRA-16249) + * Make sure OOM errors are rethrown on truncation failure (CASSANDRA-16254) + * Send back client warnings when creating too many tables/keyspaces (CASSANDRA-16309) + * Add dedicated tcp user timeout for streaming connection (CASSANDRA-16143) + * Add generatetokens script for offline token allocation strategy generation (CASSANDRA-16205) + * Remove Windows scripts (CASSANDRA-16171) + * Improve checksumming and compression in protocol V5 (CASSANDRA-15299) + * Optimised repair streaming improvements (CASSANDRA-16274) + * Update jctools dependency to 3.1.0 (CASSANDRA-16255) + * 'SSLEngine closed already' exception on failed outbound connection (CASSANDRA-16277) + * Drain and/or shutdown might throw because of slow messaging service shutdown (CASSANDRA-16276) + * Upgrade JNA to 5.6.0, dropping support for <=glibc-2.6 systems (CASSANDRA-16212) + * Add saved Host IDs to TokenMetadata at startup (CASSANDRA-16246) + * Ensure that CacheMetrics.requests is picked up by the metric reporter (CASSANDRA-16228) + * Add a ratelimiter to snapshot creation and deletion (CASSANDRA-13019) + * Produce consistent tombstone for reads to avoid digest mistmatch (CASSANDRA-15369) + * Fix SSTableloader issue when restoring a table named backups (CASSANDRA-16235) + * Invalid serialized size for responses caused by increasing message time by 1ms which caused extra bytes in size calculation (CASSANDRA-16103) + * Throw BufferOverflowException from DataOutputBuffer for better visibility (CASSANDRA-16214) + * TLS connections to the storage port on a node without server encryption configured causes java.io.IOException accessing missing keystore (CASSANDRA-16144) + * Internode messaging catches OOMs and does not rethrow (CASSANDRA-15214) + * When a table attempts to clean up metrics, it was cleaning up all global table metrics (CASSANDRA-16095) + * Bring back the accepted encryption protocols list as configurable option (CASSANDRA-13325) + * DigestResolver.getData throws AssertionError since dataResponse is null (CASSANDRA-16097) + * Cannot replace_address /X because it doesn't exist in gossip (CASSANDRA-16213) + * cqlsh row_id resets on page boundaries (CASSANDRA-16160) +Merged from 3.11: + * SASI's `max_compaction_flush_memory_in_mb` settings over 100GB revert to default of 1GB (CASSANDRA-16071) +Merged from 3.0: * Extend the exclusion of replica filtering protection to other indices instead of just SASI (CASSANDRA-16311) * Synchronize transaction logs for JBOD (CASSANDRA-16225) * Fix the counting of cells per partition (CASSANDRA-16259) diff --cc src/java/org/apache/cassandra/db/SinglePartitionReadCommand.java index b7ff1b6,21b77e3..217f4f1 --- a/src/java/org/apache/cassandra/db/SinglePartitionReadCommand.java +++ b/src/java/org/apache/cassandra/db/SinglePartitionReadCommand.java @@@ -937,27 -1043,20 +937,27 @@@ public class SinglePartitionReadComman boolean removeStatic = false; if (!columns.statics.isEmpty())
[cassandra] branch cassandra-3.0 updated: Fix skipping on pre-3.0 created compact storage sstables due to missing primary key liveness
This is an automated email from the ASF dual-hosted git repository.
mck 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 f8500ee Fix skipping on pre-3.0 created compact storage sstables due
to missing primary key liveness
f8500ee is described below
commit f8500ee911343eb8826f9c44bb6db2ab780f6327
Author: Caleb Rackliffe
AuthorDate: Fri Oct 23 15:38:57 2020 -0500
Fix skipping on pre-3.0 created compact storage sstables due to missing
primary key liveness
Check primary key liveness information only if it exists, and fall back to
checking cell contents, which makes skipping possible for COMPACT STORAGE
tables after and upgrade to 3.0+
patch by Caleb Rackliffe; reviewed by Alex Petrov, Mick Semb Wever for
CASSANDRA-16226
---
CHANGES.txt| 1 +
.../cassandra/db/SinglePartitionReadCommand.java | 37 +++-
.../upgrade/CompactStorage2to3UpgradeTest.java | 6 +-
.../miscellaneous/SSTablesIteratedTest.java| 238 -
.../cql3/validation/operations/UpdateTest.java | 1 -
5 files changed, 266 insertions(+), 17 deletions(-)
diff --git a/CHANGES.txt b/CHANGES.txt
index 53883bc..54456c1 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
3.0.24:
+ * Fix skipping on pre-3.0 created compact storage sstables due to missing
primary key liveness (CASSANDRA-16226)
* Fix DecimalDeserializer#toString OOM (CASSANDRA-14925)
* Extend the exclusion of replica filtering protection to other indices
instead of just SASI (CASSANDRA-16311)
* Synchronize transaction logs for JBOD (CASSANDRA-16225)
diff --git a/src/java/org/apache/cassandra/db/SinglePartitionReadCommand.java
b/src/java/org/apache/cassandra/db/SinglePartitionReadCommand.java
index ca4e8e3..1e1953b 100644
--- a/src/java/org/apache/cassandra/db/SinglePartitionReadCommand.java
+++ b/src/java/org/apache/cassandra/db/SinglePartitionReadCommand.java
@@ -27,8 +27,6 @@ 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;
@@ -1004,14 +1002,14 @@ public class SinglePartitionReadCommand extends
ReadCommand
if (!columns.statics.isEmpty())
{
Row staticRow = searchIter.next(Clustering.STATIC_CLUSTERING);
-removeStatic = staticRow != null && canRemoveRow(staticRow,
columns.statics, sstableTimestamp);
+removeStatic = staticRow != null && isRowComplete(staticRow,
columns.statics, sstableTimestamp);
}
NavigableSet toRemove = null;
for (Clustering clustering : clusterings)
{
Row row = searchIter.next(clustering);
-if (row == null || !canRemoveRow(row, columns.regulars,
sstableTimestamp))
+if (row == null || !isRowComplete(row, columns.regulars,
sstableTimestamp))
continue;
if (toRemove == null)
@@ -1037,21 +1035,40 @@ public class SinglePartitionReadCommand extends
ReadCommand
return new ClusteringIndexNamesFilter(clusterings,
filter.isReversed());
}
-private boolean canRemoveRow(Row row, Columns requestedColumns, long
sstableTimestamp)
+/**
+ * We can stop reading row data from disk if what we've already read is
more recent than the max timestamp
+ * of the next newest SSTable that might have data for the query. We care
about 1.) the row timestamp (since
+ * every query cares if the row exists or not), 2.) the timestamps of the
requested cells, and 3.) whether or
+ * not any of the cells we've read have actual data.
+ *
+ * @param row a potentially incomplete {@link Row}
+ * @param requestedColumns the columns requested by the query
+ * @param sstableTimestamp the max timestamp of the next newest SSTable to
read
+ *
+ * @return true if the supplied {@link Row} is complete and its data more
recent than the supplied timestamp
+ */
+private boolean isRowComplete(Row row, Columns requestedColumns, long
sstableTimestamp)
{
-// We can remove a row if it has data that is more recent that the
next sstable to consider for the data that the query
-// cares about. And the data we care about is 1) the row timestamp
(since every query cares if the row exists or not)
-// and 2) the requested columns.
-if (row.primaryKeyLivenessInfo().isEmpty() ||
row.primaryKeyLivenessInfo().timestamp() <= sstableTimestamp)
+// Note that compact tables will always have an
[cassandra] branch trunk updated (7637acc -> 1596c37)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git. from 7637acc SSLFactory should initialize SSLContext before setting protocols new f8500ee Fix skipping on pre-3.0 created compact storage sstables due to missing primary key liveness new 3e24c03 Merge branch 'cassandra-3.0' into cassandra-3.11 new 1596c37 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| 5 +- doc/source/cql/appendices.rst | 9 +- .../cassandra/db/SinglePartitionReadCommand.java | 35 ++- .../miscellaneous/SSTablesIteratedTest.java| 238 - .../cql3/validation/operations/UpdateTest.java | 15 +- 5 files changed, 279 insertions(+), 23 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 (2473ee3 -> 3e24c03)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch cassandra-3.11 in repository https://gitbox.apache.org/repos/asf/cassandra.git. from 2473ee3 Merge branch 'cassandra-3.0' into cassandra-3.11 new f8500ee Fix skipping on pre-3.0 created compact storage sstables due to missing primary key liveness new 3e24c03 Merge branch 'cassandra-3.0' into cassandra-3.11 The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: CHANGES.txt| 1 + doc/source/cql/appendices.rst | 9 +- .../cassandra/db/SinglePartitionReadCommand.java | 37 +++- .../upgrade/CompactStorage2to3UpgradeTest.java | 6 +- .../miscellaneous/SSTablesIteratedTest.java| 236 - .../cql3/validation/operations/UpdateTest.java | 14 +- 6 files changed, 278 insertions(+), 25 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-builds] branch trunk updated: Fix rpm artifact building: idna-3.1 doesn't support python-2 (in centos7-image.docker)
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra-builds.git The following commit(s) were added to refs/heads/trunk by this push: new 413ca67 Fix rpm artifact building: idna-3.1 doesn't support python-2 (in centos7-image.docker) 413ca67 is described below commit 413ca677fc9b621464ef18ce8ce5e0958e2491ec Author: Mick Semb Wever AuthorDate: Thu Jan 7 23:46:59 2021 +0100 Fix rpm artifact building: idna-3.1 doesn't support python-2 (in centos7-image.docker) --- docker/centos7-image.docker | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docker/centos7-image.docker b/docker/centos7-image.docker index 7116449..ac8b1f6 100644 --- a/docker/centos7-image.docker +++ b/docker/centos7-image.docker @@ -33,7 +33,7 @@ RUN yum -y install python2-pip # install ssl enabled urllib for retrieving python packages # this will produce some ssl related warnings, which will be resolved once the package has been installed -RUN pip install urllib3[secure] +RUN pip install 'idna<3' urllib3[secure] # upgrade to modern pip version RUN pip install --upgrade pip - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16362) SSLFactory should initialize SSLContext before setting protocols
[
https://issues.apache.org/jira/browse/CASSANDRA-16362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-16362:
--
Fix Version/s: 4.0-beta5
Since Version: 4.0-beta3
Source Control Link:
https://github.com/apache/cassandra/commit/7637acc3d762047f2a478855eb4d239b4f314cd8
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> SSLFactory should initialize SSLContext before setting protocols
>
>
> Key: CASSANDRA-16362
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16362
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
>Reporter: Erik Merkle
>Assignee: Jon Meredith
>Priority: Normal
> Fix For: 4.0-beta5
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Trying to use sstableloader from the latest trunk produced the following
> Exception:
> {quote}
> Exception in thread "main" java.lang.RuntimeException: Could not create SSL
> Context.
> at
> org.apache.cassandra.tools.BulkLoader.buildSSLOptions(BulkLoader.java:261)
> at org.apache.cassandra.tools.BulkLoader.load(BulkLoader.java:64)
> at org.apache.cassandra.tools.BulkLoader.main(BulkLoader.java:49)
> Caused by: java.io.IOException: Error creating/initializing the SSL Context
> at
> org.apache.cassandra.security.SSLFactory.createSSLContext(SSLFactory.java:184)
> at
> org.apache.cassandra.tools.BulkLoader.buildSSLOptions(BulkLoader.java:257)
> ... 2 more
> Caused by: java.lang.IllegalStateException: SSLContext is not initialized
> at
> sun.security.ssl.SSLContextImpl.engineGetSocketFactory(SSLContextImpl.java:208)
> at javax.net.ssl.SSLContextSpi.getDefaultSocket(SSLContextSpi.java:158)
> at
> javax.net.ssl.SSLContextSpi.engineGetDefaultSSLParameters(SSLContextSpi.java:184)
> at javax.net.ssl.SSLContext.getDefaultSSLParameters(SSLContext.java:435)
> at
> org.apache.cassandra.security.SSLFactory.createSSLContext(SSLFactory.java:178)
> ... 3 more
> {quote}
> I believe this is because of a change to SSLFactory for CASSANDRA-13325 here:
> [https://github.com/apache/cassandra/commit/919a8964a83511d96766c3e53ba603e77bca626c#diff-0d569398cfd58566fc56bfb80c971a72afe3f392addc2df731a0b44baf29019eR177-R178]
>
> I think the solution is to call {{ctx.init()}} before trying to call
> {{ctx.getDefaultSSLParameters()}}, essentialy swapping the two lines in the
> link above.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated: SSLFactory should initialize SSLContext before setting protocols
This is an automated email from the ASF dual-hosted git repository.
dcapwell pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git
The following commit(s) were added to refs/heads/trunk by this push:
new 7637acc SSLFactory should initialize SSLContext before setting
protocols
7637acc is described below
commit 7637acc3d762047f2a478855eb4d239b4f314cd8
Author: Jon Meredith
AuthorDate: Thu Jan 7 13:10:53 2021 -0800
SSLFactory should initialize SSLContext before setting protocols
patch by Jon Meredith; reviewed by David Capwell, Dinesh Joshi for
CASSANDRA-16362
---
CHANGES.txt| 1 +
.../apache/cassandra/config/EncryptionOptions.java | 6 +-
.../org/apache/cassandra/security/SSLFactory.java | 21 +++-
.../org/apache/cassandra/tools/BulkLoader.java | 24 -
.../test/SSTableLoaderEncryptionOptionsTest.java | 106 +
.../config/DatabaseDescriptorRefTest.java | 1 +
.../cassandra/db/virtual/SettingsTableTest.java| 3 +-
.../cassandra/stress/util/JavaDriverClient.java| 22 -
8 files changed, 171 insertions(+), 13 deletions(-)
diff --git a/CHANGES.txt b/CHANGES.txt
index b593a1b..10e7a43 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,6 +1,7 @@
4.0-beta5
* Restore sasi dependencies jflex, snowball-stemmer, and concurrent-trees, in
the cassandra-all pom (CASSANDRA-16303)
* Fix DecimalDeserializer#toString OOM (CASSANDRA-14925)
+ * SSLFactory should initialize SSLContext before setting protocols
(CASSANDRA-16362)
4.0-beta4
* DROP COMPACT STORAGE should invalidate prepared statements still using
CompactTableMetadata (CASSANDRA-16361)
diff --git a/src/java/org/apache/cassandra/config/EncryptionOptions.java
b/src/java/org/apache/cassandra/config/EncryptionOptions.java
index fad6190..a534e36 100644
--- a/src/java/org/apache/cassandra/config/EncryptionOptions.java
+++ b/src/java/org/apache/cassandra/config/EncryptionOptions.java
@@ -29,6 +29,7 @@ import org.slf4j.LoggerFactory;
import org.apache.cassandra.locator.IEndpointSnitch;
import org.apache.cassandra.locator.InetAddressAndPort;
+import org.apache.cassandra.security.SSLFactory;
public class EncryptionOptions
{
@@ -236,10 +237,9 @@ public class EncryptionOptions
}
/* This list is substituted in configurations that have explicitly
specified the original "TLS" default,
- * it is not a 'default' list or 'support protocol versions' list. It is
just an attempt to preserve the
- * original intent for the user configuration
+ * by extracting it from the default "TLS" SSL Context instance
*/
-private final List TLS_PROTOCOL_SUBSTITUTION =
ImmutableList.of("TLSv1.3", "TLSv1.2", "TLSv1.1", "TLSv1");
+static private final List TLS_PROTOCOL_SUBSTITUTION =
SSLFactory.tlsInstanceProtocolSubstitution();
/**
* Combine the pre-4.0 protocol field with the accepted_protocols list,
substituting a list of
diff --git a/src/java/org/apache/cassandra/security/SSLFactory.java
b/src/java/org/apache/cassandra/security/SSLFactory.java
index 7dc0256..2f7ea75 100644
--- a/src/java/org/apache/cassandra/security/SSLFactory.java
+++ b/src/java/org/apache/cassandra/security/SSLFactory.java
@@ -161,6 +161,26 @@ public final class SSLFactory
}
}
+/** Provides the list of protocols that would have been supported if "TLS"
was selected as the
+ * protocol before the change for CASSANDRA-13325 that expects explicit
protocol versions.
+ * @return list of enabled protocol names
+ */
+public static List tlsInstanceProtocolSubstitution()
+{
+try
+{
+SSLContext ctx = SSLContext.getInstance("TLS");
+ctx.init(null, null, null);
+SSLParameters params = ctx.getSupportedSSLParameters();
+String[] protocols = params.getProtocols();
+return Arrays.asList(protocols);
+}
+catch (Exception e)
+{
+throw new RuntimeException("Error finding supported TLS
Protocols", e);
+}
+}
+
/**
* Create a JSSE {@link SSLContext}.
*/
@@ -175,7 +195,6 @@ public final class SSLFactory
try
{
SSLContext ctx = SSLContext.getInstance("TLS");
-
ctx.getDefaultSSLParameters().setProtocols(options.acceptedProtocolsArray());
ctx.init(kmf.getKeyManagers(), trustManagers, null);
return ctx;
}
diff --git a/src/java/org/apache/cassandra/tools/BulkLoader.java
b/src/java/org/apache/cassandra/tools/BulkLoader.java
index 5fd3885..c1de1ff 100644
--- a/src/java/org/apache/cassandra/tools/BulkLoader.java
+++ b/src/java/org/apache/cassandra/tools/BulkLoader.java
@@ -21,15 +21,17 @@ import java.io.IOException;
import java.net.InetSocketAddress;
import java.util.Set;
import javax.net.ssl.SSLContext;
+import javax.net.ssl.SSLEngine;
import
[cassandra] branch trunk updated: Bump copyright to 2009-2021
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/trunk by this push: new 2ef0ac6 Bump copyright to 2009-2021 2ef0ac6 is described below commit 2ef0ac6ae971073e84251d3b151df44839931cf7 Author: Mick Semb Wever AuthorDate: Thu Jan 7 22:47:22 2021 +0100 Bump copyright to 2009-2021 --- NOTICE.txt | 2 +- build.xml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/NOTICE.txt b/NOTICE.txt index d135e1e..7d215d2 100644 --- a/NOTICE.txt +++ b/NOTICE.txt @@ -1,5 +1,5 @@ Apache Cassandra -Copyright 2009-2020 The Apache Software Foundation +Copyright 2009-2021 The Apache Software Foundation This product includes software developed by The Apache Software Foundation (http://www.apache.org/). diff --git a/build.xml b/build.xml index 8e79a6f..7633111 100644 --- a/build.xml +++ b/build.xml @@ -293,7 +293,7 @@ - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16373) Deploy testing docker images to hub.docker.com/u/apache/
[ https://issues.apache.org/jira/browse/CASSANDRA-16373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17260845#comment-17260845 ] Michael Semb Wever commented on CASSANDRA-16373: Committed as [b2d679b60ac55f9bfd759fb0376a9e4e4aa3bfd4|https://github.com/apache/cassandra-builds/commit/b2d679b60ac55f9bfd759fb0376a9e4e4aa3bfd4] and [457422ac1acc3c6e13c3738410def539af64d264|https://github.com/apache/cassandra/commit/457422ac1acc3c6e13c3738410def539af64d264]. > Deploy testing docker images to hub.docker.com/u/apache/ > - > > Key: CASSANDRA-16373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16373 > Project: Cassandra > Issue Type: Task > Components: Test/dtest/java, Test/dtest/python, Test/unit >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 2.2.20, 3.0.24, 3.11.10, 4.0-beta5 > > > INFRA-21103 demonstrates PMC individuals can get access to the apache > organisation on dockerhub (and the dockerhub "cassandra" team). > We have a number of docker images (used in testing and CI) that are currently > deployed under individual user accounts on dockerhub. These can now be > deployed under https://hub.docker.com/u/apache -- 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-16373) Deploy testing docker images to hub.docker.com/u/apache/
[ https://issues.apache.org/jira/browse/CASSANDRA-16373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16373: --- Fix Version/s: 4.0-beta5 3.11.10 3.0.24 2.2.20 Source Control Link: https://github.com/apache/cassandra/commit/457422ac1acc3c6e13c3738410def539af64d264 https://github.com/apache/cassandra-builds/commit/b2d679b60ac55f9bfd759fb0376a9e4e4aa3bfd4 Resolution: Fixed Status: Resolved (was: Ready to Commit) > Deploy testing docker images to hub.docker.com/u/apache/ > - > > Key: CASSANDRA-16373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16373 > Project: Cassandra > Issue Type: Task > Components: Test/dtest/java, Test/dtest/python, Test/unit >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 2.2.20, 3.0.24, 3.11.10, 4.0-beta5 > > > INFRA-21103 demonstrates PMC individuals can get access to the apache > organisation on dockerhub (and the dockerhub "cassandra" team). > We have a number of docker images (used in testing and CI) that are currently > deployed under individual user accounts on dockerhub. These can now be > deployed under https://hub.docker.com/u/apache -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (401e933 -> a716b6d)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git. from 401e933 Restore sasi dependencies jflex, snowball-stemmer, and concurrent-trees, in the cassandra-all pom new 457422a Use ubuntu2004_* docker testing images, from the apache organisation in dockerhub new c2487f5 Merge branch 'cassandra-2.2' into cassandra-3.0 new 2473ee3 Merge branch 'cassandra-3.0' into cassandra-3.11 new a716b6d Merge branch 'cassandra-3.11' into trunk The 4 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: .circleci/config-2_1.yml | 4 +-- .circleci/config.yml | 62 ++-- .circleci/config.yml.HIGHRES | 62 ++-- .circleci/config.yml.LOWRES | 62 ++-- .circleci/config.yml.MIDRES | 62 ++-- 5 files changed, 126 insertions(+), 126 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-2.2' into cassandra-3.0
This is an automated email from the ASF dual-hosted git repository.
mck pushed a commit to branch cassandra-3.0
in repository https://gitbox.apache.org/repos/asf/cassandra.git
commit c2487f5836f3713bd04d8684cf5d0f07a3b7c70a
Merge: a2aa78d 457422a
Author: Mick Semb Wever
AuthorDate: Thu Jan 7 22:16:54 2021 +0100
Merge branch 'cassandra-2.2' into cassandra-3.0
.circleci/config-2_1.yml | 2 +-
.circleci/config.yml | 20 ++--
.circleci/config.yml.HIGHRES | 20 ++--
.circleci/config.yml.LOWRES | 20 ++--
4 files changed, 31 insertions(+), 31 deletions(-)
diff --cc .circleci/config.yml
index d49ace5,8627e96..43216a5
--- a/.circleci/config.yml
+++ b/.circleci/config.yml
@@@ -1,100 -1,8 +1,100 @@@
version: 2
jobs:
+ j8_jvm_upgrade_dtests:
+docker:
- - image:
beobal/cassandra-testing-ubuntu1910-java11-w-dependencies:20201130
++- image:
apache/cassandra-testing-ubuntu2004-java11-w-dependencies:20210105
+resource_class: medium
+working_directory: ~/
+shell: /bin/bash -eo pipefail -l
+parallelism: 1
+steps:
+- attach_workspace:
+at: /home/cassandra
+- run:
+name: Determine distributed Tests to Run
+command: |
+ # reminder: this code (along with all the steps) is independently
executed on every circle container
+ # so the goal here is to get the circleci script to return the
tests *this* container will run
+ # which we do via the `circleci` cli tool.
+
+ rm -fr ~/cassandra-dtest/upgrade_tests
+ echo "***java tests***"
+
+ # get all of our unit test filenames
+ set -eo pipefail && circleci tests glob
"$HOME/cassandra/test/distributed/**/*.java" > /tmp/all_java_unit_tests.txt
+
+ # split up the unit tests into groups based on the number of
containers we have
+ set -eo pipefail && circleci tests split --split-by=timings
--timings-type=filename --index=${CIRCLE_NODE_INDEX}
--total=${CIRCLE_NODE_TOTAL} /tmp/all_java_unit_tests.txt >
/tmp/java_tests_${CIRCLE_NODE_INDEX}.txt
+ set -eo pipefail && cat /tmp/java_tests_${CIRCLE_NODE_INDEX}.txt |
sed "s;^/home/cassandra/cassandra/test/distributed/;;g" | grep "Test\.java$" |
grep upgrade > /tmp/java_tests_${CIRCLE_NODE_INDEX}_final.txt
+ echo "** /tmp/java_tests_${CIRCLE_NODE_INDEX}_final.txt"
+ cat /tmp/java_tests_${CIRCLE_NODE_INDEX}_final.txt
+no_output_timeout: 15m
+- run:
+name: Log Environment Information
+command: |
+ echo '*** id ***'
+ id
+ echo '*** cat /proc/cpuinfo ***'
+ cat /proc/cpuinfo
+ echo '*** free -m ***'
+ free -m
+ echo '*** df -m ***'
+ df -m
+ echo '*** ifconfig -a ***'
+ ifconfig -a
+ echo '*** uname -a ***'
+ uname -a
+ echo '*** mount ***'
+ mount
+ echo '*** env ***'
+ env
+ echo '*** java ***'
+ which java
+ java -version
+- run:
+name: Run Unit Tests (testclasslist)
+command: |
+ set -x
+ export PATH=$JAVA_HOME/bin:$PATH
+ time mv ~/cassandra /tmp
+ cd /tmp/cassandra
+ if [ -d ~/dtest_jars ]; then
+cp ~/dtest_jars/dtest* /tmp/cassandra/build/
+ fi
+ test_timeout=$(grep 'name="test.distributed.timeout"' build.xml |
awk -F'"' '{print $4}' || true)
+ if [ -z "$test_timeout" ]; then
+test_timeout=$(grep 'name="test.timeout"' build.xml | awk -F'"'
'{print $4}')
+ fi
+ ant testclasslist -Dtest.timeout="$test_timeout"
-Dtest.classlistfile=/tmp/java_tests_${CIRCLE_NODE_INDEX}_final.txt
-Dtest.classlistprefix=distributed
+no_output_timeout: 15m
+- store_test_results:
+path: /tmp/cassandra/build/test/output/
+- store_artifacts:
+path: /tmp/cassandra/build/test/output
+destination: junitxml
+- store_artifacts:
+path: /tmp/cassandra/build/test/logs
+destination: logs
+environment:
+- JAVA8_HOME: /usr/lib/jvm/java-8-openjdk-amd64
+- ANT_HOME: /usr/share/ant
+- LANG: en_US.UTF-8
+- KEEP_TEST_DIR: true
+- DEFAULT_DIR: /home/cassandra/cassandra-dtest
+- PYTHONIOENCODING: utf-8
+- PYTHONUNBUFFERED: true
+- CASS_DRIVER_NO_EXTENSIONS: true
+- CASS_DRIVER_NO_CYTHON: true
+- CASSANDRA_SKIP_SYNC: true
+- DTEST_REPO: git://github.com/apache/cassandra-dtest.git
+- DTEST_BRANCH: trunk
+- CCM_MAX_HEAP_SIZE: 1024M
+- CCM_HEAP_NEWSIZE: 256M
+- JAVA_HOME: /usr/lib/jvm/java-8-openjdk-amd64
+- JDK_HOME: /usr/lib/jvm/java-8-openjdk-amd64
build:
docker:
- - image:
beobal/cassandra-testing-ubuntu1910-java11-w-dependencies:20201130
+ - image:
[cassandra] 01/01: Merge branch 'cassandra-3.0' into cassandra-3.11
This is an automated email from the ASF dual-hosted git repository.
mck pushed a commit to branch cassandra-3.11
in repository https://gitbox.apache.org/repos/asf/cassandra.git
commit 2473ee323d1aeb323ccd1c9cff2ab0855d615e0f
Merge: 3ec9054 c2487f5
Author: Mick Semb Wever
AuthorDate: Thu Jan 7 22:17:57 2021 +0100
Merge branch 'cassandra-3.0' into cassandra-3.11
.circleci/config-2_1.yml | 2 +-
.circleci/config.yml | 22 +++---
.circleci/config.yml.HIGHRES | 22 +++---
.circleci/config.yml.LOWRES | 22 +++---
4 files changed, 34 insertions(+), 34 deletions(-)
diff --cc .circleci/config.yml
index 027ccb8,43216a5..385de52
--- a/.circleci/config.yml
+++ b/.circleci/config.yml
@@@ -330,55 -330,9 +330,55 @@@ jobs
- CCM_HEAP_NEWSIZE: 256M
- JAVA_HOME: /usr/lib/jvm/java-8-openjdk-amd64
- JDK_HOME: /usr/lib/jvm/java-8-openjdk-amd64
+ utests_stress:
+docker:
- - image:
beobal/cassandra-testing-ubuntu1910-java11-w-dependencies:20201130
++- image:
apache/cassandra-testing-ubuntu2004-java11-w-dependencies:20210105
+resource_class: medium
+working_directory: ~/
+shell: /bin/bash -eo pipefail -l
+parallelism: 1
+steps:
+- attach_workspace:
+at: /home/cassandra
+- run:
+name: Run Unit Tests (stress-test)
+command: |
+ export PATH=$JAVA_HOME/bin:$PATH
+ time mv ~/cassandra /tmp
+ cd /tmp/cassandra
+ if [ -d ~/dtest_jars ]; then
+cp ~/dtest_jars/dtest* /tmp/cassandra/build/
+ fi
+ ant stress-test
-Dtest.classlistfile=/tmp/java_tests_${CIRCLE_NODE_INDEX}_final.txt
-Dtest.classlistprefix=unit
+no_output_timeout: 15m
+- store_test_results:
+path: /tmp/cassandra/build/test/output/
+- store_artifacts:
+path: /tmp/cassandra/build/test/output
+destination: junitxml
+- store_artifacts:
+path: /tmp/cassandra/build/test/logs
+destination: logs
+environment:
+- JAVA8_HOME: /usr/lib/jvm/java-8-openjdk-amd64
+- ANT_HOME: /usr/share/ant
+- LANG: en_US.UTF-8
+- KEEP_TEST_DIR: true
+- DEFAULT_DIR: /home/cassandra/cassandra-dtest
+- PYTHONIOENCODING: utf-8
+- PYTHONUNBUFFERED: true
+- CASS_DRIVER_NO_EXTENSIONS: true
+- CASS_DRIVER_NO_CYTHON: true
+- CASSANDRA_SKIP_SYNC: true
+- DTEST_REPO: git://github.com/apache/cassandra-dtest.git
+- DTEST_BRANCH: trunk
+- CCM_MAX_HEAP_SIZE: 1024M
+- CCM_HEAP_NEWSIZE: 256M
+- JAVA_HOME: /usr/lib/jvm/java-8-openjdk-amd64
+- JDK_HOME: /usr/lib/jvm/java-8-openjdk-amd64
j8_unit_tests:
docker:
- - image:
beobal/cassandra-testing-ubuntu1910-java11-w-dependencies:20201130
+ - image:
apache/cassandra-testing-ubuntu2004-java11-w-dependencies:20210105
resource_class: medium
working_directory: ~/
shell: /bin/bash -eo pipefail -l
diff --cc .circleci/config.yml.HIGHRES
index cf18b13,e272801..c830556
--- a/.circleci/config.yml.HIGHRES
+++ b/.circleci/config.yml.HIGHRES
@@@ -330,55 -330,9 +330,55 @@@ jobs
- CCM_HEAP_NEWSIZE: 512M
- JAVA_HOME: /usr/lib/jvm/java-8-openjdk-amd64
- JDK_HOME: /usr/lib/jvm/java-8-openjdk-amd64
+ utests_stress:
+docker:
- - image:
beobal/cassandra-testing-ubuntu1910-java11-w-dependencies:20201130
++- image:
apache/cassandra-testing-ubuntu2004-java11-w-dependencies:20210105
+resource_class: xlarge
+working_directory: ~/
+shell: /bin/bash -eo pipefail -l
+parallelism: 1
+steps:
+- attach_workspace:
+at: /home/cassandra
+- run:
+name: Run Unit Tests (stress-test)
+command: |
+ export PATH=$JAVA_HOME/bin:$PATH
+ time mv ~/cassandra /tmp
+ cd /tmp/cassandra
+ if [ -d ~/dtest_jars ]; then
+cp ~/dtest_jars/dtest* /tmp/cassandra/build/
+ fi
+ ant stress-test
-Dtest.classlistfile=/tmp/java_tests_${CIRCLE_NODE_INDEX}_final.txt
-Dtest.classlistprefix=unit
+no_output_timeout: 15m
+- store_test_results:
+path: /tmp/cassandra/build/test/output/
+- store_artifacts:
+path: /tmp/cassandra/build/test/output
+destination: junitxml
+- store_artifacts:
+path: /tmp/cassandra/build/test/logs
+destination: logs
+environment:
+- JAVA8_HOME: /usr/lib/jvm/java-8-openjdk-amd64
+- ANT_HOME: /usr/share/ant
+- LANG: en_US.UTF-8
+- KEEP_TEST_DIR: true
+- DEFAULT_DIR: /home/cassandra/cassandra-dtest
+- PYTHONIOENCODING: utf-8
+- PYTHONUNBUFFERED: true
+- CASS_DRIVER_NO_EXTENSIONS: true
+- CASS_DRIVER_NO_CYTHON: true
+- CASSANDRA_SKIP_SYNC: true
+- DTEST_REPO: git://github.com/apache/cassandra-dtest.git
+- DTEST_BRANCH: trunk
+- CCM_MAX_HEAP_SIZE: 2048M
+- CCM_HEAP_NEWSIZE: 512M
+-
[cassandra] branch cassandra-3.11 updated (3ec9054 -> 2473ee3)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch cassandra-3.11 in repository https://gitbox.apache.org/repos/asf/cassandra.git. from 3ec9054 Merge branch 'cassandra-3.0' into cassandra-3.11 new 457422a Use ubuntu2004_* docker testing images, from the apache organisation in dockerhub new c2487f5 Merge branch 'cassandra-2.2' into cassandra-3.0 new 2473ee3 Merge branch 'cassandra-3.0' into cassandra-3.11 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: .circleci/config-2_1.yml | 2 +- .circleci/config.yml | 22 +++--- .circleci/config.yml.HIGHRES | 22 +++--- .circleci/config.yml.LOWRES | 22 +++--- 4 files changed, 34 insertions(+), 34 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-3.0 updated (a2aa78d -> c2487f5)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch cassandra-3.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git. from a2aa78d Avoid decimal-serializer.toString() creating huge string new 457422a Use ubuntu2004_* docker testing images, from the apache organisation in dockerhub new c2487f5 Merge branch 'cassandra-2.2' into cassandra-3.0 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: .circleci/config-2_1.yml | 2 +- .circleci/config.yml | 20 ++-- .circleci/config.yml.HIGHRES | 20 ++-- .circleci/config.yml.LOWRES | 20 ++-- 4 files changed, 31 insertions(+), 31 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-2.2 updated: Use ubuntu2004_* docker testing images, from the apache organisation in dockerhub
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch cassandra-2.2 in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/cassandra-2.2 by this push: new 457422a Use ubuntu2004_* docker testing images, from the apache organisation in dockerhub 457422a is described below commit 457422ac1acc3c6e13c3738410def539af64d264 Author: Mick Semb Wever AuthorDate: Wed Jan 6 09:19:01 2021 +0100 Use ubuntu2004_* docker testing images, from the apache organisation in dockerhub patch by Mick Semb Wever; reviewed by Sam Tunnicliffe for CASSANDRA-16373 --- .circleci/config-2_1.yml | 2 +- .circleci/config.yml | 16 .circleci/config.yml.HIGHRES | 16 .circleci/config.yml.LOWRES | 16 4 files changed, 25 insertions(+), 25 deletions(-) diff --git a/.circleci/config-2_1.yml b/.circleci/config-2_1.yml index 44bf4ca..3826575 100644 --- a/.circleci/config-2_1.yml +++ b/.circleci/config-2_1.yml @@ -102,7 +102,7 @@ executors: type: string default: medium docker: - - image: beobal/cassandra-testing-ubuntu1910-java11-w-dependencies:20201130 + - image: apache/cassandra-testing-ubuntu2004-java11-w-dependencies:20210105 resource_class: << parameters.exec_resource_class >> working_directory: ~/ shell: /bin/bash -eo pipefail -l diff --git a/.circleci/config.yml b/.circleci/config.yml index 862d4a1..8627e96 100644 --- a/.circleci/config.yml +++ b/.circleci/config.yml @@ -2,7 +2,7 @@ version: 2 jobs: build: docker: -- image: beobal/cassandra-testing-ubuntu1910-java11-w-dependencies:20201130 +- image: apache/cassandra-testing-ubuntu2004-java11-w-dependencies:20210105 resource_class: medium working_directory: ~/ shell: /bin/bash -eo pipefail -l @@ -77,7 +77,7 @@ jobs: - JDK_HOME: /usr/lib/jvm/java-8-openjdk-amd64 j8_unit_tests: docker: -- image: beobal/cassandra-testing-ubuntu1910-java11-w-dependencies:20201130 +- image: apache/cassandra-testing-ubuntu2004-java11-w-dependencies:20210105 resource_class: medium working_directory: ~/ shell: /bin/bash -eo pipefail -l @@ -166,7 +166,7 @@ jobs: - JDK_HOME: /usr/lib/jvm/java-8-openjdk-amd64 j8_jvm_dtests: docker: -- image: beobal/cassandra-testing-ubuntu1910-java11-w-dependencies:20201130 +- image: apache/cassandra-testing-ubuntu2004-java11-w-dependencies:20210105 resource_class: medium working_directory: ~/ shell: /bin/bash -eo pipefail -l @@ -255,7 +255,7 @@ jobs: - JDK_HOME: /usr/lib/jvm/java-8-openjdk-amd64 utests_long: docker: -- image: beobal/cassandra-testing-ubuntu1910-java11-w-dependencies:20201130 +- image: apache/cassandra-testing-ubuntu2004-java11-w-dependencies:20210105 resource_class: medium working_directory: ~/ shell: /bin/bash -eo pipefail -l @@ -298,7 +298,7 @@ jobs: - JDK_HOME: /usr/lib/jvm/java-8-openjdk-amd64 utests_compression: docker: -- image: beobal/cassandra-testing-ubuntu1910-java11-w-dependencies:20201130 +- image: apache/cassandra-testing-ubuntu2004-java11-w-dependencies:20210105 resource_class: medium working_directory: ~/ shell: /bin/bash -eo pipefail -l @@ -387,7 +387,7 @@ jobs: - JDK_HOME: /usr/lib/jvm/java-8-openjdk-amd64 j8_dtests-with-vnodes: docker: -- image: beobal/cassandra-testing-ubuntu1910-java11-w-dependencies:20201130 +- image: apache/cassandra-testing-ubuntu2004-java11-w-dependencies:20210105 resource_class: medium working_directory: ~/ shell: /bin/bash -eo pipefail -l @@ -445,7 +445,7 @@ jobs: - JDK_HOME: /usr/lib/jvm/java-8-openjdk-amd64 j8_dtests-no-vnodes: docker: -- image: beobal/cassandra-testing-ubuntu1910-java11-w-dependencies:20201130 +- image: apache/cassandra-testing-ubuntu2004-java11-w-dependencies:20210105 resource_class: medium working_directory: ~/ shell: /bin/bash -eo pipefail -l @@ -503,7 +503,7 @@ jobs: - JDK_HOME: /usr/lib/jvm/java-8-openjdk-amd64 j8_upgradetests-no-vnodes: docker: -- image: beobal/cassandra-testing-ubuntu1910-java11-w-dependencies:20201130 +- image: apache/cassandra-testing-ubuntu2004-java11-w-dependencies:20210105 resource_class: medium working_directory: ~/ shell: /bin/bash -eo pipefail -l diff --git a/.circleci/config.yml.HIGHRES b/.circleci/config.yml.HIGHRES index 6e5a50b..c825bf1 100644 --- a/.circleci/config.yml.HIGHRES +++ b/.circleci/config.yml.HIGHRES @@ -2,7 +2,7 @@ version: 2 jobs: build: docker: -- image: beobal/cassandra-testing-ubuntu1910-java11-w-dependencies:20201130 +- image: apache/cassandra-testing-ubuntu2004-java11-w-dependencies:20210105 resource_class: medium working_directory: ~/ shell: /bin/bash -eo pipefail -l @@ -77,7 +77,7 @@ jobs: -
[jira] [Updated] (CASSANDRA-16373) Deploy testing docker images to hub.docker.com/u/apache/
[ https://issues.apache.org/jira/browse/CASSANDRA-16373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16373: --- Status: Ready to Commit (was: Changes Suggested) > Deploy testing docker images to hub.docker.com/u/apache/ > - > > Key: CASSANDRA-16373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16373 > Project: Cassandra > Issue Type: Task > Components: Test/dtest/java, Test/dtest/python, Test/unit >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > > INFRA-21103 demonstrates PMC individuals can get access to the apache > organisation on dockerhub (and the dockerhub "cassandra" team). > We have a number of docker images (used in testing and CI) that are currently > deployed under individual user accounts on dockerhub. These can now be > deployed under https://hub.docker.com/u/apache -- 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-16362) SSLFactory should initialize SSLContext before setting protocols
[
https://issues.apache.org/jira/browse/CASSANDRA-16362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17260832#comment-17260832
]
David Capwell commented on CASSANDRA-16362:
---
Starting commit
CI Results (pending):
||Branch||Source||Circle CI||Jenkins||
|trunk|[branch|https://github.com/dcapwell/cassandra/tree/commit_remote_branch/CASSANDRA-16362-trunk-87BA7E88-24F7-4F84-A26B-3A7B781C9B57]|[build|https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-16362-trunk-87BA7E88-24F7-4F84-A26B-3A7B781C9B57]|[build|unknown]|
> SSLFactory should initialize SSLContext before setting protocols
>
>
> Key: CASSANDRA-16362
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16362
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
>Reporter: Erik Merkle
>Assignee: Jon Meredith
>Priority: Normal
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Trying to use sstableloader from the latest trunk produced the following
> Exception:
> {quote}
> Exception in thread "main" java.lang.RuntimeException: Could not create SSL
> Context.
> at
> org.apache.cassandra.tools.BulkLoader.buildSSLOptions(BulkLoader.java:261)
> at org.apache.cassandra.tools.BulkLoader.load(BulkLoader.java:64)
> at org.apache.cassandra.tools.BulkLoader.main(BulkLoader.java:49)
> Caused by: java.io.IOException: Error creating/initializing the SSL Context
> at
> org.apache.cassandra.security.SSLFactory.createSSLContext(SSLFactory.java:184)
> at
> org.apache.cassandra.tools.BulkLoader.buildSSLOptions(BulkLoader.java:257)
> ... 2 more
> Caused by: java.lang.IllegalStateException: SSLContext is not initialized
> at
> sun.security.ssl.SSLContextImpl.engineGetSocketFactory(SSLContextImpl.java:208)
> at javax.net.ssl.SSLContextSpi.getDefaultSocket(SSLContextSpi.java:158)
> at
> javax.net.ssl.SSLContextSpi.engineGetDefaultSSLParameters(SSLContextSpi.java:184)
> at javax.net.ssl.SSLContext.getDefaultSSLParameters(SSLContext.java:435)
> at
> org.apache.cassandra.security.SSLFactory.createSSLContext(SSLFactory.java:178)
> ... 3 more
> {quote}
> I believe this is because of a change to SSLFactory for CASSANDRA-13325 here:
> [https://github.com/apache/cassandra/commit/919a8964a83511d96766c3e53ba603e77bca626c#diff-0d569398cfd58566fc56bfb80c971a72afe3f392addc2df731a0b44baf29019eR177-R178]
>
> I think the solution is to call {{ctx.init()}} before trying to call
> {{ctx.getDefaultSSLParameters()}}, essentialy swapping the two lines in the
> link above.
--
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-builds] branch trunk updated: Add ubuntu2004_* testing docker files, and deploy them to the apache organisation in dockerhub
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra-builds.git The following commit(s) were added to refs/heads/trunk by this push: new b2d679b Add ubuntu2004_* testing docker files, and deploy them to the apache organisation in dockerhub b2d679b is described below commit b2d679b60ac55f9bfd759fb0376a9e4e4aa3bfd4 Author: Mick Semb Wever AuthorDate: Tue Jan 5 22:16:16 2021 +0100 Add ubuntu2004_* testing docker files, and deploy them to the apache organisation in dockerhub Also remove ubuntu18* docker files patch by Mick Semb Wever; reviewed by Sam Tunnicliffe for CASSANDRA-16373 --- docker/testing/README.md | 14 +-- .../testing/ubuntu1810_j11_w_dependencies.docker | 37 --- docker/testing/ubuntu18_j11.docker | 112 - docker/testing/ubuntu1910_j11.docker | 3 +- .../testing/ubuntu1910_j11_w_dependencies.docker | 4 +- ...ubuntu1810_j11.docker => ubuntu2004_j11.docker} | 37 +-- ...docker => ubuntu2004_j11_w_dependencies.docker} | 6 +- jenkins-dsl/cassandra_job_dsl_seed.groovy | 2 +- 8 files changed, 44 insertions(+), 171 deletions(-) diff --git a/docker/testing/README.md b/docker/testing/README.md index 8864391..195f95e 100644 --- a/docker/testing/README.md +++ b/docker/testing/README.md @@ -1,6 +1,6 @@ # Docker CI Testing -Docker files in this directory are used to build images used by CircleCI. These are directly referenced in the `circle.yml` after publishing to dockerhub. There are two types of images: +Docker files in this directory are used to build images used by ci-cassandra.apache.org and CircleCI. These are directly referenced in the `cassandra_job_dsl_seed.groovy` and `.circleci/config*.yml` files, after publishing to dockerhub. There are two types of images: * Base image for Linux distribution to use for testing (e.g. `ubuntu1910_j11.docker`) * Caching image that contains git sources, maven and ccm dependencies @@ -11,11 +11,11 @@ Build images from the parent directory using the following commands. Change tag Base image: -`docker build -t nastra/cassandra-testing-ubuntu1910-java11:20200603 -t nastra/cassandra-testing-ubuntu1910-java11:latest -f ubuntu1910_j11.docker .` +`docker build -t apache/cassandra-testing-ubuntu2004-java11:$(date +"%Y%m%d") -t apache/cassandra-testing-ubuntu2004-java11:latest -f ubuntu2004_j11.docker .` Caching image: -`docker build --no-cache -t nastra/cassandra-testing-ubuntu1910-java11-w-dependencies:20200603 -t nastra/cassandra-testing-ubuntu1910-java11-w-dependencies:latest -f ubuntu1910_j11_w_dependencies.docker .` +`docker build --no-cache -t apache/cassandra-testing-ubuntu2004-java11-w-dependencies:$(date +"%Y%m%d") -t apache/cassandra-testing-ubuntu2004-java11-w-dependencies:latest -f ubuntu2004_j11_w_dependencies.docker .` Please make sure to always tag also by date, so we can go back to that version in case anything breaks after the next update! @@ -26,10 +26,12 @@ We are using Docker Hub for storing published images. See [Quick Start Guide](ht Push both image references: ``` -docker push nastra/cassandra-testing-ubuntu1910-java11-w-dependencies:20200603 -docker push nastra/cassandra-testing-ubuntu1910-java11-w-dependencies:latest +docker push apache/cassandra-testing-ubuntu2004-java11:$(date +"%Y%m%d") +docker push apache/cassandra-testing-ubuntu2004-java11:latest +docker push apache/cassandra-testing-ubuntu2004-java11-w-dependencies:$(date +"%Y%m%d") +docker push apache/cassandra-testing-ubuntu2004-java11-w-dependencies:latest ``` ## Updating circleci.yml -Check if the correct image is used in `.circleci/config-2_1.yml` by looking for the `- image:` value. It should either be set to the date dervived tag created above, or `:latest`. +Check if the correct image is used in `cassandra_job_dsl_seed.groovy` and `.circleci/config*.yml`. It should either be set to the date dervived tag created above, or `:latest`. diff --git a/docker/testing/ubuntu1810_j11_w_dependencies.docker b/docker/testing/ubuntu1810_j11_w_dependencies.docker deleted file mode 100644 index 8f25165..000 --- a/docker/testing/ubuntu1810_j11_w_dependencies.docker +++ /dev/null @@ -1,37 +0,0 @@ -# Licensed under the Apache License, Version 2.0 (the "License"); -# you may not use this file except in compliance with the License. -# You may obtain a copy of the License at -# -# http://www.apache.org/licenses/LICENSE-2.0 -# -# Unless required by applicable law or agreed to in writing, software -# distributed under the License is distributed on an "AS IS" BASIS, -# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -# See the License for the specific language governing permissions and -# limitations under the License. - -# base things off the testing image
[jira] [Comment Edited] (CASSANDRA-16373) Deploy testing docker images to hub.docker.com/u/apache/
[ https://issues.apache.org/jira/browse/CASSANDRA-16373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17260821#comment-17260821 ] Michael Semb Wever edited comment on CASSANDRA-16373 at 1/7/21, 9:04 PM: - CI - https://ci-cassandra.apache.org/job/Cassandra-devbranch-dtest/302/ - https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/5/workflows/30cea1c3-2e17-4ff0-9a72-434d02ef2f75/jobs/96 - https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/7/workflows/aa4627a1-1524-42cd-a236-f6f57f390ec2 - https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/7/workflows/ae39eca8-fa99-4d25-92ed-70c3499c58a7 was (Author: michaelsembwever): CI - https://ci-cassandra.apache.org/job/Cassandra-devbranch-dtest/302/ - > Deploy testing docker images to hub.docker.com/u/apache/ > - > > Key: CASSANDRA-16373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16373 > Project: Cassandra > Issue Type: Task > Components: Test/dtest/java, Test/dtest/python, Test/unit >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > > INFRA-21103 demonstrates PMC individuals can get access to the apache > organisation on dockerhub (and the dockerhub "cassandra" team). > We have a number of docker images (used in testing and CI) that are currently > deployed under individual user accounts on dockerhub. These can now be > deployed under https://hub.docker.com/u/apache -- 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-16373) Deploy testing docker images to hub.docker.com/u/apache/
[ https://issues.apache.org/jira/browse/CASSANDRA-16373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17260779#comment-17260779 ] Michael Semb Wever edited comment on CASSANDRA-16373 at 1/7/21, 9:02 PM: - bq. The in-tree patches seem correct, but before merging they'll need updating with the correct tags after the images are actually published. I've stuck with the `20210105` tag (and the images that were built that day). (Trunk patch has been corrected.) Those images are… - apache/cassandra-testing-ubuntu2004-java11:20210105 https://hub.docker.com/layers/132406965/apache/cassandra-testing-ubuntu2004-java11/20210105/images/sha256-1065f707aa2dbf941d71f879aac285f0df9042ff191b4554c7f2c2890b3f5e17?context=explore - apache/cassandra-testing-ubuntu2004-java11-w-dependencies:20210105 https://hub.docker.com/layers/apache/cassandra-testing-ubuntu2004-java11-w-dependencies/20210105/images/sha256-fc79253ccb0f1cd85386dcbf893d7c94ececd8c9c5700d22683d6b827c2044c3?context=explore was (Author: michaelsembwever): bq. The in-tree patches seem correct, but before merging they'll need updating with the correct tags after the images are actually published. I've stuck with the `20210105` tag (and the images that were built that day). - apache/cassandra-testing-ubuntu2004-java11:20210105 https://hub.docker.com/layers/132406965/apache/cassandra-testing-ubuntu2004-java11/20210105/images/sha256-1065f707aa2dbf941d71f879aac285f0df9042ff191b4554c7f2c2890b3f5e17?context=explore - apache/cassandra-testing-ubuntu2004-java11-w-dependencies:20210105 https://hub.docker.com/layers/apache/cassandra-testing-ubuntu2004-java11-w-dependencies/20210105/images/sha256-fc79253ccb0f1cd85386dcbf893d7c94ececd8c9c5700d22683d6b827c2044c3?context=explore > Deploy testing docker images to hub.docker.com/u/apache/ > - > > Key: CASSANDRA-16373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16373 > Project: Cassandra > Issue Type: Task > Components: Test/dtest/java, Test/dtest/python, Test/unit >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > > INFRA-21103 demonstrates PMC individuals can get access to the apache > organisation on dockerhub (and the dockerhub "cassandra" team). > We have a number of docker images (used in testing and CI) that are currently > deployed under individual user accounts on dockerhub. These can now be > deployed under https://hub.docker.com/u/apache -- 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-16373) Deploy testing docker images to hub.docker.com/u/apache/
[ https://issues.apache.org/jira/browse/CASSANDRA-16373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17260821#comment-17260821 ] Michael Semb Wever commented on CASSANDRA-16373: CI - https://ci-cassandra.apache.org/job/Cassandra-devbranch-dtest/302/ - > Deploy testing docker images to hub.docker.com/u/apache/ > - > > Key: CASSANDRA-16373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16373 > Project: Cassandra > Issue Type: Task > Components: Test/dtest/java, Test/dtest/python, Test/unit >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > > INFRA-21103 demonstrates PMC individuals can get access to the apache > organisation on dockerhub (and the dockerhub "cassandra" team). > We have a number of docker images (used in testing and CI) that are currently > deployed under individual user accounts on dockerhub. These can now be > deployed under https://hub.docker.com/u/apache -- 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-16373) Deploy testing docker images to hub.docker.com/u/apache/
[ https://issues.apache.org/jira/browse/CASSANDRA-16373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17260779#comment-17260779 ] Michael Semb Wever commented on CASSANDRA-16373: bq. The in-tree patches seem correct, but before merging they'll need updating with the correct tags after the images are actually published. I've stuck with the `20210105` tag (and the images that were built that day). - apache/cassandra-testing-ubuntu2004-java11:20210105 https://hub.docker.com/layers/132406965/apache/cassandra-testing-ubuntu2004-java11/20210105/images/sha256-1065f707aa2dbf941d71f879aac285f0df9042ff191b4554c7f2c2890b3f5e17?context=explore - apache/cassandra-testing-ubuntu2004-java11-w-dependencies:20210105 https://hub.docker.com/layers/apache/cassandra-testing-ubuntu2004-java11-w-dependencies/20210105/images/sha256-fc79253ccb0f1cd85386dcbf893d7c94ececd8c9c5700d22683d6b827c2044c3?context=explore > Deploy testing docker images to hub.docker.com/u/apache/ > - > > Key: CASSANDRA-16373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16373 > Project: Cassandra > Issue Type: Task > Components: Test/dtest/java, Test/dtest/python, Test/unit >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > > INFRA-21103 demonstrates PMC individuals can get access to the apache > organisation on dockerhub (and the dockerhub "cassandra" team). > We have a number of docker images (used in testing and CI) that are currently > deployed under individual user accounts on dockerhub. These can now be > deployed under https://hub.docker.com/u/apache -- 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-15962) Digest for some queries is different depending whether the data are retrieved from sstable or memtable
[
https://issues.apache.org/jira/browse/CASSANDRA-15962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-15962:
---
Reviewers: Benjamin Lerer, Sylvain Lebresne, Benjamin Lerer (was: Benjamin
Lerer, Sylvain Lebresne)
Benjamin Lerer, Sylvain Lebresne, Benjamin Lerer (was: Benjamin
Lerer, Sylvain Lebresne)
Status: Review In Progress (was: Patch Available)
> Digest for some queries is different depending whether the data are retrieved
> from sstable or memtable
> --
>
> Key: CASSANDRA-15962
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15962
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Coordination
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 3.11.x, 4.0-beta
>
> Attachments: DigestTest.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Not sure into which category should I assign this ticket.
>
> Basically when reading using certain column filters, the digest is different
> depending whether we read from sstable and memtable. This happens on
> {{trunk}} and {{cassandra-3.11}} branches. However it works properly on
> {{cassandra-3.0}} branch.
>
> I'm attaching a simple test for trunk to demonstrate what I mean.
>
> Please verify my test and my conclusions
>
--
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-16353) Fix client push notifications in protocol v5
[ https://issues.apache.org/jira/browse/CASSANDRA-16353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-16353: --- Reviewers: Benjamin Lerer > Fix client push notifications in protocol v5 > > > Key: CASSANDRA-16353 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16353 > Project: Cassandra > Issue Type: Bug > Components: Messaging/Client >Reporter: Sam Tunnicliffe >Assignee: Sam Tunnicliffe >Priority: Normal > Labels: protocolv5 > Fix For: 4.0-beta > > > The changes to native protocol v5 in CASSANDRA-15299 broke the delivery of > push notifications from server to client. This wasn't caught earlier as there > weren't any unit or dtests which would exercise client notifications in a > beta protocol version. Working on CASSANDRA-14973 to bring v5 out of beta > exposed the regression. -- 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
