[jira] [Commented] (CASSANDRA-16500) Missing validation in AbstractType.writeValue():
[
https://issues.apache.org/jira/browse/CASSANDRA-16500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17309176#comment-17309176
]
Berenguer Blasi commented on CASSANDRA-16500:
-
LOL! thx...
> Missing validation in AbstractType.writeValue():
>
>
> Key: CASSANDRA-16500
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16500
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Other
>Reporter: Benjamin Lerer
>Assignee: Alexandre Dutra
>Priority: Normal
> Fix For: 4.0-beta5, 4.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Some validation checks present in {{AbstractType.writeValue()}} in
> {{cassandra-3.11}} are not there in {{trunk}}.
> In 3.11 the checks used assertion. It would make sense to use
> {{IOExceptions}} instead as used in {{AbstractType.readValue()}}.
--
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-16532) Fix flaky testSkipScrubCorruptedCounterRowWithTool
[ https://issues.apache.org/jira/browse/CASSANDRA-16532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17309174#comment-17309174 ] Berenguer Blasi commented on CASSANDRA-16532: - Aha, good catch. So we just had the same problem in the other test cases as well: cross-talk at ks.cf level. I am +1 to merge everything in here specially after the 1000 runs! > Fix flaky testSkipScrubCorruptedCounterRowWithTool > -- > > Key: CASSANDRA-16532 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16532 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-rc > > Time Spent: 1.5h > Remaining Estimate: 0h > > Fix flaky > [testSkipScrubCorruptedCounterRowWithTool|https://ci-cassandra.apache.org/job/Cassandra-trunk/365/testReport/junit/org.apache.cassandra.db/ScrubTest/testSkipScrubCorruptedCounterRowWithTool_compression/] -- 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-16538) Cannot run restore for a list of Cassandra nodes
[
https://issues.apache.org/jira/browse/CASSANDRA-16538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17309131#comment-17309131
]
Yolanda Tang commented on CASSANDRA-16538:
--
Hi [~brandon.williams],
Sorry to raise the issue here, please kindly close it.
I've raised this on the Github issue page.
Thanks for replying anyway.
> Cannot run restore for a list of Cassandra nodes
>
>
> Key: CASSANDRA-16538
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16538
> Project: Cassandra
> Issue Type: Bug
>Reporter: Yolanda Tang
>Priority: Normal
>
> Hi,
>
> When switching to use Cassandra medus to fulfill our work for node data
> restore, we encountered some issues.
> When using pssh remotely we are getting timeout issue, when trying the
> command on one node of Cassandra, we get
>
> {code:java}
> pssh -H medusa -vvv restore-node --in-place --no-verify --backup-name
> 2021031803 --temp-dir /tmp/medusa-job-bd8a39ca-a5ea-4a3a-820f-0fa6ddc5130a
> [1] 06:52:08 [FAILURE] sha8392 Timed out, Killed by signal 9
> When further looking into the timeout issue, we get logs as
> [2021-03-25 02:23:50,113] DEBUG: https://s3.cn-north-1.amazonaws.com.cn:443
> "GET /XX/XX/10.44.XX.XX/2021031803/meta/schema.cql?Version=2006-03-01
> HTTP/1.1" 200 24005[2021-03-25 02:23:50,114] DEBUG: [Storage] Getting object
> sre_dev_cass_sha/10.44.79.15/2021031803/meta/tokenmap.json
> [2021-03-25 02:23:50,151] DEBUG: https://s3.cn-north-1.amazonaws.com.cn:443
> "HEAD /XX HTTP/1.1" 200 0[2021-03-25 02:23:50,201] DEBUG:
> https://s3.cn-north-1.amazonaws.com.cn:443 "HEAD
> /XX/XX/10.44.79.15/2021031803/meta/tokenmap.json HTTP/1.1" 200 0[2021-03-25
> 02:23:50,202] DEBUG: Downloading
> /tmp/medusa-job-bd8a39ca-a5ea-4a3a-820f-0fa6ddc5130a/medusa-restore-197b6c82-4cd5-4c5b-b3c2-9d98863c1b3f
> as single part
> [2021-03-25 02:23:50,254] DEBUG: https://s3.cn-north-1.amazonaws.com.cn:443
> "GET /XX/XX/10.44.XX.XX/2021031803/meta/tokenmap.json?Version=2006-03-01
> HTTP/1.1" 200 1535[2021-03-25 02:23:50,255] INFO: Stopping Cassandra
> + /usr/bin/nodetool u cassandra -pw if9te8ohKei9xaep drain+ /usr/bin/nodetool
> -u cassandra -pw if9te8ohKei9xaep drainerror: null- StackTrace
> --java.io.EOFException at
> java.io.DataInputStream.readByte(DataInputStream.java:267) at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:222) at
> sun.rmi.server.UnicastRef.invoke(UnicastRef.java:161) at
> com.sun.jmx.remote.internal.PRef.invoke(Unknown Source) at
> javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(Unknown Source) at
> javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:1020)
> at
> javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:298)
> at com.sun.proxy.$Proxy8.drain(Unknown Source) at
> org.apache.cassandra.tools.NodeProbe.drain(NodeProbe.java:371) at
> org.apache.cassandra.tools.nodetool.Drain.execute(Drain.java:36) at
> org.apache.cassandra.tools.NodeTool$NodeToolCmd.run(NodeTool.java:244) at
> org.apache.cassandra.tools.NodeTool.main(NodeTool.java:158)
> + ls -l /var/run/cassandra/cassandra.pidls: cannot access
> /var/run/cassandra/cassandra.pid: No such file or directory+ sleep 10+ echo
> -n 'Shutdown Cassandra: 'Shutdown Cassandra: ++ cat
> /var/run/cassandra/cassandra.pidcat: /var/run/cassandra/cassandra.pid: No
> such file or directory+ su cassandra -c 'kill 'kill: usage: kill [-s sigspec
> | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]++ seq 40+ for
> t in '`seq 40`'+ /etc/init.d/cassandra status+ break+ sleep 5+ echo OKOK
> {code}
> But we can get a successful run of the command on one node for
> {code:java}
> export LC_ALL=en_US.UTF-8; export LANG=en_US.UTF-8; export
> https_proxy=http://proxy.XX:3128 ; export
> PATH=$PATH:/usr/share/cassandra-medusa/bin; sudo su; mkdir
> /tmp/medusa-job-bd8a39ca-a5ea-4a3a-820f-0fa6ddc5130a; cd
> /tmp/medusa-job-bd8a39ca-a5ea-4a3a-820f-0fa6ddc5130a;
> medusa-wrapper sudo
> medusa -vvv restore-node --in-place --no-verify --backup-name 2021031803
> --temp-dir /tmp/medusa-job-bd8a39ca-a5ea-4a3a-820f-0fa6ddc5130a{code}
> We are running the command on
> {code:java}
> uname -a
> Linux 5.3.0-53-generic #47~18.04.1-Ubuntu SMP Thu May 7 13:10:50 UTC
> 2020 x86_64 x86_64 x86_64 GNU/Linux{code}
> Could you please have a look at the issue?
> Thanks
--
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-16540) WEBSITE - Publish a new landing page for the 2021 World Party marketing efforts
[ https://issues.apache.org/jira/browse/CASSANDRA-16540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-16540: -- Change Category: Semantic Complexity: Normal Status: Open (was: Triage Needed) > WEBSITE - Publish a new landing page for the 2021 World Party marketing > efforts > --- > > Key: CASSANDRA-16540 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16540 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Attachments: cass-world-party.markdown, world-party-horizontal.png > > > Request from [~mklogan] at Constantia.io to create a new landing page for the > 2021 World Party to support marketing efforts. > Attached are the page draft and assets. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-16540) WEBSITE - Publish a new landing page for the 2021 World Party marketing efforts
Erick Ramirez created CASSANDRA-16540: - Summary: WEBSITE - Publish a new landing page for the 2021 World Party marketing efforts Key: CASSANDRA-16540 URL: https://issues.apache.org/jira/browse/CASSANDRA-16540 Project: Cassandra Issue Type: Task Components: Documentation/Website Reporter: Erick Ramirez Assignee: Erick Ramirez Attachments: cass-world-party.markdown, world-party-horizontal.png Request from [~mklogan] at Constantia.io to create a new landing page for the 2021 World Party to support marketing efforts. Attached are the page draft and assets. -- 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-13517) dtest failure in paxos_tests.TestPaxos.contention_test_many_threads
[
https://issues.apache.org/jira/browse/CASSANDRA-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17309073#comment-17309073
]
Ekaterina Dimitrova edited comment on CASSANDRA-13517 at 3/26/21, 1:22 AM:
---
Can we loop like 100 times the updated test on this resource-constrained VM?
(not a review, that I can do tomorrow :) )
was (Author: e.dimitrova):
Can we loop like 100 times the test on this resource-constrained VM?
(not a review, that I can do tomorrow :) )
> dtest failure in paxos_tests.TestPaxos.contention_test_many_threads
> ---
>
> Key: CASSANDRA-13517
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13517
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Ariel Weisberg
>Assignee: Adam Holmberg
>Priority: Normal
> Labels: dtest, test-failure, test-failure-fresh
> Fix For: 4.0-rc
>
> Attachments: test_failure.txt
>
>
> Error Message
> AssertionError: value=278, errors=22, retries=2888 assert (278 == (300 * 1))
> {noformat}
> > assert (value == threads * iterations) and (errors == 0), "value={},
> > errors={}, retries={}".format(value, errors, retries)
> E AssertionError: value=278, errors=22, retries=2888 E assert (278 == (300 *
> 1))
> paxos_test.py:195: AssertionError
> {noformat}
>
--
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-13517) dtest failure in paxos_tests.TestPaxos.contention_test_many_threads
[
https://issues.apache.org/jira/browse/CASSANDRA-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17309073#comment-17309073
]
Ekaterina Dimitrova commented on CASSANDRA-13517:
-
Can we loop like 100 times the test on this resource-constrained VM?
(not a review, that I can do tomorrow :) )
> dtest failure in paxos_tests.TestPaxos.contention_test_many_threads
> ---
>
> Key: CASSANDRA-13517
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13517
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Ariel Weisberg
>Assignee: Adam Holmberg
>Priority: Normal
> Labels: dtest, test-failure, test-failure-fresh
> Fix For: 4.0-rc
>
> Attachments: test_failure.txt
>
>
> Error Message
> AssertionError: value=278, errors=22, retries=2888 assert (278 == (300 * 1))
> {noformat}
> > assert (value == threads * iterations) and (errors == 0), "value={},
> > errors={}, retries={}".format(value, errors, retries)
> E AssertionError: value=278, errors=22, retries=2888 E assert (278 == (300 *
> 1))
> paxos_test.py:195: AssertionError
> {noformat}
>
--
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-13517) dtest failure in paxos_tests.TestPaxos.contention_test_many_threads
[
https://issues.apache.org/jira/browse/CASSANDRA-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17309069#comment-17309069
]
Brandon Williams commented on CASSANDRA-13517:
--
[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/508/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/508/pipeline]
> dtest failure in paxos_tests.TestPaxos.contention_test_many_threads
> ---
>
> Key: CASSANDRA-13517
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13517
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Ariel Weisberg
>Assignee: Adam Holmberg
>Priority: Normal
> Labels: dtest, test-failure, test-failure-fresh
> Fix For: 4.0-rc
>
> Attachments: test_failure.txt
>
>
> Error Message
> AssertionError: value=278, errors=22, retries=2888 assert (278 == (300 * 1))
> {noformat}
> > assert (value == threads * iterations) and (errors == 0), "value={},
> > errors={}, retries={}".format(value, errors, retries)
> E AssertionError: value=278, errors=22, retries=2888 E assert (278 == (300 *
> 1))
> paxos_test.py:195: AssertionError
> {noformat}
>
--
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-13517) dtest failure in paxos_tests.TestPaxos.contention_test_many_threads
[
https://issues.apache.org/jira/browse/CASSANDRA-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Holmberg updated CASSANDRA-13517:
--
Test and Documentation Plan: this is a small test change
Status: Patch Available (was: In Progress)
> dtest failure in paxos_tests.TestPaxos.contention_test_many_threads
> ---
>
> Key: CASSANDRA-13517
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13517
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Ariel Weisberg
>Assignee: Adam Holmberg
>Priority: Normal
> Labels: dtest, test-failure, test-failure-fresh
> Fix For: 4.0-rc
>
> Attachments: test_failure.txt
>
>
> Error Message
> AssertionError: value=278, errors=22, retries=2888 assert (278 == (300 * 1))
> {noformat}
> > assert (value == threads * iterations) and (errors == 0), "value={},
> > errors={}, retries={}".format(value, errors, retries)
> E AssertionError: value=278, errors=22, retries=2888 E assert (278 == (300 *
> 1))
> paxos_test.py:195: AssertionError
> {noformat}
>
--
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-13517) dtest failure in paxos_tests.TestPaxos.contention_test_many_threads
[
https://issues.apache.org/jira/browse/CASSANDRA-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17309065#comment-17309065
]
Adam Holmberg edited comment on CASSANDRA-13517 at 3/26/21, 12:35 AM:
--
The test fails this way intermittently, but consistently on a
resource-constrained VM. Failures are characterized by driver heartbeat
timeouts which [exits the
worker|https://github.com/apache/cassandra-dtest/blob/49f46fce94c8f25f32e9b778ded8b14c30ad851e/paxos_test.py#L145-L149]
and does not retry. I think the server and cluster are just being overwhelmed.
This never fails on a well-provisioned machine.
The proposed change creates a client connection with ample timeouts and
heartbeats disabled. I'm also reducing the concurrency from one arbitrary
number to another slightly smaller arbitrary number to make it a bit more
appropriate in the envelope of a single-host three-node test cluster.
[test patch|https://github.com/aholmberg/cassandra-dtest/pull/5]
[ci|https://app.circleci.com/pipelines/github/aholmberg/cassandra?branch=CASSANDRA-13517]
(started, not reviewed)
was (Author: aholmber):
The test fails this way intermittently, but consistently on a
resource-constrained VM. Failures are characterized by driver heartbeat
timeouts which [exits the
worker|https://github.com/apache/cassandra-dtest/blob/49f46fce94c8f25f32e9b778ded8b14c30ad851e/paxos_test.py#L145-L149]
and does not retry.
The proposed change creates a client connection with ample timeouts and
heartbeats disabled. I'm also reducing the concurrency from one arbitrary
number to another slightly smaller arbitrary number to make it a bit more
appropriate in the envelope of a single-host three-node test cluster.
[test patch|https://github.com/aholmberg/cassandra-dtest/pull/5]
[ci|https://app.circleci.com/pipelines/github/aholmberg/cassandra?branch=CASSANDRA-13517]
(started, not reviewed)
> dtest failure in paxos_tests.TestPaxos.contention_test_many_threads
> ---
>
> Key: CASSANDRA-13517
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13517
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Ariel Weisberg
>Assignee: Adam Holmberg
>Priority: Normal
> Labels: dtest, test-failure, test-failure-fresh
> Fix For: 4.0-rc
>
> Attachments: test_failure.txt
>
>
> Error Message
> AssertionError: value=278, errors=22, retries=2888 assert (278 == (300 * 1))
> {noformat}
> > assert (value == threads * iterations) and (errors == 0), "value={},
> > errors={}, retries={}".format(value, errors, retries)
> E AssertionError: value=278, errors=22, retries=2888 E assert (278 == (300 *
> 1))
> paxos_test.py:195: AssertionError
> {noformat}
>
--
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-13517) dtest failure in paxos_tests.TestPaxos.contention_test_many_threads
[
https://issues.apache.org/jira/browse/CASSANDRA-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17309065#comment-17309065
]
Adam Holmberg commented on CASSANDRA-13517:
---
The test fails this way intermittently, but consistently on a
resource-constrained VM. Failures are characterized by driver heartbeat
timeouts which [exits the
worker|https://github.com/apache/cassandra-dtest/blob/49f46fce94c8f25f32e9b778ded8b14c30ad851e/paxos_test.py#L145-L149]
and does not retry.
The proposed change creates a client connection with ample timeouts and
heartbeats disabled. I'm also reducing the concurrency from one arbitrary
number to another slightly smaller arbitrary number to make it a bit more
appropriate in the envelope of a single-host three-node test cluster.
[test patch|https://github.com/aholmberg/cassandra-dtest/pull/5]
[ci|https://app.circleci.com/pipelines/github/aholmberg/cassandra?branch=CASSANDRA-13517]
(started, not reviewed)
> dtest failure in paxos_tests.TestPaxos.contention_test_many_threads
> ---
>
> Key: CASSANDRA-13517
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13517
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Ariel Weisberg
>Assignee: Adam Holmberg
>Priority: Normal
> Labels: dtest, test-failure, test-failure-fresh
> Fix For: 4.0-rc
>
> Attachments: test_failure.txt
>
>
> Error Message
> AssertionError: value=278, errors=22, retries=2888 assert (278 == (300 * 1))
> {noformat}
> > assert (value == threads * iterations) and (errors == 0), "value={},
> > errors={}, retries={}".format(value, errors, retries)
> E AssertionError: value=278, errors=22, retries=2888 E assert (278 == (300 *
> 1))
> paxos_test.py:195: AssertionError
> {noformat}
>
--
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-16524) Upgrading SSL enabled Cassandra cluster from 3.11.10 to 4.0-beta4 failing with javax.net.ssl.SSLException: java.lang.IndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/CASSANDRA-16524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17309057#comment-17309057
]
Jon Meredith commented on CASSANDRA-16524:
--
Do you have larger than usual key sizes or perhaps an openssl configuration
that's being picked up on the host? It seems to be failing when adding the key
material.
> Upgrading SSL enabled Cassandra cluster from 3.11.10 to 4.0-beta4 failing
> with javax.net.ssl.SSLException: java.lang.IndexOutOfBoundsException
> --
>
> Key: CASSANDRA-16524
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16524
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Encryption
>Reporter: Alaykumar Barochia
>Assignee: Gianluca Righetto
>Priority: Normal
> Fix For: 4.0, 4.0-rc
>
> Attachments: system.log.ssl-error.txt
>
>
> Hi,
> We have SSL enabled cluster running on Apache Cassandra 3.11.10 and we are
> trying to upgrade it to 4.0-beta4 as a part of testing.
> Cluster size is 3x3 and deployed on Azure IaaS.
> {noformat}
> [cassandra@cass-521828978-1-1189299202 ~]$ nodetool status
> Datacenter: southcentral
>
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> -- Address Load Tokens Owns (effective) Host ID
>Rack
> UN 10.12.74.31 85.61 KiB 16 32.2%
> 6db7a7ef-3490-4823-9ff3-c60a32165124 2
> UN 10.12.74.42 263.27 KiB 16 27.6%
> 7ad99ecf-7c7d-4780-872b-7c68b6b19849 1
> UN 10.12.74.34 85.61 KiB 16 37.8%
> 41ce16b7-2ab2-44ea-a810-8391f7f3caf2 0
> Datacenter: westus
> ==
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> -- Address Load Tokens Owns (effective) Host ID
>Rack
> UN 10.12.90.11 90.63 KiB 16 38.9%
> 8d4cdb65-ff66-4bcd-8d4b-a4a0e893a728 2
> UN 10.12.90.6 85.61 KiB 16 34.5%
> 4f8007e9-fa3e-4e99-a9f9-f7bf9625 1
> UN 10.12.89.80 94.1 KiB 16 28.9%
> 11f86cb0-c86b-440e-848f-b160118f43d5 0
> {noformat}
> We placed a new 4.0-beta4 binary on the first seed node (10.12.74.310) and
> starting Cassandra.
> It started throwing the below error:
> {noformat}
> ERROR [Messaging-EventLoop-3-11] 2021-03-15 22:10:05,188
> InboundConnectionInitiator.java:342 - Failed to properly handshake with peer
> /10.12.74.42:52356. Closing the channel.
> io.netty.handler.codec.DecoderException: javax.net.ssl.SSLException:
> java.lang.IndexOutOfBoundsException: writerIndex(8560) +
> minWritableBytes(1977) exceeds maxCapacity(10240):
> BufferPoolAllocator$Wrapped(ridx: 0, widx: 8560, cap: 10240/10240)
> at
> io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:471)
> at
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:276)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
> at
> io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
> at
> io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
> at
> io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:795)
> at
> io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:480)
> at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:378)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
> at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: javax.net.ssl.SSLException: java.lang.IndexOutOfBoundsException:
> writerIndex(8560) + minWritableBytes(1977) exceeds maxCapacity(10240):
> BufferPoolAllocator$Wrapped(ridx: 0, widx: 8560, cap: 10240/10240)
> at
>
[jira] [Commented] (CASSANDRA-13196) test failure in snitch_test.TestGossipingPropertyFileSnitch.test_prefer_local_reconnect_on_listen_address
[
https://issues.apache.org/jira/browse/CASSANDRA-13196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17309049#comment-17309049
]
Ekaterina Dimitrova commented on CASSANDRA-13196:
-
PS I ran the new version also locally with 3.0 and 3.11 and it passes
successfully
> test failure in
> snitch_test.TestGossipingPropertyFileSnitch.test_prefer_local_reconnect_on_listen_address
> -
>
> Key: CASSANDRA-13196
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13196
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Testing
>Reporter: Michael Shuler
>Assignee: Brandon Williams
>Priority: Normal
> Labels: dtest, test-failure
> Fix For: 4.0, 4.0-rc
>
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log,
> node2_debug.log, node2_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_dtest/1487/testReport/snitch_test/TestGossipingPropertyFileSnitch/test_prefer_local_reconnect_on_listen_address
> {code}
> {novnode}
> Error Message
> Error from server: code=2200 [Invalid query] message="keyspace keyspace1 does
> not exist"
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /tmp/dtest-k6b0iF
> dtest: DEBUG: Done setting configuration options:
> { 'initial_token': None,
> 'num_tokens': '32',
> 'phi_convict_threshold': 5,
> 'range_request_timeout_in_ms': 1,
> 'read_request_timeout_in_ms': 1,
> 'request_timeout_in_ms': 1,
> 'truncate_request_timeout_in_ms': 1,
> 'write_request_timeout_in_ms': 1}
> cassandra.policies: INFO: Using datacenter 'dc1' for DCAwareRoundRobinPolicy
> (via host '127.0.0.1'); if incorrect, please specify a local_dc to the
> constructor, or limit contact points to local cluster nodes
> cassandra.cluster: INFO: New Cassandra host discovered
> - >> end captured logging << -
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/snitch_test.py", line 87, in
> test_prefer_local_reconnect_on_listen_address
> new_rows = list(session.execute("SELECT * FROM {}".format(stress_table)))
> File "/home/automaton/src/cassandra-driver/cassandra/cluster.py", line
> 1998, in execute
> return self.execute_async(query, parameters, trace, custom_payload,
> timeout, execution_profile, paging_state).result()
> File "/home/automaton/src/cassandra-driver/cassandra/cluster.py", line
> 3784, in result
> raise self._final_exception
> 'Error from server: code=2200 [Invalid query] message="keyspace keyspace1
> does not exist"\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /tmp/dtest-k6b0iF\ndtest: DEBUG: Done setting configuration options:\n{
> \'initial_token\': None,\n\'num_tokens\': \'32\',\n
> \'phi_convict_threshold\': 5,\n\'range_request_timeout_in_ms\': 1,\n
> \'read_request_timeout_in_ms\': 1,\n\'request_timeout_in_ms\':
> 1,\n\'truncate_request_timeout_in_ms\': 1,\n
> \'write_request_timeout_in_ms\': 1}\ncassandra.policies: INFO: Using
> datacenter \'dc1\' for DCAwareRoundRobinPolicy (via host \'127.0.0.1\'); if
> incorrect, please specify a local_dc to the constructor, or limit contact
> points to local cluster nodes\ncassandra.cluster: INFO: New Cassandra host
> discovered\n- >> end captured
> logging << -'
> {novnode}
> {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] [Comment Edited] (CASSANDRA-13196) test failure in snitch_test.TestGossipingPropertyFileSnitch.test_prefer_local_reconnect_on_listen_address
[
https://issues.apache.org/jira/browse/CASSANDRA-13196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17309046#comment-17309046
]
Ekaterina Dimitrova edited comment on CASSANDRA-13196 at 3/25/21, 11:47 PM:
I am +1 on the new version of the test. The patterns are way more reliable and
remove the need of updating the previous strings all the time.
I haven't been able to reproduce the test failure or find recent CI failures.
Looking at the log from Caleb what you say seems reasonable to me from code
inspection.
I suggest we commit the new version and close the ticket. If the issue
reappears we will reopen it. WDYT?
was (Author: e.dimitrova):
I am +1 on the new version of the test. The patterns are way more reliable and
remove the need of updating the previous strings all the time.
I haven't been able to reproduce the test failure or find recent failures.
Looking at the log from Caleb what you say seems reasonable to me from code
inspection.
I suggest we commit the new version and close the ticket. If the issue
reappears we will reopen it. WDYT?
> test failure in
> snitch_test.TestGossipingPropertyFileSnitch.test_prefer_local_reconnect_on_listen_address
> -
>
> Key: CASSANDRA-13196
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13196
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Testing
>Reporter: Michael Shuler
>Assignee: Brandon Williams
>Priority: Normal
> Labels: dtest, test-failure
> Fix For: 4.0, 4.0-rc
>
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log,
> node2_debug.log, node2_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_dtest/1487/testReport/snitch_test/TestGossipingPropertyFileSnitch/test_prefer_local_reconnect_on_listen_address
> {code}
> {novnode}
> Error Message
> Error from server: code=2200 [Invalid query] message="keyspace keyspace1 does
> not exist"
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /tmp/dtest-k6b0iF
> dtest: DEBUG: Done setting configuration options:
> { 'initial_token': None,
> 'num_tokens': '32',
> 'phi_convict_threshold': 5,
> 'range_request_timeout_in_ms': 1,
> 'read_request_timeout_in_ms': 1,
> 'request_timeout_in_ms': 1,
> 'truncate_request_timeout_in_ms': 1,
> 'write_request_timeout_in_ms': 1}
> cassandra.policies: INFO: Using datacenter 'dc1' for DCAwareRoundRobinPolicy
> (via host '127.0.0.1'); if incorrect, please specify a local_dc to the
> constructor, or limit contact points to local cluster nodes
> cassandra.cluster: INFO: New Cassandra host discovered
> - >> end captured logging << -
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/snitch_test.py", line 87, in
> test_prefer_local_reconnect_on_listen_address
> new_rows = list(session.execute("SELECT * FROM {}".format(stress_table)))
> File "/home/automaton/src/cassandra-driver/cassandra/cluster.py", line
> 1998, in execute
> return self.execute_async(query, parameters, trace, custom_payload,
> timeout, execution_profile, paging_state).result()
> File "/home/automaton/src/cassandra-driver/cassandra/cluster.py", line
> 3784, in result
> raise self._final_exception
> 'Error from server: code=2200 [Invalid query] message="keyspace keyspace1
> does not exist"\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /tmp/dtest-k6b0iF\ndtest: DEBUG: Done setting configuration options:\n{
> \'initial_token\': None,\n\'num_tokens\': \'32\',\n
> \'phi_convict_threshold\': 5,\n\'range_request_timeout_in_ms\': 1,\n
> \'read_request_timeout_in_ms\': 1,\n\'request_timeout_in_ms\':
> 1,\n\'truncate_request_timeout_in_ms\': 1,\n
> \'write_request_timeout_in_ms\': 1}\ncassandra.policies: INFO: Using
> datacenter \'dc1\' for DCAwareRoundRobinPolicy (via host \'127.0.0.1\'); if
> incorrect, please specify a local_dc to the constructor, or limit contact
> points to local cluster nodes\ncassandra.cluster: INFO: New Cassandra host
> discovered\n- >> end captured
> logging << -'
> {novnode}
> {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-13196) test failure in snitch_test.TestGossipingPropertyFileSnitch.test_prefer_local_reconnect_on_listen_address
[
https://issues.apache.org/jira/browse/CASSANDRA-13196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17309046#comment-17309046
]
Ekaterina Dimitrova commented on CASSANDRA-13196:
-
I am +1 on the new version of the test. The patterns are way more reliable and
remove the need of updating the previous strings all the time.
I haven't been able to reproduce the test failure or find recent failures.
Looking at the log from Caleb what you say seems reasonable to me from code
inspection.
I suggest we commit the new version and close the ticket. If the issue
reappears we will reopen it. WDYT?
> test failure in
> snitch_test.TestGossipingPropertyFileSnitch.test_prefer_local_reconnect_on_listen_address
> -
>
> Key: CASSANDRA-13196
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13196
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Testing
>Reporter: Michael Shuler
>Assignee: Brandon Williams
>Priority: Normal
> Labels: dtest, test-failure
> Fix For: 4.0, 4.0-rc
>
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log,
> node2_debug.log, node2_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_dtest/1487/testReport/snitch_test/TestGossipingPropertyFileSnitch/test_prefer_local_reconnect_on_listen_address
> {code}
> {novnode}
> Error Message
> Error from server: code=2200 [Invalid query] message="keyspace keyspace1 does
> not exist"
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /tmp/dtest-k6b0iF
> dtest: DEBUG: Done setting configuration options:
> { 'initial_token': None,
> 'num_tokens': '32',
> 'phi_convict_threshold': 5,
> 'range_request_timeout_in_ms': 1,
> 'read_request_timeout_in_ms': 1,
> 'request_timeout_in_ms': 1,
> 'truncate_request_timeout_in_ms': 1,
> 'write_request_timeout_in_ms': 1}
> cassandra.policies: INFO: Using datacenter 'dc1' for DCAwareRoundRobinPolicy
> (via host '127.0.0.1'); if incorrect, please specify a local_dc to the
> constructor, or limit contact points to local cluster nodes
> cassandra.cluster: INFO: New Cassandra host discovered
> - >> end captured logging << -
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/snitch_test.py", line 87, in
> test_prefer_local_reconnect_on_listen_address
> new_rows = list(session.execute("SELECT * FROM {}".format(stress_table)))
> File "/home/automaton/src/cassandra-driver/cassandra/cluster.py", line
> 1998, in execute
> return self.execute_async(query, parameters, trace, custom_payload,
> timeout, execution_profile, paging_state).result()
> File "/home/automaton/src/cassandra-driver/cassandra/cluster.py", line
> 3784, in result
> raise self._final_exception
> 'Error from server: code=2200 [Invalid query] message="keyspace keyspace1
> does not exist"\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /tmp/dtest-k6b0iF\ndtest: DEBUG: Done setting configuration options:\n{
> \'initial_token\': None,\n\'num_tokens\': \'32\',\n
> \'phi_convict_threshold\': 5,\n\'range_request_timeout_in_ms\': 1,\n
> \'read_request_timeout_in_ms\': 1,\n\'request_timeout_in_ms\':
> 1,\n\'truncate_request_timeout_in_ms\': 1,\n
> \'write_request_timeout_in_ms\': 1}\ncassandra.policies: INFO: Using
> datacenter \'dc1\' for DCAwareRoundRobinPolicy (via host \'127.0.0.1\'); if
> incorrect, please specify a local_dc to the constructor, or limit contact
> points to local cluster nodes\ncassandra.cluster: INFO: New Cassandra host
> discovered\n- >> end captured
> logging << -'
> {novnode}
> {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] [Assigned] (CASSANDRA-13517) dtest failure in paxos_tests.TestPaxos.contention_test_many_threads
[
https://issues.apache.org/jira/browse/CASSANDRA-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Holmberg reassigned CASSANDRA-13517:
-
Assignee: Adam Holmberg (was: Jason Brown)
> dtest failure in paxos_tests.TestPaxos.contention_test_many_threads
> ---
>
> Key: CASSANDRA-13517
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13517
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Ariel Weisberg
>Assignee: Adam Holmberg
>Priority: Normal
> Labels: dtest, test-failure, test-failure-fresh
> Fix For: 4.0-rc
>
> Attachments: test_failure.txt
>
>
> Error Message
> AssertionError: value=278, errors=22, retries=2888 assert (278 == (300 * 1))
> {noformat}
> > assert (value == threads * iterations) and (errors == 0), "value={},
> > errors={}, retries={}".format(value, errors, retries)
> E AssertionError: value=278, errors=22, retries=2888 E assert (278 == (300 *
> 1))
> paxos_test.py:195: AssertionError
> {noformat}
>
--
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-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2
[
https://issues.apache.org/jira/browse/CASSANDRA-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-16536:
--
Status: Changes Suggested (was: Review In Progress)
Please git remove
{{src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown}} so we
don't end up with duplicate posts and just have
{{2021-03-29-cassandra-and-kubernetes-sig-update.markdown}}.
Once done, I'll stage it for final review. Cheers! :)
> BLOG - Post about Cassandra & Kubernetes - SIG Update #2
>
>
> Key: CASSANDRA-16536
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16536
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Michael Semb Wever
>Priority: High
> Labels: pull-request-available
> Fix For: 4.0-beta5, 4.0
>
> Attachments: image-2021-03-24-18-57-08-450.png
>
>
> We're getting another update up for the Cassandra & Kubernetes SIG
>
> [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2
[ https://issues.apache.org/jira/browse/CASSANDRA-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-16536: -- Status: Review In Progress (was: Changes Suggested) Reviewing updates to [PR #39|https://github.com/apache/cassandra-website/pull/39]. > BLOG - Post about Cassandra & Kubernetes - SIG Update #2 > > > Key: CASSANDRA-16536 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16536 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Michael Semb Wever >Priority: High > Labels: pull-request-available > Fix For: 4.0-beta5, 4.0 > > Attachments: image-2021-03-24-18-57-08-450.png > > > We're getting another update up for the Cassandra & Kubernetes SIG > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown] > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16245) Implement repair quality test scenarios
[ https://issues.apache.org/jira/browse/CASSANDRA-16245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17309000#comment-17309000 ] Ekaterina Dimitrova commented on CASSANDRA-16245: - Does this need a reviewer as stated in the weekly progress report or it is ready to be closed? > Implement repair quality test scenarios > --- > > Key: CASSANDRA-16245 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16245 > Project: Cassandra > Issue Type: Task > Components: Test/dtest/java >Reporter: Alexander Dejanovski >Assignee: Radovan Zvoncek >Priority: Normal > Fix For: 4.0-rc > > > Implement the following test scenarios in a new test suite for repair > integration testing with significant load: > Generate/restore a workload of ~100GB per node. Medusa should be considered > to create the initial backup which could then be restored from an S3 bucket > to speed up node population. > Data should on purpose require repair and be generated accordingly. > Perform repairs for a 3 nodes cluster with 4 cores each and 16GB-32GB RAM > (m5d.xlarge instances would be the most cost efficient type). > Repaired keyspaces will use RF=3 or RF=2 in some cases (the latter is for > subranges with different sets of replicas). > ||Mode||Version||Settings||Checks|| > |Full repair|trunk|Sequential + All token ranges|"No anticompaction > (repairedAt==0) > Out of sync ranges > 0 > Subsequent run must show no out of sync range"| > |Full repair|trunk|Parallel + Primary range|"No anticompaction (repairedAt==0) > Out of sync ranges > 0 > Subsequent run must show no out of sync range"| > |Full repair|trunk|Force terminate repair shortly after it was > triggered|Repair threads must be cleaned up| > |Subrange repair|trunk|Sequential + single token range|"No anticompaction > (repairedAt==0) > Out of sync ranges > 0 > Subsequent run must show no out of sync range"| > |Subrange repair|trunk|Parallel + 10 token ranges which have the same > replicas|"No anticompaction (repairedAt == 0) > Out of sync ranges > 0 > Subsequent run must show no out of sync range > A single repair session will handle all subranges at once"| > |Subrange repair|trunk|Parallel + 10 token ranges which have different > replicas|"No anticompaction (repairedAt==0) > Out of sync ranges > 0 > Subsequent run must show no out of sync range > More than one repair session is triggered to process all subranges"| > |Incremental repair|trunk|"Parallel (mandatory) > No compaction during repair"|"Anticompaction status (repairedAt != 0) on all > SSTables > No pending repair on SSTables after completion (could require to wait a bit > as this will happen asynchronously) > Out of sync ranges > 0 + Subsequent run must show no out of sync range"| > |Incremental repair|trunk|"Parallel (mandatory) > Major compaction triggered during repair"|"Anticompaction status (repairedAt > != 0) on all SSTables > No pending repair on SSTables after completion (could require to wait a bit > as this will happen asynchronously) > Out of sync ranges > 0 + Subsequent run must show no out of sync range"| > |Incremental repair|trunk|Force terminate repair shortly after it was > triggered.|Repair threads must be cleaned up| -- 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-16524) Upgrading SSL enabled Cassandra cluster from 3.11.10 to 4.0-beta4 failing with javax.net.ssl.SSLException: java.lang.IndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/CASSANDRA-16524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gianluca Righetto reassigned CASSANDRA-16524:
-
Assignee: Gianluca Righetto
> Upgrading SSL enabled Cassandra cluster from 3.11.10 to 4.0-beta4 failing
> with javax.net.ssl.SSLException: java.lang.IndexOutOfBoundsException
> --
>
> Key: CASSANDRA-16524
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16524
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Encryption
>Reporter: Alaykumar Barochia
>Assignee: Gianluca Righetto
>Priority: Normal
> Fix For: 4.0, 4.0-rc
>
> Attachments: system.log.ssl-error.txt
>
>
> Hi,
> We have SSL enabled cluster running on Apache Cassandra 3.11.10 and we are
> trying to upgrade it to 4.0-beta4 as a part of testing.
> Cluster size is 3x3 and deployed on Azure IaaS.
> {noformat}
> [cassandra@cass-521828978-1-1189299202 ~]$ nodetool status
> Datacenter: southcentral
>
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> -- Address Load Tokens Owns (effective) Host ID
>Rack
> UN 10.12.74.31 85.61 KiB 16 32.2%
> 6db7a7ef-3490-4823-9ff3-c60a32165124 2
> UN 10.12.74.42 263.27 KiB 16 27.6%
> 7ad99ecf-7c7d-4780-872b-7c68b6b19849 1
> UN 10.12.74.34 85.61 KiB 16 37.8%
> 41ce16b7-2ab2-44ea-a810-8391f7f3caf2 0
> Datacenter: westus
> ==
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> -- Address Load Tokens Owns (effective) Host ID
>Rack
> UN 10.12.90.11 90.63 KiB 16 38.9%
> 8d4cdb65-ff66-4bcd-8d4b-a4a0e893a728 2
> UN 10.12.90.6 85.61 KiB 16 34.5%
> 4f8007e9-fa3e-4e99-a9f9-f7bf9625 1
> UN 10.12.89.80 94.1 KiB 16 28.9%
> 11f86cb0-c86b-440e-848f-b160118f43d5 0
> {noformat}
> We placed a new 4.0-beta4 binary on the first seed node (10.12.74.310) and
> starting Cassandra.
> It started throwing the below error:
> {noformat}
> ERROR [Messaging-EventLoop-3-11] 2021-03-15 22:10:05,188
> InboundConnectionInitiator.java:342 - Failed to properly handshake with peer
> /10.12.74.42:52356. Closing the channel.
> io.netty.handler.codec.DecoderException: javax.net.ssl.SSLException:
> java.lang.IndexOutOfBoundsException: writerIndex(8560) +
> minWritableBytes(1977) exceeds maxCapacity(10240):
> BufferPoolAllocator$Wrapped(ridx: 0, widx: 8560, cap: 10240/10240)
> at
> io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:471)
> at
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:276)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
> at
> io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
> at
> io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
> at
> io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:795)
> at
> io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:480)
> at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:378)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
> at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: javax.net.ssl.SSLException: java.lang.IndexOutOfBoundsException:
> writerIndex(8560) + minWritableBytes(1977) exceeds maxCapacity(10240):
> BufferPoolAllocator$Wrapped(ridx: 0, widx: 8560, cap: 10240/10240)
> at
> io.netty.handler.ssl.OpenSslKeyMaterialManager.setKeyMaterial(OpenSslKeyMaterialManager.java:115)
> at
>
[jira] [Updated] (CASSANDRA-16539) cqlsh encoding error with unicode in multi-line statement
[
https://issues.apache.org/jira/browse/CASSANDRA-16539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Holmberg updated CASSANDRA-16539:
--
Summary: cqlsh encoding error with unicode in multi-line statement (was:
cqlsh fails with encoding)
> cqlsh encoding error with unicode in multi-line statement
> -
>
> Key: CASSANDRA-16539
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16539
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: Adam Holmberg
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0.x
>
>
> {noformat}
> CREATE TABLE test.users (
> user_id int PRIMARY KEY,
> name text,
> state text
> )
> {noformat}
> Multiline cql with unicode characters will fail with an encoding error:
> {noformat}
> cqlsh> insert into test.users ( user_id, name, state ) values (
>... 6,
>... 'Bonne',
>... 'Année');
> 'ascii' codec can't encode character u'\xe9' in position 74: ordinal not in
> range(128)
> {noformat}
> This is only when running Python 2.7 (deprecated in 4.0) and when python3 is
> not present in the environment.
--
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-16539) cqlsh fails with encoding
[
https://issues.apache.org/jira/browse/CASSANDRA-16539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Holmberg updated CASSANDRA-16539:
--
Bug Category: Parent values: Correctness(12982)
Complexity: Low Hanging Fruit
Discovered By: User Report
Fix Version/s: 4.0.x
Severity: Low
Status: Open (was: Triage Needed)
> cqlsh fails with encoding
> -
>
> Key: CASSANDRA-16539
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16539
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: Adam Holmberg
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0.x
>
>
> {noformat}
> CREATE TABLE test.users (
> user_id int PRIMARY KEY,
> name text,
> state text
> )
> {noformat}
> Multiline cql with unicode characters will fail with an encoding error:
> {noformat}
> cqlsh> insert into test.users ( user_id, name, state ) values (
>... 6,
>... 'Bonne',
>... 'Année');
> 'ascii' codec can't encode character u'\xe9' in position 74: ordinal not in
> range(128)
> {noformat}
> This is only when running Python 2.7 (deprecated in 4.0) and when python3 is
> not present in the environment.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-16539) cqlsh fails with encoding
Adam Holmberg created CASSANDRA-16539:
-
Summary: cqlsh fails with encoding
Key: CASSANDRA-16539
URL: https://issues.apache.org/jira/browse/CASSANDRA-16539
Project: Cassandra
Issue Type: Bug
Components: Tool/cqlsh
Reporter: Adam Holmberg
Assignee: Adam Holmberg
{noformat}
CREATE TABLE test.users (
user_id int PRIMARY KEY,
name text,
state text
)
{noformat}
Multiline cql with unicode characters will fail with an encoding error:
{noformat}
cqlsh> insert into test.users ( user_id, name, state ) values (
... 6,
... 'Bonne',
... 'Année');
'ascii' codec can't encode character u'\xe9' in position 74: ordinal not in
range(128)
{noformat}
This is only when running Python 2.7 (deprecated in 4.0) and when python3 is
not present in the environment.
--
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-15892) JAVA 8/11: test_resumable_rebuild - rebuild_test.TestRebuild
[ https://issues.apache.org/jira/browse/CASSANDRA-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-15892: Reviewers: Ekaterina Dimitrova, Michael Semb Wever, Zhao Yang (was: Ekaterina Dimitrova, Michael Semb Wever) > JAVA 8/11: test_resumable_rebuild - rebuild_test.TestRebuild > > > Key: CASSANDRA-15892 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15892 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Ekaterina Dimitrova >Assignee: Gianluca Righetto >Priority: Normal > Fix For: 4.0-rc > > Attachments: CASSANDRA-15892-07babf3c-node2-deadlock-thread-dump.txt, > Screenshot 2021-03-23 at 19.37.35.png, Screenshot 2021-03-23 at 19.53.51.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > JAVA 11: > test_resumable_rebuild - rebuild_test.TestRebuild > Fails locally and in > [CircleCI | > [https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/222/workflows/11202c7e-6c94-4d4e-bbbf-9e2fa9791ad0/jobs/1338]] -- 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-11684) Cleanup key ranges during compaction
[ https://issues.apache.org/jira/browse/CASSANDRA-11684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paulo Motta updated CASSANDRA-11684: Resolution: Duplicate Status: Resolved (was: Open) Thanks for clarifying [~jjirsa]! Closing as duplicate of CASSANDRA-5051. > Cleanup key ranges during compaction > > > Key: CASSANDRA-11684 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11684 > Project: Cassandra > Issue Type: Improvement > Components: Local/Compaction >Reporter: Stefan Podkowinski >Priority: Normal > > Currently cleanup is considered an optional, manual operation that users are > told to run to free disk space after a node was affected by topology changes. > However, unmanaged key ranges could also end up on a node through other ways, > e.g. manual added sstable files by an admin. > I'm also not sure unmanaged data is really that harmless and cleanup should > really be optional, if you don't need to reclaim the disk space. When it > comes to repairs, users are expected to purge a node after downtime in case > it was not fully covered by a repair within gc_grace afterwards, in order to > avoid re-introducing deleted data. But the same could happen with unmanaged > data, e.g. after topology changes activate unmanaged ranges again or after > restoring backups. > I'd therefor suggest to avoid rewriting key ranges no longer belonging to a > node and older than gc_grace during compactions. > Maybe we could also introduce another CLEANUP_COMPACTION operation to find > candidates based on SSTable.first/last in case we don't have pending regular > or tombstone compactions. -- 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-16500) Missing validation in AbstractType.writeValue():
[
https://issues.apache.org/jira/browse/CASSANDRA-16500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-16500:
Fix Version/s: (was: 4.0-rc)
4.0
4.0-beta5
Since Version: 4.0-beta4
Source Control Link:
https://github.com/apache/cassandra/commit/eb68380866c9d96592580fefbc1b79a497a674bf
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Missing validation in AbstractType.writeValue():
>
>
> Key: CASSANDRA-16500
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16500
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Other
>Reporter: Benjamin Lerer
>Assignee: Alexandre Dutra
>Priority: Normal
> Fix For: 4.0-beta5, 4.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Some validation checks present in {{AbstractType.writeValue()}} in
> {{cassandra-3.11}} are not there in {{trunk}}.
> In 3.11 the checks used assertion. It would make sense to use
> {{IOExceptions}} instead as used in {{AbstractType.readValue()}}.
--
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-16500) Missing validation in AbstractType.writeValue():
[
https://issues.apache.org/jira/browse/CASSANDRA-16500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308944#comment-17308944
]
Ekaterina Dimitrova commented on CASSANDRA-16500:
-
Committed [here
|https://github.com/apache/cassandra/commit/eb68380866c9d96592580fefbc1b79a497a674bf]
and a CHANGES.txt ninja fix [here
|https://github.com/apache/cassandra/commit/866844743ec3cd23451b0158a7841a026e2e68d6]
Thank you all!
> Missing validation in AbstractType.writeValue():
>
>
> Key: CASSANDRA-16500
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16500
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Other
>Reporter: Benjamin Lerer
>Assignee: Alexandre Dutra
>Priority: Normal
> Fix For: 4.0-rc
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Some validation checks present in {{AbstractType.writeValue()}} in
> {{cassandra-3.11}} are not there in {{trunk}}.
> In 3.11 the checks used assertion. It would make sense to use
> {{IOExceptions}} instead as used in {{AbstractType.readValue()}}.
--
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-16364) Simultaneous bootstrap can cause token collision
[
https://issues.apache.org/jira/browse/CASSANDRA-16364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308942#comment-17308942
]
Paulo Motta commented on CASSANDRA-16364:
-
bq. I will point out that simultaneous bootstrap is actually not valid after
CASSANDRA-2434, so I don't think this is technically a regression.
The issue happens with {{auto_bootstrap: false}}. Previously since token
generation was random, the likelihood of token collision existed but was pretty
low. With {{allocate_tokens_for_local_rf}} by default, since token generation
is deterministic the likelihood of collision is higher if all nodes are brought
up simultaneously (such as when instantiating a new DC or bringing up a CCM
cluster). For instance we have nodes A, B and C. Nodes B and C don't see each
other but see node A so they generate the same tokens and collide, only one of
them succeed.
> Simultaneous bootstrap can cause token collision
>
>
> Key: CASSANDRA-16364
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16364
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Membership
>Reporter: Paulo Motta
>Priority: Urgent
> Fix For: 4.0.x
>
>
> While raising a 6-node ccm cluster to test 4.0-beta4, 2 nodes chosen the same
> tokens using the default {{allocate_tokens_for_local_rf}}. However they both
> succeeded bootstrap with colliding tokens.
> We were familiar with this issue from CASSANDRA-13701 and CASSANDRA-16079,
> and the workaround to fix this is to avoid parallel bootstrap when using
> {{allocate_tokens_for_local_rf}}.
> However, since this is the default behavior, we should try to detect and
> prevent this situation when possible, since it can break users relying on
> parallel bootstrap behavior.
> I think we could prevent this as following:
> 1. announce intent to bootstrap via gossip (ie. add node on gossip without
> token information)
> 2. wait for gossip to settle for a longer period (ie. ring delay)
> 3. allocate tokens (if multiple bootstrap attempts are detected, tie break
> via node-id)
> 4. broadcast tokens and move on with bootstrap
--
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: ninja fix CHANGES.txt entry for CASSANDRA-16500
This is an automated email from the ASF dual-hosted git repository. edimitrova 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 8668447 ninja fix CHANGES.txt entry for CASSANDRA-16500 8668447 is described below commit 866844743ec3cd23451b0158a7841a026e2e68d6 Author: Ekaterina Dimitrova AuthorDate: Thu Mar 25 15:56:59 2021 -0400 ninja fix CHANGES.txt entry for CASSANDRA-16500 --- CHANGES.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/CHANGES.txt b/CHANGES.txt index bb9bd81..b06dbd2 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 4.0-beta5 + * Throw IOE in AbstractType.writeValue if value has wrong fixed length (CASSANDRA-16500) * Execute background refreshing of auth caches on a dedicated executor (CASSANDRA-15177) * Update bundled java and python drivers to 3.11.0 and 3.25.0 respectively (CASSANDRA-13951) * Add io.netty.tryReflectionSetAccessible=true to j11 server options in order to enable netty to use Unsafe direct byte buffer construction (CASSANDRA-16493) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated: Throw IOE in AbstractType.writeValue if value has wrong fixed length authored by Alexandre Dutra; reviewed by Berenguer Blasi and Andres de la Pena for CASSANDRA-1650
This is an automated email from the ASF dual-hosted git repository.
edimitrova 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 eb68380 Throw IOE in AbstractType.writeValue if value has wrong fixed
length authored by Alexandre Dutra; reviewed by Berenguer Blasi and Andres de
la Pena for CASSANDRA-16500
eb68380 is described below
commit eb68380866c9d96592580fefbc1b79a497a674bf
Author: Alexandre Dutra
AuthorDate: Wed Mar 10 11:01:35 2021 +0100
Throw IOE in AbstractType.writeValue if value has wrong fixed length
authored by Alexandre Dutra; reviewed by Berenguer Blasi and Andres de la
Pena for CASSANDRA-16500
---
.../apache/cassandra/db/marshal/AbstractType.java | 18 ++
test/unit/org/apache/cassandra/db/ScrubTest.java| 3 ++-
.../cassandra/db/marshal/TypeValidationTest.java| 21 -
3 files changed, 36 insertions(+), 6 deletions(-)
diff --git a/src/java/org/apache/cassandra/db/marshal/AbstractType.java
b/src/java/org/apache/cassandra/db/marshal/AbstractType.java
index 0b47644..19cf849 100644
--- a/src/java/org/apache/cassandra/db/marshal/AbstractType.java
+++ b/src/java/org/apache/cassandra/db/marshal/AbstractType.java
@@ -435,11 +435,21 @@ public abstract class AbstractType implements
Comparator, Assignm
// This assumes that no empty values are passed
public void writeValue(V value, ValueAccessor accessor,
DataOutputPlus out) throws IOException
{
-assert !accessor.isEmpty(value);
-if (valueLengthIfFixed() >= 0)
-accessor.write(value, out);
+assert !accessor.isEmpty(value) : "bytes should not be empty for type
" + this;
+int expectedValueLength = valueLengthIfFixed();
+if (expectedValueLength >= 0)
+{
+int actualValueLength = accessor.size(value);
+if (actualValueLength == expectedValueLength)
+accessor.write(value, out);
+else
+throw new IOException(String.format("Expected exactly %d
bytes, but was %d",
+expectedValueLength,
actualValueLength));
+}
else
+{
accessor.writeWithVIntLength(value, out);
+}
}
public long writtenLength(ByteBuffer value)
@@ -451,7 +461,7 @@ public abstract class AbstractType implements
Comparator, Assignm
{
assert !accessor.isEmpty(value) : "bytes should not be empty for type
" + this;
return valueLengthIfFixed() >= 0
- ? accessor.size(value)
+ ? accessor.size(value) // if the size is wrong, this will be
detected in writeValue
: accessor.sizeWithVIntLength(value);
}
diff --git a/test/unit/org/apache/cassandra/db/ScrubTest.java
b/test/unit/org/apache/cassandra/db/ScrubTest.java
index 6ecaded..343089e 100644
--- a/test/unit/org/apache/cassandra/db/ScrubTest.java
+++ b/test/unit/org/apache/cassandra/db/ScrubTest.java
@@ -56,6 +56,7 @@ import org.apache.cassandra.db.compaction.OperationType;
import org.apache.cassandra.db.compaction.Scrubber;
import org.apache.cassandra.db.lifecycle.LifecycleNewTracker;
import org.apache.cassandra.db.lifecycle.LifecycleTransaction;
+import org.apache.cassandra.db.marshal.Int32Type;
import org.apache.cassandra.db.marshal.LongType;
import org.apache.cassandra.db.marshal.UUIDType;
import org.apache.cassandra.db.partitions.Partition;
@@ -548,7 +549,7 @@ public class ScrubTest
QueryProcessor.process("CREATE TABLE
\"Keyspace1\".test_scrub_validation (a text primary key, b int)",
ConsistencyLevel.ONE);
ColumnFamilyStore cfs2 =
keyspace.getColumnFamilyStore("test_scrub_validation");
-new Mutation(UpdateBuilder.create(cfs2.metadata(),
"key").newRow().add("b", LongType.instance.decompose(1L)).build()).apply();
+new Mutation(UpdateBuilder.create(cfs2.metadata(),
"key").newRow().add("b", Int32Type.instance.decompose(1)).build()).apply();
cfs2.forceBlockingFlush();
CompactionManager.instance.performScrub(cfs2, false, false, 2);
diff --git a/test/unit/org/apache/cassandra/db/marshal/TypeValidationTest.java
b/test/unit/org/apache/cassandra/db/marshal/TypeValidationTest.java
index cdcc5a6..7c0c863 100644
--- a/test/unit/org/apache/cassandra/db/marshal/TypeValidationTest.java
+++ b/test/unit/org/apache/cassandra/db/marshal/TypeValidationTest.java
@@ -1,4 +1,4 @@
-/**
+/*
* 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
@@ -19,16 +19,19 @@
package org.apache.cassandra.db.marshal;
import org.apache.cassandra.Util;
+import org.apache.cassandra.io.util.DataOutputPlus;
import org.apache.cassandra.serializers.MarshalException;
import
[jira] [Commented] (CASSANDRA-11684) Cleanup key ranges during compaction
[ https://issues.apache.org/jira/browse/CASSANDRA-11684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308939#comment-17308939 ] Jeff Jirsa commented on CASSANDRA-11684: Close as a dupe of 5051 In Slack I mentioned this morning: "I had implemented something like 5051 in an early version of the pluggable twcs jar before i realized how terrifying it is given cassandra's lack of actual cluster membership" The TLDR is I've learned a bit since 2015 and what I thought was a good idea then probably requires some technical support to do safely now. > Cleanup key ranges during compaction > > > Key: CASSANDRA-11684 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11684 > Project: Cassandra > Issue Type: Improvement > Components: Local/Compaction >Reporter: Stefan Podkowinski >Priority: Normal > > Currently cleanup is considered an optional, manual operation that users are > told to run to free disk space after a node was affected by topology changes. > However, unmanaged key ranges could also end up on a node through other ways, > e.g. manual added sstable files by an admin. > I'm also not sure unmanaged data is really that harmless and cleanup should > really be optional, if you don't need to reclaim the disk space. When it > comes to repairs, users are expected to purge a node after downtime in case > it was not fully covered by a repair within gc_grace afterwards, in order to > avoid re-introducing deleted data. But the same could happen with unmanaged > data, e.g. after topology changes activate unmanaged ranges again or after > restoring backups. > I'd therefor suggest to avoid rewriting key ranges no longer belonging to a > node and older than gc_grace during compactions. > Maybe we could also introduce another CLEANUP_COMPACTION operation to find > candidates based on SSTable.first/last in case we don't have pending regular > or tombstone compactions. -- 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-16500) Missing validation in AbstractType.writeValue():
[
https://issues.apache.org/jira/browse/CASSANDRA-16500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308930#comment-17308930
]
Ekaterina Dimitrova edited comment on CASSANDRA-16500 at 3/25/21, 7:50 PM:
---
I think you already have a second committer review +1 (congrats one more time
[~Bereng]) so in order to speed up the CI cleaning I will commit this now. :)
was (Author: e.dimitrova):
I think you need a second committer review +1 (congrats one more time
[~Bereng]) so in order to speed up the CI cleaning I will commit this now. :)
> Missing validation in AbstractType.writeValue():
>
>
> Key: CASSANDRA-16500
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16500
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Other
>Reporter: Benjamin Lerer
>Assignee: Alexandre Dutra
>Priority: Normal
> Fix For: 4.0-rc
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Some validation checks present in {{AbstractType.writeValue()}} in
> {{cassandra-3.11}} are not there in {{trunk}}.
> In 3.11 the checks used assertion. It would make sense to use
> {{IOExceptions}} instead as used in {{AbstractType.readValue()}}.
--
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-16364) Simultaneous bootstrap can cause token collision
[
https://issues.apache.org/jira/browse/CASSANDRA-16364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308934#comment-17308934
]
Brandon Williams commented on CASSANDRA-16364:
--
bq. the workaround to fix this is to avoid parallel bootstrap when using
allocate_tokens_for_local_rf.
I will point out that simultaneous bootstrap is actually not valid after
CASSANDRA-2434, so I don't think this is technically a regression.
> Simultaneous bootstrap can cause token collision
>
>
> Key: CASSANDRA-16364
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16364
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Membership
>Reporter: Paulo Motta
>Priority: Urgent
> Fix For: 4.0.x
>
>
> While raising a 6-node ccm cluster to test 4.0-beta4, 2 nodes chosen the same
> tokens using the default {{allocate_tokens_for_local_rf}}. However they both
> succeeded bootstrap with colliding tokens.
> We were familiar with this issue from CASSANDRA-13701 and CASSANDRA-16079,
> and the workaround to fix this is to avoid parallel bootstrap when using
> {{allocate_tokens_for_local_rf}}.
> However, since this is the default behavior, we should try to detect and
> prevent this situation when possible, since it can break users relying on
> parallel bootstrap behavior.
> I think we could prevent this as following:
> 1. announce intent to bootstrap via gossip (ie. add node on gossip without
> token information)
> 2. wait for gossip to settle for a longer period (ie. ring delay)
> 3. allocate tokens (if multiple bootstrap attempts are detected, tie break
> via node-id)
> 4. broadcast tokens and move on with bootstrap
--
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-16500) Missing validation in AbstractType.writeValue():
[
https://issues.apache.org/jira/browse/CASSANDRA-16500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308930#comment-17308930
]
Ekaterina Dimitrova edited comment on CASSANDRA-16500 at 3/25/21, 7:39 PM:
---
I think you need a second committer review +1 (congrats one more time
[~Bereng]) so in order to speed up the CI cleaning I will commit this now. :)
was (Author: e.dimitrova):
I think you need a second committer review +1 (congrats one more time [~Bereng]
) so in order to speed up the CI cleaning I will commit this now. :)
> Missing validation in AbstractType.writeValue():
>
>
> Key: CASSANDRA-16500
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16500
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Other
>Reporter: Benjamin Lerer
>Assignee: Alexandre Dutra
>Priority: Normal
> Fix For: 4.0-rc
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Some validation checks present in {{AbstractType.writeValue()}} in
> {{cassandra-3.11}} are not there in {{trunk}}.
> In 3.11 the checks used assertion. It would make sense to use
> {{IOExceptions}} instead as used in {{AbstractType.readValue()}}.
--
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-16500) Missing validation in AbstractType.writeValue():
[
https://issues.apache.org/jira/browse/CASSANDRA-16500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308930#comment-17308930
]
Ekaterina Dimitrova edited comment on CASSANDRA-16500 at 3/25/21, 7:39 PM:
---
I think you need a second committer review +1 (congrats one more time [~Bereng]
) so in order to speed up the CI cleaning I will commit this now. :)
was (Author: e.dimitrova):
I think you have a second committer review +1 (congrats one more time [~Bereng]
) so in order to speed up the CI cleaning I will commit this now. :)
> Missing validation in AbstractType.writeValue():
>
>
> Key: CASSANDRA-16500
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16500
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Other
>Reporter: Benjamin Lerer
>Assignee: Alexandre Dutra
>Priority: Normal
> Fix For: 4.0-rc
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Some validation checks present in {{AbstractType.writeValue()}} in
> {{cassandra-3.11}} are not there in {{trunk}}.
> In 3.11 the checks used assertion. It would make sense to use
> {{IOExceptions}} instead as used in {{AbstractType.readValue()}}.
--
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-16500) Missing validation in AbstractType.writeValue():
[
https://issues.apache.org/jira/browse/CASSANDRA-16500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-16500:
Status: Ready to Commit (was: Review In Progress)
> Missing validation in AbstractType.writeValue():
>
>
> Key: CASSANDRA-16500
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16500
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Other
>Reporter: Benjamin Lerer
>Assignee: Alexandre Dutra
>Priority: Normal
> Fix For: 4.0-rc
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Some validation checks present in {{AbstractType.writeValue()}} in
> {{cassandra-3.11}} are not there in {{trunk}}.
> In 3.11 the checks used assertion. It would make sense to use
> {{IOExceptions}} instead as used in {{AbstractType.readValue()}}.
--
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-16500) Missing validation in AbstractType.writeValue():
[
https://issues.apache.org/jira/browse/CASSANDRA-16500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308930#comment-17308930
]
Ekaterina Dimitrova commented on CASSANDRA-16500:
-
I think you have a second committer review +1 (congrats one more time [~Bereng]
) so in order to speed up the CI cleaning I will commit this now. :)
> Missing validation in AbstractType.writeValue():
>
>
> Key: CASSANDRA-16500
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16500
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Other
>Reporter: Benjamin Lerer
>Assignee: Alexandre Dutra
>Priority: Normal
> Fix For: 4.0-rc
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Some validation checks present in {{AbstractType.writeValue()}} in
> {{cassandra-3.11}} are not there in {{trunk}}.
> In 3.11 the checks used assertion. It would make sense to use
> {{IOExceptions}} instead as used in {{AbstractType.readValue()}}.
--
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-16495) Scheduled (Delayed) Schema Pull Tasks May Run After MIGRATION Stage Shutdown During Decommission
[
https://issues.apache.org/jira/browse/CASSANDRA-16495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-16495:
Test and Documentation Plan:
https://issues.apache.org/jira/browse/CASSANDRA-16495?focusedCommentId=17308927=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17308927
Status: Patch Available (was: In Progress)
> Scheduled (Delayed) Schema Pull Tasks May Run After MIGRATION Stage Shutdown
> During Decommission
>
>
> Key: CASSANDRA-16495
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16495
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Startup and Shutdown
>Reporter: Caleb Rackliffe
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0-rc
>
>
> A new test added in CASSANDRA-16181 stumbled across this, although it doesn’t
> happen consistently. When [failure
> occurs|https://app.circleci.com/pipelines/github/maedhroz/cassandra/235/workflows/eb8133ce-9373-4136-b404-ceca167353f6/jobs/1355/tests],
> it appears to be because a delayed schema pull happens after decommission
> shuts down the MIGRATION stage’s thread pool.
> {noformat}
> ERROR [node1_isolatedExecutor:1] node1 2021-02-15 19:35:36,284
> CassandraDaemon.java:579 - Exception in thread
> Thread[node1_NonPeriodicTasks:1,5,node1]
> java.util.concurrent.RejectedExecutionException: ThreadPoolExecutor has shut
> down at
> org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor$1.rejectedExecution(DebuggableThreadPoolExecutor.java:72)
>
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:825)
>
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1355)
>
> at
> org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor.execute(DebuggableThreadPoolExecutor.java:176)
>
> at
> java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118)
> at org.apache.cassandra.concurrent.Stage.submit(Stage.java:129)
> at
> org.apache.cassandra.schema.MigrationCoordinator.lambda$scheduleSchemaPull$2(MigrationCoordinator.java:362)
>
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
>
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
>
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
>
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
>
> at java.base/java.lang.Thread.run(Thread.java:834)
> {noformat}
> A fix might be as simple as shutting down ScheduledExecutors.nonPeriodicTasks
> in StorageService#decommission(). See the original discussion
> [here|https://issues.apache.org/jira/browse/CASSANDRA-16181?focusedCommentId=17293329=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17293329].
--
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-16495) Scheduled (Delayed) Schema Pull Tasks May Run After MIGRATION Stage Shutdown During Decommission
[
https://issues.apache.org/jira/browse/CASSANDRA-16495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308927#comment-17308927
]
Ekaterina Dimitrova commented on CASSANDRA-16495:
-
I just submitted a patch
[here|https://github.com/ekaterinadimitrova2/cassandra/commit/99840c80523a571182abaef495f4ad55223c2291]
for trunk. Jenkins CI triggered
[here|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/507/]
I can't really reproduce it and the patch is based only on code analysis, but
from what I see I agree with you [~maedhroz]
Wondering whether to port it also to 3.0 and 3.11
> Scheduled (Delayed) Schema Pull Tasks May Run After MIGRATION Stage Shutdown
> During Decommission
>
>
> Key: CASSANDRA-16495
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16495
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Startup and Shutdown
>Reporter: Caleb Rackliffe
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0-rc
>
>
> A new test added in CASSANDRA-16181 stumbled across this, although it doesn’t
> happen consistently. When [failure
> occurs|https://app.circleci.com/pipelines/github/maedhroz/cassandra/235/workflows/eb8133ce-9373-4136-b404-ceca167353f6/jobs/1355/tests],
> it appears to be because a delayed schema pull happens after decommission
> shuts down the MIGRATION stage’s thread pool.
> {noformat}
> ERROR [node1_isolatedExecutor:1] node1 2021-02-15 19:35:36,284
> CassandraDaemon.java:579 - Exception in thread
> Thread[node1_NonPeriodicTasks:1,5,node1]
> java.util.concurrent.RejectedExecutionException: ThreadPoolExecutor has shut
> down at
> org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor$1.rejectedExecution(DebuggableThreadPoolExecutor.java:72)
>
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:825)
>
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1355)
>
> at
> org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor.execute(DebuggableThreadPoolExecutor.java:176)
>
> at
> java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118)
> at org.apache.cassandra.concurrent.Stage.submit(Stage.java:129)
> at
> org.apache.cassandra.schema.MigrationCoordinator.lambda$scheduleSchemaPull$2(MigrationCoordinator.java:362)
>
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
>
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
>
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
>
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
>
> at java.base/java.lang.Thread.run(Thread.java:834)
> {noformat}
> A fix might be as simple as shutting down ScheduledExecutors.nonPeriodicTasks
> in StorageService#decommission(). See the original discussion
> [here|https://issues.apache.org/jira/browse/CASSANDRA-16181?focusedCommentId=17293329=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17293329].
--
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-11684) Cleanup key ranges during compaction
[ https://issues.apache.org/jira/browse/CASSANDRA-11684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308915#comment-17308915 ] Paulo Motta commented on CASSANDRA-11684: - bq. I think Jeff is speaking to the concept here Yeah I'm curious on why he claimed this is unsafe now since he supported it on CASSANDRA-5051. But it seems there could be some edge cases during network partitions. Any objection to closing this as dupe of CASSANDRA-5051? > Cleanup key ranges during compaction > > > Key: CASSANDRA-11684 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11684 > Project: Cassandra > Issue Type: Improvement > Components: Local/Compaction >Reporter: Stefan Podkowinski >Priority: Normal > > Currently cleanup is considered an optional, manual operation that users are > told to run to free disk space after a node was affected by topology changes. > However, unmanaged key ranges could also end up on a node through other ways, > e.g. manual added sstable files by an admin. > I'm also not sure unmanaged data is really that harmless and cleanup should > really be optional, if you don't need to reclaim the disk space. When it > comes to repairs, users are expected to purge a node after downtime in case > it was not fully covered by a repair within gc_grace afterwards, in order to > avoid re-introducing deleted data. But the same could happen with unmanaged > data, e.g. after topology changes activate unmanaged ranges again or after > restoring backups. > I'd therefor suggest to avoid rewriting key ranges no longer belonging to a > node and older than gc_grace during compactions. > Maybe we could also introduce another CLEANUP_COMPACTION operation to find > candidates based on SSTable.first/last in case we don't have pending regular > or tombstone compactions. -- 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-11684) Cleanup key ranges during compaction
[ https://issues.apache.org/jira/browse/CASSANDRA-11684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308912#comment-17308912 ] Brandon Williams commented on CASSANDRA-11684: -- I think Jeff is speaking to the concept here, which seems like a duplicate of CASSANDRA-5051. > Cleanup key ranges during compaction > > > Key: CASSANDRA-11684 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11684 > Project: Cassandra > Issue Type: Improvement > Components: Local/Compaction >Reporter: Stefan Podkowinski >Priority: Normal > > Currently cleanup is considered an optional, manual operation that users are > told to run to free disk space after a node was affected by topology changes. > However, unmanaged key ranges could also end up on a node through other ways, > e.g. manual added sstable files by an admin. > I'm also not sure unmanaged data is really that harmless and cleanup should > really be optional, if you don't need to reclaim the disk space. When it > comes to repairs, users are expected to purge a node after downtime in case > it was not fully covered by a repair within gc_grace afterwards, in order to > avoid re-introducing deleted data. But the same could happen with unmanaged > data, e.g. after topology changes activate unmanaged ranges again or after > restoring backups. > I'd therefor suggest to avoid rewriting key ranges no longer belonging to a > node and older than gc_grace during compactions. > Maybe we could also introduce another CLEANUP_COMPACTION operation to find > candidates based on SSTable.first/last in case we don't have pending regular > or tombstone compactions. -- 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-13517) dtest failure in paxos_tests.TestPaxos.contention_test_many_threads
[
https://issues.apache.org/jira/browse/CASSANDRA-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Holmberg updated CASSANDRA-13517:
--
Description:
Error Message
AssertionError: value=278, errors=22, retries=2888 assert (278 == (300 * 1))
{noformat}
> assert (value == threads * iterations) and (errors == 0), "value={},
> errors={}, retries={}".format(value, errors, retries)
E AssertionError: value=278, errors=22, retries=2888 E assert (278 == (300 *
1))
paxos_test.py:195: AssertionError
{noformat}
was:
Error Message
AssertionError: value=278, errors=22, retries=2888 assert (278 == (300 * 1))
{noformat}
> assert (value == threads * iterations) and (errors == 0), "value={},
> errors={}, retries={}".format(value, errors, retries) E AssertionError:
> value=278, errors=22, retries=2888 E assert (278 == (300 * 1))
> paxos_test.py:195: AssertionError
{noformat}
> dtest failure in paxos_tests.TestPaxos.contention_test_many_threads
> ---
>
> Key: CASSANDRA-13517
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13517
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Ariel Weisberg
>Assignee: Jason Brown
>Priority: Normal
> Labels: dtest, test-failure, test-failure-fresh
> Fix For: 4.0-rc
>
> Attachments: test_failure.txt
>
>
> Error Message
> AssertionError: value=278, errors=22, retries=2888 assert (278 == (300 * 1))
> {noformat}
> > assert (value == threads * iterations) and (errors == 0), "value={},
> > errors={}, retries={}".format(value, errors, retries)
> E AssertionError: value=278, errors=22, retries=2888 E assert (278 == (300 *
> 1))
> paxos_test.py:195: AssertionError
> {noformat}
>
--
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-16190) Add tests for streaming metrics
[ https://issues.apache.org/jira/browse/CASSANDRA-16190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-16190: Reviewers: Ekaterina Dimitrova > Add tests for streaming metrics > --- > > Key: CASSANDRA-16190 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16190 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/python >Reporter: Benjamin Lerer >Assignee: Benjamin Lerer >Priority: Normal > Fix For: 4.0-rc > > > We currently have no tests to checks the streaming metrics -- 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-13517) dtest failure in paxos_tests.TestPaxos.contention_test_many_threads
[
https://issues.apache.org/jira/browse/CASSANDRA-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Holmberg updated CASSANDRA-13517:
--
Description:
Error Message
AssertionError: value=278, errors=22, retries=2888 assert (278 == (300 * 1))
{noformat}
> assert (value == threads * iterations) and (errors == 0), "value={},
> errors={}, retries={}".format(value, errors, retries) E AssertionError:
> value=278, errors=22, retries=2888 E assert (278 == (300 * 1))
> paxos_test.py:195: AssertionError
{noformat}
was:See attachment for details
> dtest failure in paxos_tests.TestPaxos.contention_test_many_threads
> ---
>
> Key: CASSANDRA-13517
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13517
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Ariel Weisberg
>Assignee: Jason Brown
>Priority: Normal
> Labels: dtest, test-failure, test-failure-fresh
> Fix For: 4.0-rc
>
> Attachments: test_failure.txt
>
>
> Error Message
> AssertionError: value=278, errors=22, retries=2888 assert (278 == (300 * 1))
> {noformat}
> > assert (value == threads * iterations) and (errors == 0), "value={},
> > errors={}, retries={}".format(value, errors, retries) E AssertionError:
> > value=278, errors=22, retries=2888 E assert (278 == (300 * 1))
> > paxos_test.py:195: AssertionError
> {noformat}
>
--
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-13517) dtest failure in paxos_tests.TestPaxos.contention_test_many_threads
[ https://issues.apache.org/jira/browse/CASSANDRA-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Holmberg updated CASSANDRA-13517: -- Resolution: (was: Cannot Reproduce) Status: Open (was: Resolved) This test appears to still be flaky. > dtest failure in paxos_tests.TestPaxos.contention_test_many_threads > --- > > Key: CASSANDRA-13517 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13517 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Ariel Weisberg >Assignee: Jason Brown >Priority: Normal > Labels: dtest, test-failure, test-failure-fresh > Attachments: test_failure.txt > > > See attachment for details -- 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-13517) dtest failure in paxos_tests.TestPaxos.contention_test_many_threads
[ https://issues.apache.org/jira/browse/CASSANDRA-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Holmberg updated CASSANDRA-13517: -- Fix Version/s: 4.0-rc > dtest failure in paxos_tests.TestPaxos.contention_test_many_threads > --- > > Key: CASSANDRA-13517 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13517 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Ariel Weisberg >Assignee: Jason Brown >Priority: Normal > Labels: dtest, test-failure, test-failure-fresh > Fix For: 4.0-rc > > Attachments: test_failure.txt > > > See attachment for details -- 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-11684) Cleanup key ranges during compaction
[ https://issues.apache.org/jira/browse/CASSANDRA-11684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308865#comment-17308865 ] Paulo Motta commented on CASSANDRA-11684: - [~jjirsa] can you elaborate on why this is an issue? Unless I'm missing something this seems to be a duplicate of CASSANDRA-5051. > Cleanup key ranges during compaction > > > Key: CASSANDRA-11684 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11684 > Project: Cassandra > Issue Type: Improvement > Components: Local/Compaction >Reporter: Stefan Podkowinski >Priority: Normal > > Currently cleanup is considered an optional, manual operation that users are > told to run to free disk space after a node was affected by topology changes. > However, unmanaged key ranges could also end up on a node through other ways, > e.g. manual added sstable files by an admin. > I'm also not sure unmanaged data is really that harmless and cleanup should > really be optional, if you don't need to reclaim the disk space. When it > comes to repairs, users are expected to purge a node after downtime in case > it was not fully covered by a repair within gc_grace afterwards, in order to > avoid re-introducing deleted data. But the same could happen with unmanaged > data, e.g. after topology changes activate unmanaged ranges again or after > restoring backups. > I'd therefor suggest to avoid rewriting key ranges no longer belonging to a > node and older than gc_grace during compactions. > Maybe we could also introduce another CLEANUP_COMPACTION operation to find > candidates based on SSTable.first/last in case we don't have pending regular > or tombstone compactions. -- 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-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2
[ https://issues.apache.org/jira/browse/CASSANDRA-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308847#comment-17308847 ] Rahul Singh commented on CASSANDRA-16536: - PR updated [https://github.com/apache/cassandra-website/pull/39] > BLOG - Post about Cassandra & Kubernetes - SIG Update #2 > > > Key: CASSANDRA-16536 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16536 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Michael Semb Wever >Priority: High > Labels: pull-request-available > Fix For: 4.0-beta5, 4.0 > > Attachments: image-2021-03-24-18-57-08-450.png > > > We're getting another update up for the Cassandra & Kubernetes SIG > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown] > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-16533) The two tests in NetstatsBootstrapWithEntireSSTablesCompressionStreamingTest are flaky
[
https://issues.apache.org/jira/browse/CASSANDRA-16533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexandre Dutra reassigned CASSANDRA-16533:
---
Assignee: Alexandre Dutra
> The two tests in NetstatsBootstrapWithEntireSSTablesCompressionStreamingTest
> are flaky
> ---
>
> Key: CASSANDRA-16533
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16533
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Alexandre Dutra
>Priority: Normal
> Fix For: 4.0-rc
>
>
> The issue is when there are interleaving logs, then the filter
> [here|https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/test/AbstractNetstatsStreaming.java#L142-L148]
> doesn't help.
> I managed to reproduce the issue only once.
> But I found logs from old CircleCI
> [run|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/705/workflows/c3534f6a-071e-428c-9a4d-0a1e08f23257/jobs/3866/artifacts].
> Please see
> [logs/org.apache.cassandra.distributed.test.NetstatsBootstrapWithoutEntireSSTablesCompressionStreamingTest///system.log|https://3866-218559411-gh.circle-artifacts.com/0/logs/org.apache.cassandra.distributed.test.NetstatsBootstrapWithoutEntireSSTablesCompressionStreamingTest/%3Cmain%3E/%3Cmain%3E/system.log]
> The excerpt that shows what I am talking about:
>
> {code:java}
> DEBUG [node1_NettyStreaming-Outbound-/127.0.0.2.7012:1] node1 2021-03-17
> 22:41:21,057 CassandraCompressedStreamWriter.java:102 - [Stream
> #e3d93810-8771-11eb-a0f1-f756ef192fe7] Finished streaming file
> /tmp/dtests9118120876279144235/node1/data1/netstats_test/test_table-c0f7eda0877111ebbfc147ef604f6105/na-11-big-Data.db
> to /127.0.0.2:7012, bytesTransferred = 66.646KiB, totalSize = 66.646KiB
> Bootstrap e3d93810-8771-11eb-a0f1-f756ef192fe7
> /127.0.0.2
> Sending 15 files, 1339433 bytes total. Already sent 3 files (20.00%), 197286
> bytes total (14.73%)
> DEBUG [Stream-Deserializer-/127.0.0.1:7012-2bcb5810] node2 2021-03-17
> 22:41:21,057 StreamingInboundHandler.java:187 - [Stream
> #e3d93810-8771-11eb-a0f1-f756ef192fe7 channel: 2bcb5810] Received
> IncomingStreamMessage{header=Header (tableId:
> c0f7eda0-8771-11eb-bfc1-47ef604f6105, #1, repairedAt: 0, pendingRepair: null,
> sendByFollower: true),
> stream=CassandraIncomingFile{sstable=netstats_test/test_table}}
> DEBUG [Stream-Deserializer-/127.0.0.1:7012-2bcb5810] node2 2021-03-17
> 22:41:21,058 NettyStreamingMessageSender.java:258 - [Stream
> #e3d93810-8771-11eb-a0f1-f756ef192fe7 channel: 09fdf87e] Sending Received
> (c0f7eda0-8771-11eb-bfc1-47ef604f6105, #1)
>
> /tmp/dtests9118120876279144235/node1/data1/system_auth/roles-5bc52802de2535edaeab188eecebb090/na-2-big-Data.db
> 102/102 bytes (100%) sent to idx:0/127.0.0.2
>
> /tmp/dtests9118120876279144235/node1/data1/netstats_test/test_table-c0f7eda0877111ebbfc147ef604f6105/na-11-big-Data.db
> 65536/68246 bytes (96%) sent to idx:0/127.0.0.2
>
> /tmp/dtests9118120876279144235/node1/data1/netstats_test/test_table-c0f7eda0877111ebbfc147ef604f6105/na-20-big-Data.db
> 62836/62836 bytes (100%) sent to idx:0/127.0.0.2
>
> /tmp/dtests9118120876279144235/node1/data1/netstats_test/test_table-c0f7eda0877111ebbfc147ef604f6105/na-17-big-Data.db
> 68812/68812 bytes (100%) sent to idx:0/127.0.0.2
> Read Repair Statistics:
> Attempted: 0
> Mismatch (Blocking): 0
> Mismatch (Background): 0
> Pool Name DEBUG [node1_NettyStreaming-Outbound-/127.0.0.2.7012:1] node1
> 2021-03-17 22:41:21,058 CassandraCompressedStreamWriter.java:64 - [Stream
> #e3d93810-8771-11eb-a0f1-f756ef192fe7] Start streaming file
> /tmp/dtests9118120876279144235/node1/data1/netstats_test/test_table-c0f7eda0877111ebbfc147ef604f6105/na-8-big-Data.db
> to /127.0.0.2:7012, repairedAt = 0, totalSize = 67504
> Active PendingDEBUG [Stream-Deserializer-/127.0.0.1:7012-2bcb5810] node2
> 2021-03-17 22:41:21,058 StreamReceiveTask.java:88 - received 2 of 14 total
> files, 131648 of total bytes 68812
> Completed Dropped
> Large messages n/a 0 0 0
> Small messages n/a 0 1 0
> DEBUG [node1_NettyStreaming-Outbound-/127.0.0.2.7012:1] node1 2021-03-17
> 22:41:21,058 CassandraCompressedStreamWriter.java:81 - [Stream
> #e3d93810-8771-11eb-a0f1-f756ef192fe7] Writing section 0 with length 67504 to
> stream.
> Gossip messages n/a 0 54 0
> INFO [pool-2-thread-2] 2021-03-17 22:41:21,567 /127.0.0.1:7012 Mode:
> NORMAL
>
> {code}
> The line _Pool Name Active Pending Completed Dropped_ is split into three
> parts due to DEBUG logs interleaving and the filter doesn't remove _Completed
> Dropped_ which is added to the results
>
[jira] [Commented] (CASSANDRA-16190) Add tests for streaming metrics
[ https://issues.apache.org/jira/browse/CASSANDRA-16190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308823#comment-17308823 ] Benjamin Lerer commented on CASSANDRA-16190: [~edimitrova] I think you were involve in CASSANDRA-15656. Do you mind reviewing that ticket? > Add tests for streaming metrics > --- > > Key: CASSANDRA-16190 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16190 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/python >Reporter: Benjamin Lerer >Assignee: Benjamin Lerer >Priority: Normal > Fix For: 4.0-rc > > > We currently have no tests to checks the streaming metrics -- 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-16190) Add tests for streaming metrics
[ https://issues.apache.org/jira/browse/CASSANDRA-16190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-16190: --- Test and Documentation Plan: Ad new in-jvm tests for streaming metrics Status: Patch Available (was: In Progress) > Add tests for streaming metrics > --- > > Key: CASSANDRA-16190 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16190 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/python >Reporter: Benjamin Lerer >Assignee: Benjamin Lerer >Priority: Normal > Fix For: 4.0-rc > > > We currently have no tests to checks the streaming metrics -- 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-16190) Add tests for streaming metrics
[ https://issues.apache.org/jira/browse/CASSANDRA-16190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308820#comment-17308820 ] Benjamin Lerer commented on CASSANDRA-16190: [~cscotta] I hit an issue while implementing those tests with the metrics added by CASSANDRA-15656. It seems that they are not updated in every cases. The following [PR|https://github.com/apache/cassandra/pull/941] fix the problem and add the missing tests. Circle-CI [j8|https://app.circleci.com/pipelines/github/blerer/cassandra/116/workflows/4edd0829-c1ee-4ca3-b21d-85cb35da08b9] and [j11|https://app.circleci.com/pipelines/github/blerer/cassandra/116/workflows/795f14d7-9659-4534-8182-5ca0966d63ef] > Add tests for streaming metrics > --- > > Key: CASSANDRA-16190 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16190 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/python >Reporter: Benjamin Lerer >Assignee: Benjamin Lerer >Priority: Normal > Fix For: 4.0-rc > > > We currently have no tests to checks the streaming metrics -- 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-16236) Fix flaky testTrackMaxDeletionTime
[ https://issues.apache.org/jira/browse/CASSANDRA-16236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andres de la Peña reassigned CASSANDRA-16236: - Assignee: Andres de la Peña > Fix flaky testTrackMaxDeletionTime > -- > > Key: CASSANDRA-16236 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16236 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Brandon Williams >Assignee: Andres de la Peña >Priority: Normal > Fix For: 4.0-rc > > Attachments: Screenshot 2021-03-23 at 20.12.18.png > > > * > testTrackMaxDeletionTime - org.apache.cassandra.io.sstable.SSTableMetadataTest > > junit.framework.AssertionFailedError: expected:<1.6038784E9> but > was:<1.60387827E9> > at > org.apache.cassandra.io.sstable.SSTableMetadataTest.testTrackMaxDeletionTime(SSTableMetadataTest.java:102) > https://app.circleci.com/pipelines/github/bereng/cassandra/160/workflows/6cb80410-b398-477c-b4c9-cc7369785869/jobs/1317 -- 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-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2
[ https://issues.apache.org/jira/browse/CASSANDRA-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308807#comment-17308807 ] Rahul Singh commented on CASSANDRA-16536: - acknowledged will make updates and do update the pull request > BLOG - Post about Cassandra & Kubernetes - SIG Update #2 > > > Key: CASSANDRA-16536 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16536 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Michael Semb Wever >Priority: High > Labels: pull-request-available > Fix For: 4.0-beta5, 4.0 > > Attachments: image-2021-03-24-18-57-08-450.png > > > We're getting another update up for the Cassandra & Kubernetes SIG > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown] > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16532) Fix flaky testSkipScrubCorruptedCounterRowWithTool
[
https://issues.apache.org/jira/browse/CASSANDRA-16532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308766#comment-17308766
]
Andres de la Peña commented on CASSANDRA-16532:
---
I suspect that those failures with {{testScrubOutOfOrder}} and compression are
also related to the tests reusing the tables and calling {{clearUnsafe}}.
[In this
commit|https://github.com/adelapena/cassandra/commit/b19711ac8d6f163113ba8f49762e2959996adfd7]
I have tried to unify the two coexistent initialization methods
({{defineSchema}} and {{toolTestingSetup}}) into a single method annotated with
JUnit's {{@Begin}}. This way every test uses its own dedicated keyspace and we
don't need the calls to {{clearUnsafe}}. I have also done some minor cleaning
to reduce the number of tables per keyspace and to get rid of most of the
warnings across {{ScrubTest}}.
With these changes it seems that the test suite passes 400 runs in the
multiplexer with compression
([here|https://jenkins-dse.build.dsinternal.org/view/Parameterized/job/parameterized-testall/737/]
and
[here|https://jenkins-dse.build.dsinternal.org/view/Parameterized/job/parameterized-testall/737/]),
and 200 more runs without compression
([here|https://jenkins-dse.build.dsinternal.org/view/Parameterized/job/parameterized-testall/739/]).
> Fix flaky testSkipScrubCorruptedCounterRowWithTool
> --
>
> Key: CASSANDRA-16532
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16532
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Berenguer Blasi
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 4.0-rc
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Fix flaky
> [testSkipScrubCorruptedCounterRowWithTool|https://ci-cassandra.apache.org/job/Cassandra-trunk/365/testReport/junit/org.apache.cassandra.db/ScrubTest/testSkipScrubCorruptedCounterRowWithTool_compression/]
--
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-16538) Cannot run restore for a list of Cassandra nodes
[
https://issues.apache.org/jira/browse/CASSANDRA-16538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-16538:
-
Resolution: Invalid
Status: Resolved (was: Triage Needed)
Hi Yolanda,
This jira is for tracking bugs in the Apache Cassandra software, and doesn't
make for a good vehicle support. I recommend contacting the community through
Slack or the mailing list: https://cassandra.apache.org/community/
> Cannot run restore for a list of Cassandra nodes
>
>
> Key: CASSANDRA-16538
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16538
> Project: Cassandra
> Issue Type: Bug
>Reporter: Yolanda Tang
>Priority: Normal
>
> Hi,
>
> When switching to use Cassandra medus to fulfill our work for node data
> restore, we encountered some issues.
> When using pssh remotely we are getting timeout issue, when trying the
> command on one node of Cassandra, we get
>
> {code:java}
> pssh -H medusa -vvv restore-node --in-place --no-verify --backup-name
> 2021031803 --temp-dir /tmp/medusa-job-bd8a39ca-a5ea-4a3a-820f-0fa6ddc5130a
> [1] 06:52:08 [FAILURE] sha8392 Timed out, Killed by signal 9
> When further looking into the timeout issue, we get logs as
> [2021-03-25 02:23:50,113] DEBUG: https://s3.cn-north-1.amazonaws.com.cn:443
> "GET /XX/XX/10.44.XX.XX/2021031803/meta/schema.cql?Version=2006-03-01
> HTTP/1.1" 200 24005[2021-03-25 02:23:50,114] DEBUG: [Storage] Getting object
> sre_dev_cass_sha/10.44.79.15/2021031803/meta/tokenmap.json
> [2021-03-25 02:23:50,151] DEBUG: https://s3.cn-north-1.amazonaws.com.cn:443
> "HEAD /XX HTTP/1.1" 200 0[2021-03-25 02:23:50,201] DEBUG:
> https://s3.cn-north-1.amazonaws.com.cn:443 "HEAD
> /XX/XX/10.44.79.15/2021031803/meta/tokenmap.json HTTP/1.1" 200 0[2021-03-25
> 02:23:50,202] DEBUG: Downloading
> /tmp/medusa-job-bd8a39ca-a5ea-4a3a-820f-0fa6ddc5130a/medusa-restore-197b6c82-4cd5-4c5b-b3c2-9d98863c1b3f
> as single part
> [2021-03-25 02:23:50,254] DEBUG: https://s3.cn-north-1.amazonaws.com.cn:443
> "GET /XX/XX/10.44.XX.XX/2021031803/meta/tokenmap.json?Version=2006-03-01
> HTTP/1.1" 200 1535[2021-03-25 02:23:50,255] INFO: Stopping Cassandra
> + /usr/bin/nodetool u cassandra -pw if9te8ohKei9xaep drain+ /usr/bin/nodetool
> -u cassandra -pw if9te8ohKei9xaep drainerror: null- StackTrace
> --java.io.EOFException at
> java.io.DataInputStream.readByte(DataInputStream.java:267) at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:222) at
> sun.rmi.server.UnicastRef.invoke(UnicastRef.java:161) at
> com.sun.jmx.remote.internal.PRef.invoke(Unknown Source) at
> javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(Unknown Source) at
> javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:1020)
> at
> javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:298)
> at com.sun.proxy.$Proxy8.drain(Unknown Source) at
> org.apache.cassandra.tools.NodeProbe.drain(NodeProbe.java:371) at
> org.apache.cassandra.tools.nodetool.Drain.execute(Drain.java:36) at
> org.apache.cassandra.tools.NodeTool$NodeToolCmd.run(NodeTool.java:244) at
> org.apache.cassandra.tools.NodeTool.main(NodeTool.java:158)
> + ls -l /var/run/cassandra/cassandra.pidls: cannot access
> /var/run/cassandra/cassandra.pid: No such file or directory+ sleep 10+ echo
> -n 'Shutdown Cassandra: 'Shutdown Cassandra: ++ cat
> /var/run/cassandra/cassandra.pidcat: /var/run/cassandra/cassandra.pid: No
> such file or directory+ su cassandra -c 'kill 'kill: usage: kill [-s sigspec
> | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]++ seq 40+ for
> t in '`seq 40`'+ /etc/init.d/cassandra status+ break+ sleep 5+ echo OKOK
> {code}
> But we can get a successful run of the command on one node for
> {code:java}
> export LC_ALL=en_US.UTF-8; export LANG=en_US.UTF-8; export
> https_proxy=http://proxy.XX:3128 ; export
> PATH=$PATH:/usr/share/cassandra-medusa/bin; sudo su; mkdir
> /tmp/medusa-job-bd8a39ca-a5ea-4a3a-820f-0fa6ddc5130a; cd
> /tmp/medusa-job-bd8a39ca-a5ea-4a3a-820f-0fa6ddc5130a;
> medusa-wrapper sudo
> medusa -vvv restore-node --in-place --no-verify --backup-name 2021031803
> --temp-dir /tmp/medusa-job-bd8a39ca-a5ea-4a3a-820f-0fa6ddc5130a{code}
> We are running the command on
> {code:java}
> uname -a
> Linux 5.3.0-53-generic #47~18.04.1-Ubuntu SMP Thu May 7 13:10:50 UTC
> 2020 x86_64 x86_64 x86_64 GNU/Linux{code}
> Could you please have a look at the issue?
> Thanks
--
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-16538) Cannot run restore for a list of Cassandra nodes
[
https://issues.apache.org/jira/browse/CASSANDRA-16538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308717#comment-17308717
]
Brandon Williams edited comment on CASSANDRA-16538 at 3/25/21, 2:32 PM:
Hi Yolanda,
This jira is for tracking bugs in the Apache Cassandra software, and doesn't
make for a good vehicle for support. I recommend contacting the community
through Slack or the mailing list: https://cassandra.apache.org/community/
was (Author: brandon.williams):
Hi Yolanda,
This jira is for tracking bugs in the Apache Cassandra software, and doesn't
make for a good vehicle support. I recommend contacting the community through
Slack or the mailing list: https://cassandra.apache.org/community/
> Cannot run restore for a list of Cassandra nodes
>
>
> Key: CASSANDRA-16538
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16538
> Project: Cassandra
> Issue Type: Bug
>Reporter: Yolanda Tang
>Priority: Normal
>
> Hi,
>
> When switching to use Cassandra medus to fulfill our work for node data
> restore, we encountered some issues.
> When using pssh remotely we are getting timeout issue, when trying the
> command on one node of Cassandra, we get
>
> {code:java}
> pssh -H medusa -vvv restore-node --in-place --no-verify --backup-name
> 2021031803 --temp-dir /tmp/medusa-job-bd8a39ca-a5ea-4a3a-820f-0fa6ddc5130a
> [1] 06:52:08 [FAILURE] sha8392 Timed out, Killed by signal 9
> When further looking into the timeout issue, we get logs as
> [2021-03-25 02:23:50,113] DEBUG: https://s3.cn-north-1.amazonaws.com.cn:443
> "GET /XX/XX/10.44.XX.XX/2021031803/meta/schema.cql?Version=2006-03-01
> HTTP/1.1" 200 24005[2021-03-25 02:23:50,114] DEBUG: [Storage] Getting object
> sre_dev_cass_sha/10.44.79.15/2021031803/meta/tokenmap.json
> [2021-03-25 02:23:50,151] DEBUG: https://s3.cn-north-1.amazonaws.com.cn:443
> "HEAD /XX HTTP/1.1" 200 0[2021-03-25 02:23:50,201] DEBUG:
> https://s3.cn-north-1.amazonaws.com.cn:443 "HEAD
> /XX/XX/10.44.79.15/2021031803/meta/tokenmap.json HTTP/1.1" 200 0[2021-03-25
> 02:23:50,202] DEBUG: Downloading
> /tmp/medusa-job-bd8a39ca-a5ea-4a3a-820f-0fa6ddc5130a/medusa-restore-197b6c82-4cd5-4c5b-b3c2-9d98863c1b3f
> as single part
> [2021-03-25 02:23:50,254] DEBUG: https://s3.cn-north-1.amazonaws.com.cn:443
> "GET /XX/XX/10.44.XX.XX/2021031803/meta/tokenmap.json?Version=2006-03-01
> HTTP/1.1" 200 1535[2021-03-25 02:23:50,255] INFO: Stopping Cassandra
> + /usr/bin/nodetool u cassandra -pw if9te8ohKei9xaep drain+ /usr/bin/nodetool
> -u cassandra -pw if9te8ohKei9xaep drainerror: null- StackTrace
> --java.io.EOFException at
> java.io.DataInputStream.readByte(DataInputStream.java:267) at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:222) at
> sun.rmi.server.UnicastRef.invoke(UnicastRef.java:161) at
> com.sun.jmx.remote.internal.PRef.invoke(Unknown Source) at
> javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(Unknown Source) at
> javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:1020)
> at
> javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:298)
> at com.sun.proxy.$Proxy8.drain(Unknown Source) at
> org.apache.cassandra.tools.NodeProbe.drain(NodeProbe.java:371) at
> org.apache.cassandra.tools.nodetool.Drain.execute(Drain.java:36) at
> org.apache.cassandra.tools.NodeTool$NodeToolCmd.run(NodeTool.java:244) at
> org.apache.cassandra.tools.NodeTool.main(NodeTool.java:158)
> + ls -l /var/run/cassandra/cassandra.pidls: cannot access
> /var/run/cassandra/cassandra.pid: No such file or directory+ sleep 10+ echo
> -n 'Shutdown Cassandra: 'Shutdown Cassandra: ++ cat
> /var/run/cassandra/cassandra.pidcat: /var/run/cassandra/cassandra.pid: No
> such file or directory+ su cassandra -c 'kill 'kill: usage: kill [-s sigspec
> | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]++ seq 40+ for
> t in '`seq 40`'+ /etc/init.d/cassandra status+ break+ sleep 5+ echo OKOK
> {code}
> But we can get a successful run of the command on one node for
> {code:java}
> export LC_ALL=en_US.UTF-8; export LANG=en_US.UTF-8; export
> https_proxy=http://proxy.XX:3128 ; export
> PATH=$PATH:/usr/share/cassandra-medusa/bin; sudo su; mkdir
> /tmp/medusa-job-bd8a39ca-a5ea-4a3a-820f-0fa6ddc5130a; cd
> /tmp/medusa-job-bd8a39ca-a5ea-4a3a-820f-0fa6ddc5130a;
> medusa-wrapper sudo
> medusa -vvv restore-node --in-place --no-verify --backup-name 2021031803
> --temp-dir /tmp/medusa-job-bd8a39ca-a5ea-4a3a-820f-0fa6ddc5130a{code}
> We are running the command on
> {code:java}
> uname -a
> Linux 5.3.0-53-generic #47~18.04.1-Ubuntu SMP Thu May 7 13:10:50 UTC
> 2020 x86_64 x86_64 x86_64 GNU/Linux{code}
> Could you please have a look at the
[jira] [Commented] (CASSANDRA-16535) Fail to init Cassandra Startup with an API connected with other cluster machines (3.11.9 version)
[ https://issues.apache.org/jira/browse/CASSANDRA-16535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308712#comment-17308712 ] Brandon Williams commented on CASSANDRA-16535: -- [~yukim] could you kindly do one last windows review? > Fail to init Cassandra Startup with an API connected with other cluster > machines (3.11.9 version) > - > > Key: CASSANDRA-16535 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16535 > Project: Cassandra > Issue Type: Bug > Components: Local/Startup and Shutdown >Reporter: Aramis >Assignee: Aramis >Priority: Normal > Fix For: 3.11.11 > > Attachments: cassandra_modified.ps1, > image-2021-03-24-21-12-32-709.png, image-2021-03-24-21-13-46-704.png > > > The code in the function "VerifyPortsAreAvailable", look for the ports: 7000, > 9042, 7199 and 9160 in the "netstat -an" command output. > > If we have an API connected to the cluster in a node, and we try to start the > execution of cassandra (with that API working, accesing ports 9042 of the > other cluster machines), the output of that command return us that the port > is already in use, and Cassandra´s startup process fails, showing the output > message : "port already in use" in the .log file. > Thus, if we change the code of the function, adding the line: " -and $line > -match "LISTENING" ", just next to the "$line -match "TCP" ", we will only > interrupt the execution if the load port is in the state: "LISTENING", but no > if it´s an active connection on the other node of the cluster. > !image-2021-03-24-21-12-32-709.png|width=470,height=159! > !image-2021-03-24-21-13-46-704.png|width=526,height=119! -- 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-16532) Fix flaky testSkipScrubCorruptedCounterRowWithTool
[ https://issues.apache.org/jira/browse/CASSANDRA-16532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308680#comment-17308680 ] Adam Holmberg commented on CASSANDRA-16532: --- On my part, I agree that merging known fixes and spinning out a different ticket is a good approach. > Fix flaky testSkipScrubCorruptedCounterRowWithTool > -- > > Key: CASSANDRA-16532 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16532 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-rc > > Time Spent: 1.5h > Remaining Estimate: 0h > > Fix flaky > [testSkipScrubCorruptedCounterRowWithTool|https://ci-cassandra.apache.org/job/Cassandra-trunk/365/testReport/junit/org.apache.cassandra.db/ScrubTest/testSkipScrubCorruptedCounterRowWithTool_compression/] -- 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-16535) Fail to init Cassandra Startup with an API connected with other cluster machines (3.11.9 version)
[ https://issues.apache.org/jira/browse/CASSANDRA-16535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aramis updated CASSANDRA-16535: --- Test and Documentation Plan: Specified in post Status: Patch Available (was: Open) https://github.com/amenur/CASSANDRA-16535/blob/main/cassandra_modified.ps1 > Fail to init Cassandra Startup with an API connected with other cluster > machines (3.11.9 version) > - > > Key: CASSANDRA-16535 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16535 > Project: Cassandra > Issue Type: Bug > Components: Local/Startup and Shutdown >Reporter: Aramis >Assignee: Aramis >Priority: Normal > Fix For: 3.11.11 > > Attachments: cassandra_modified.ps1, > image-2021-03-24-21-12-32-709.png, image-2021-03-24-21-13-46-704.png > > > The code in the function "VerifyPortsAreAvailable", look for the ports: 7000, > 9042, 7199 and 9160 in the "netstat -an" command output. > > If we have an API connected to the cluster in a node, and we try to start the > execution of cassandra (with that API working, accesing ports 9042 of the > other cluster machines), the output of that command return us that the port > is already in use, and Cassandra´s startup process fails, showing the output > message : "port already in use" in the .log file. > Thus, if we change the code of the function, adding the line: " -and $line > -match "LISTENING" ", just next to the "$line -match "TCP" ", we will only > interrupt the execution if the load port is in the state: "LISTENING", but no > if it´s an active connection on the other node of the cluster. > !image-2021-03-24-21-12-32-709.png|width=470,height=159! > !image-2021-03-24-21-13-46-704.png|width=526,height=119! -- 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-16236) Fix flaky testTrackMaxDeletionTime
[ https://issues.apache.org/jira/browse/CASSANDRA-16236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17307361#comment-17307361 ] Michael Semb Wever edited comment on CASSANDRA-16236 at 3/25/21, 11:07 AM: --- Failure spotted: - [Cassandra-trunk #368|https://nightlies.apache.org/cassandra/ci-cassandra.apache.org/job/Cassandra-trunk/368/] \\ !Screenshot 2021-03-23 at 20.12.18.png|width=300! Downstream stage job: - [Cassandra-trunk-test-cdc jdk_11 #599|https://nightlies.apache.org/cassandra/ci-cassandra.apache.org/job/Cassandra-trunk-test-cdc/599/] with logs [here|https://nightlies.apache.org/cassandra/Cassandra-trunk-test-cdc/jdk=jdk_11_latest,label=cassandra/599/build/test/logs/cdc/TEST-org.apache.cassandra.io.sstable.SSTableMetadataTest.log.xz] was (Author: michaelsembwever): Failure spotted: - [Cassandra-trunk #368|https://nightlies.apache.org/cassandra/ci-cassandra.apache.org/job/Cassandra-trunk/368/] \\ !Screenshot 2021-03-23 at 20.12.18.png|width=300! Downstream stage job: - [Cassandra-trunk-test-cdc jdk_11 #599|https://nightlies.apache.org/cassandra/ci-cassandra.apache.org/job/Cassandra-trunk-test-cdc/jdk=jdk_11_latest,label=cassandra/599/] with logs [here|https://nightlies.apache.org/cassandra/Cassandra-trunk-test-cdc/jdk=jdk_11_latest,label=cassandra/599/build/test/logs/cdc/TEST-org.apache.cassandra.io.sstable.SSTableMetadataTest.log.xz] > Fix flaky testTrackMaxDeletionTime > -- > > Key: CASSANDRA-16236 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16236 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Brandon Williams >Priority: Normal > Fix For: 4.0-rc > > Attachments: Screenshot 2021-03-23 at 20.12.18.png > > > * > testTrackMaxDeletionTime - org.apache.cassandra.io.sstable.SSTableMetadataTest > > junit.framework.AssertionFailedError: expected:<1.6038784E9> but > was:<1.60387827E9> > at > org.apache.cassandra.io.sstable.SSTableMetadataTest.testTrackMaxDeletionTime(SSTableMetadataTest.java:102) > https://app.circleci.com/pipelines/github/bereng/cassandra/160/workflows/6cb80410-b398-477c-b4c9-cc7369785869/jobs/1317 -- 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-16236) Fix flaky testTrackMaxDeletionTime
[ https://issues.apache.org/jira/browse/CASSANDRA-16236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308577#comment-17308577 ] Berenguer Blasi commented on CASSANDRA-16236: - I can't repro no mater how much I loop it... > Fix flaky testTrackMaxDeletionTime > -- > > Key: CASSANDRA-16236 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16236 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Brandon Williams >Priority: Normal > Fix For: 4.0-rc > > Attachments: Screenshot 2021-03-23 at 20.12.18.png > > > * > testTrackMaxDeletionTime - org.apache.cassandra.io.sstable.SSTableMetadataTest > > junit.framework.AssertionFailedError: expected:<1.6038784E9> but > was:<1.60387827E9> > at > org.apache.cassandra.io.sstable.SSTableMetadataTest.testTrackMaxDeletionTime(SSTableMetadataTest.java:102) > https://app.circleci.com/pipelines/github/bereng/cassandra/160/workflows/6cb80410-b398-477c-b4c9-cc7369785869/jobs/1317 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] 03/03: hack in plausible tracking with
This is an automated email from the ASF dual-hosted git repository.
mck pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git
commit d4069fd5ae39b3313e843714e1cd68046f99e26e
Author: mck
AuthorDate: Sun Mar 7 15:03:00 2021 +0100
hack in plausible tracking with
`find content -name "*.html" -exec sed -i '' 's;^;https://plausible.cassandra.apache.org/js/plausible.js";>;'
{} \;`
CASSANDRA-16488
---
content/blog/Apache-Cassandra-Changelog-1-October-2020.html | 2 +-
content/blog/Apache-Cassandra-Changelog-2-December-2020.html | 2 +-
content/blog/Apache-Cassandra-Changelog-3-January-2021.html | 2 +-
content/blog/Apache-Cassandra-Changelog-4-February-2021.html | 2 +-
content/blog/Apache-Cassandra-Usage-Report-2020.html | 2 +-
content/blog/Audit-Logging-in-Apache-Cassandra-4.html | 2 +-
content/blog/Cassandra-and-Kubernetes-SIG-Update-and-Survey.html | 2 +-
...-Higher-Availability-with-5x-Faster-Streaming-in-Cassandra-4 .html | 2 +-
...ing-Bugs-in-Cassandra's-Internals-with-Property-based-Testing.html | 2 +-
.../Hardware-bound-Zero-Copy-Streaming-in-Apache-Cassandra-4.html | 2 +-
.../blog/Improving-Apache-Cassandras-Front-Door-and-Backpressure.html | 2 +-
...ntroducing-Apache-Cassandra-4-Beta-Battle-Tested-From-Day-One.html | 2 +-
content/blog/Introducing-Transient-Replication.html | 2 +-
content/blog/Testing-Apache-Cassandra-4.html | 2 +-
content/blog/cass-changelog_2.html| 2 +-
content/blog/cass-changelog_3.html| 2 +-
content/blog/index.html | 2 +-
content/blog/template.html| 2 +-
content/case-studies/index.html | 2 +-
content/cassandra-basics/index.html | 2 +-
content/community/index.html | 2 +-
content/download/index.html | 2 +-
content/ecosystem/index.html | 2 +-
content/index.html| 4 ++--
content/quickstart/index.html | 2 +-
content/resources/index.html | 2 +-
26 files changed, 27 insertions(+), 27 deletions(-)
diff --git a/content/blog/Apache-Cassandra-Changelog-1-October-2020.html
b/content/blog/Apache-Cassandra-Changelog-1-October-2020.html
index 48cd465..4126d92 100644
--- a/content/blog/Apache-Cassandra-Changelog-1-October-2020.html
+++ b/content/blog/Apache-Cassandra-Changelog-1-October-2020.html
@@ -12,7 +12,7 @@
-
+ https://plausible.cassandra.apache.org/js/plausible.js";>
diff --git a/content/blog/Apache-Cassandra-Changelog-2-December-2020.html
b/content/blog/Apache-Cassandra-Changelog-2-December-2020.html
index b31b618..f8d7646 100644
--- a/content/blog/Apache-Cassandra-Changelog-2-December-2020.html
+++ b/content/blog/Apache-Cassandra-Changelog-2-December-2020.html
@@ -12,7 +12,7 @@
-
+ https://plausible.cassandra.apache.org/js/plausible.js";>
diff --git a/content/blog/Apache-Cassandra-Changelog-3-January-2021.html
b/content/blog/Apache-Cassandra-Changelog-3-January-2021.html
index 39caa53..e11729c 100644
--- a/content/blog/Apache-Cassandra-Changelog-3-January-2021.html
+++ b/content/blog/Apache-Cassandra-Changelog-3-January-2021.html
@@ -12,7 +12,7 @@
-
+ https://plausible.cassandra.apache.org/js/plausible.js";>
diff --git a/content/blog/Apache-Cassandra-Changelog-4-February-2021.html
b/content/blog/Apache-Cassandra-Changelog-4-February-2021.html
index e1cd37e..5c665b6 100644
--- a/content/blog/Apache-Cassandra-Changelog-4-February-2021.html
+++ b/content/blog/Apache-Cassandra-Changelog-4-February-2021.html
@@ -12,7 +12,7 @@
-
+ https://plausible.cassandra.apache.org/js/plausible.js";>
diff --git a/content/blog/Apache-Cassandra-Usage-Report-2020.html
b/content/blog/Apache-Cassandra-Usage-Report-2020.html
index f33055e..d075030 100644
--- a/content/blog/Apache-Cassandra-Usage-Report-2020.html
+++ b/content/blog/Apache-Cassandra-Usage-Report-2020.html
@@ -12,7 +12,7 @@
-
+ https://plausible.cassandra.apache.org/js/plausible.js";>
[jira] [Commented] (CASSANDRA-16488) Setup instance of Plausible service to track analytics for new Cassandra web
[
https://issues.apache.org/jira/browse/CASSANDRA-16488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308559#comment-17308559
]
Michael Semb Wever commented on CASSANDRA-16488:
Both cassandra.apache.org and cassandra.stage.apache.org has the tracking
temporarily enabled on every html page.
I
[hacked|https://github.com/apache/cassandra-website/commit/f20408161173d48f45bc347898efc47270f5a0a9]
it with:
{code}
find content -name "*.html" -exec sed -i '' 's;^;https://plausible.cassandra.apache.org/js/plausible.js";>;'
{} \;
{code}
> Setup instance of Plausible service to track analytics for new Cassandra web
>
>
> Key: CASSANDRA-16488
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16488
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Website
>Reporter: Stefan Miklosovic
>Assignee: Melissa Logan
>Priority: Normal
> Fix For: 4.0.x
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> This ticket should track the work done in regards of the provisioning a box
> where Plausible service will run for tracking analytics for new Cassandra's
> web page.
--
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-16537) BLOG - World Party 2021
[ https://issues.apache.org/jira/browse/CASSANDRA-16537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16537: --- Fix Version/s: 4.0 4.0-beta5 Source Control Link: https://github.com/apache/cassandra-website/commit/66972d875ce8a5b952b4347bc55c605d561b534d Resolution: Fixed Status: Resolved (was: Ready to Commit) > BLOG - World Party 2021 > --- > > Key: CASSANDRA-16537 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16537 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-beta5, 4.0 > > Attachments: blog-01-index.png, blog-02-post-world_party.png > > > Submit PR for C* World Party blog post prepared by constantia.io. -- 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-16537) BLOG - World Party 2021
[ https://issues.apache.org/jira/browse/CASSANDRA-16537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308553#comment-17308553 ] Michael Semb Wever commented on CASSANDRA-16537: Commited as [66972d875ce8a5b952b4347bc55c605d561b534d|https://github.com/apache/cassandra-website/commit/66972d875ce8a5b952b4347bc55c605d561b534d]. Published at https://cassandra.apache.org/blog/2021/03/25/world_party.html > BLOG - World Party 2021 > --- > > Key: CASSANDRA-16537 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16537 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Attachments: blog-01-index.png, blog-02-post-world_party.png > > > Submit PR for C* World Party blog post prepared by constantia.io. -- 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-16262) 4.0 Quality: Coordination & Replication Fuzz Testing
[ https://issues.apache.org/jira/browse/CASSANDRA-16262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308551#comment-17308551 ] Alex Petrov commented on CASSANDRA-16262: - [~cscotta] sure. In fact, I've started working to make this possible. The first pull request is to Harry and it is here: https://github.com/apache/cassandra-harry/pull/7 There are several more things that I'd like to finish before we can start testing in earnest. On Harry side we only need to implement partition deletions (which is mostly ready), and implement statics (slightly more involved change, since it requires us to separate partition-level updates from row-level ones for efficiency). Other than that Harry tooling is adequate in my opinion. After this, we only need to hook up Harry into Cassandra tests, and add a simple QT-like DSL for generating schema and data, and then making checks and validations, and start running these tests for several hundred hours at very least, preferably more. FWIW, we do not strictly have to hook it up to Cassandra codebase, but I think it'll make it more accessible, since most people are already familiar with how to run Cassandra tests. > 4.0 Quality: Coordination & Replication Fuzz Testing > > > Key: CASSANDRA-16262 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16262 > Project: Cassandra > Issue Type: Task > Components: Test/fuzz >Reporter: Caleb Rackliffe >Assignee: Alex Petrov >Priority: Normal > Fix For: 4.0-rc > > > CASSANDRA-16180, CASSANDRA-16181, and CASSANDRA-15977 have largely focused on > auditing the existing tests around coordination, replication, and > read-repair, respectively. We've expanded existing test cases, added coverage > around components that we've refactored along the way, and added in-JVM dtest > upgrade tests where possible. > What remains is verifying the distributed read and write paths in the face of > common operational events, namely node restarts, bootstrapping, decommission, > and cleanup. If we can find a way to simulate these events, > [Harry|https://github.com/apache/cassandra-harry] seems like a good candidate > to host the verification logic itself. > To keep things simple initially, I would propose that we start by testing > simple read-only and write-only workloads (the former without read repair). -- 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-harry] branch CASSANDRA-16262 created (now 8238908)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to branch CASSANDRA-16262 in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git. at 8238908 Numerious minor improvements while preparing for fuzz-testing 4.0 in earnest: This branch includes the following new commits: new 8238908 Numerious minor improvements while preparing for fuzz-testing 4.0 in earnest: The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16537) BLOG - World Party 2021
[ https://issues.apache.org/jira/browse/CASSANDRA-16537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308476#comment-17308476 ] Erick Ramirez edited comment on CASSANDRA-16537 at 3/25/21, 9:46 AM: - I've successfully staged the blog post. I've verified that the listing displays correctly in the index page: !blog-01-index.png|width=300! and the elements of the blog itself renders as expected: !blog-02-post-world_party.png|width=300! was (Author: flightc): I've successfully stage the blog post. I've verified that the listing displays correctly in the index page: !blog-01-index.png|width=300! and the elements of the blog itself renders as expected: !blog-02-post-world_party.png|width=300! > BLOG - World Party 2021 > --- > > Key: CASSANDRA-16537 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16537 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Attachments: blog-01-index.png, blog-02-post-world_party.png > > > Submit PR for C* World Party blog post prepared by constantia.io. -- 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-16537) BLOG - World Party 2021
[ https://issues.apache.org/jira/browse/CASSANDRA-16537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308537#comment-17308537 ] Erick Ramirez commented on CASSANDRA-16537: --- That's a fantastic tip on setting the width. I was looking it up but got distracted with questions on ASF Slack. Thanks! (y) > BLOG - World Party 2021 > --- > > Key: CASSANDRA-16537 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16537 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Attachments: blog-01-index.png, blog-02-post-world_party.png > > > Submit PR for C* World Party blog post prepared by constantia.io. -- 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-16537) BLOG - World Party 2021
[ https://issues.apache.org/jira/browse/CASSANDRA-16537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308476#comment-17308476 ] Erick Ramirez edited comment on CASSANDRA-16537 at 3/25/21, 9:44 AM: - I've successfully stage the blog post. I've verified that the listing displays correctly in the index page: !blog-01-index.png|width=300! and the elements of the blog itself renders as expected: !blog-02-post-world_party.png|width=300! was (Author: flightc): I've successfully stage the blog post. I've verified that the listing displays correctly in the index page: !blog-01-index.png! and the elements of the blog itself renders as expected: !blog-02-post-world_party.png! > BLOG - World Party 2021 > --- > > Key: CASSANDRA-16537 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16537 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Attachments: blog-01-index.png, blog-02-post-world_party.png > > > Submit PR for C* World Party blog post prepared by constantia.io. -- 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-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2
[ https://issues.apache.org/jira/browse/CASSANDRA-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-16536: -- Status: Changes Suggested (was: Review In Progress) > BLOG - Post about Cassandra & Kubernetes - SIG Update #2 > > > Key: CASSANDRA-16536 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16536 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Michael Semb Wever >Priority: High > Labels: pull-request-available > Fix For: 4.0-beta5, 4.0 > > Attachments: image-2021-03-24-18-57-08-450.png > > > We're getting another update up for the Cassandra & Kubernetes SIG > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown] > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2
[
https://issues.apache.org/jira/browse/CASSANDRA-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308527#comment-17308527
]
Erick Ramirez edited comment on CASSANDRA-16536 at 3/25/21, 9:33 AM:
-
Below are some minor nits/suggestions.
* Omit "processes" in:
{quote}*Automated node recovery processes* - basic operations
{color:#de350b}-processes-{color} such as restart, replace node, or replace an
instance are all automated.
{quote}
* Disambiguate "operators" in:
{quote}*Customizable containers* - applying containerization best practice,
this enables {color:#de350b}*human*{color} operators to merge containers they
have built with what’s offered in the {color:#de350b}*cass-*{color}operator so
that they don’t have to deal with secrets/volumes.
{quote}
* I feel like _"... existing open source ..."_ is missing a word, maybe "tools"?
{quote}The operator leverages a number of existing open source
{color:#de350b}*tools*{color} in the OSS ecosystem ...
{quote}
* Expand "RF" to "replication factor" to make it easier for new users to
understand:
{quote}NetworkTopologyStrategy is automatically applied with appropriate
{color:#de350b}-RF- *replication factor*{color} for system keyspaces.
{quote}
* Looks like a grammatical error in:
{quote}Well documentat{color:#de350b}-ion-*ed*{color} cloud storage classes, ...
{quote}
* Consider using #cassandra-kubernetes in the last paragraph:
{quote}... by joining the {color:#de350b}*#cassandra-kubernetes*{color} channel.
{quote}
Cheers!
P.S. Noting here that we [discussed on ASF
Slack|https://the-asf.slack.com/archives/C01RY1LUPD5/p1616659232007700]
scheduling this post for next week in preference for the World Party blog post
(CASSANDRA-16537).
was (Author: flightc):
Below are some minor nits/suggestions.
* Omit "processes" in:
{quote}*Automated node recovery processes* - basic operations
{color:#de350b}-processes-{color} such as restart, replace node, or replace an
instance are all automated.
{quote}
* Disambiguate "operators" in:
{quote}*Customizable containers* - applying containerization best practice,
this enables {color:#de350b}*human*{color} operators to merge containers they
have built with what’s offered in the {color:#de350b}*cass-*{color}operator so
that they don’t have to deal with secrets/volumes.
{quote}
* I feel like _"... existing open source ..."_ is missing a word, maybe "tools"?
{quote}The operator leverages a number of existing open source
{color:#de350b}*tools*{color} in the OSS ecosystem ...
{quote}
* Expand "RF" to "replication factor" to make it easier for new users to
understand:
{quote}NetworkTopologyStrategy is automatically applied with appropriate
{color:#de350b}-RF- *replication factor*{color} for system keyspaces.
{quote}
* Looks like a grammatical error in:
{quote}Well documentat{color:#de350b}-ion-*ed*{color} cloud storage classes, ...
{quote}
* Consider using #cassandra-kubernetes in the last paragraph:
{quote}... by joining the {color:#de350b}*#cassandra-kubernetes*{color} channel.
{quote}
Cheers!
P.S. Noting here that we [discussed on ASF
Slack|https://the-asf.slack.com/archives/C01RY1LUPD5/p1616659232007700]
scheduling this post for next week in preference for the World Party blog post
(CASSANDRA-16537).
> BLOG - Post about Cassandra & Kubernetes - SIG Update #2
>
>
> Key: CASSANDRA-16536
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16536
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Michael Semb Wever
>Priority: High
> Labels: pull-request-available
> Fix For: 4.0-beta5, 4.0
>
> Attachments: image-2021-03-24-18-57-08-450.png
>
>
> We're getting another update up for the Cassandra & Kubernetes SIG
>
> [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2
[
https://issues.apache.org/jira/browse/CASSANDRA-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308527#comment-17308527
]
Erick Ramirez edited comment on CASSANDRA-16536 at 3/25/21, 9:32 AM:
-
Below are some minor nits/suggestions.
* Omit "processes" in:
{quote}*Automated node recovery processes* - basic operations
{color:#de350b}-processes-{color} such as restart, replace node, or replace an
instance are all automated.
{quote}
* Disambiguate "operators" in:
{quote}*Customizable containers* - applying containerization best practice,
this enables {color:#de350b}*human*{color} operators to merge containers they
have built with what’s offered in the {color:#de350b}*cass-*{color}operator so
that they don’t have to deal with secrets/volumes.
{quote}
* I feel like _"... existing open source ..."_ is missing a word, maybe "tools"?
{quote}The operator leverages a number of existing open source
{color:#de350b}*tools*{color} in the OSS ecosystem ...
{quote}
* Expand "RF" to "replication factor" to make it easier for new users to
understand:
{quote}NetworkTopologyStrategy is automatically applied with appropriate
{color:#de350b}-RF- *replication factor*{color} for system keyspaces.
{quote}
* Looks like a grammatical error in:
{quote}Well documentat{color:#de350b}-ion-*ed*{color} cloud storage classes, ...
{quote}
* Consider using #cassandra-kubernetes in the last paragraph:
{quote}... by joining the {color:#de350b}*#cassandra-kubernetes*{color} channel.
{quote}
Cheers!
P.S. Noting here that we [discussed on ASF
Slack|https://the-asf.slack.com/archives/C01RY1LUPD5/p1616659232007700]
scheduling this post for next week in preference for the World Party blog post
(CASSANDRA-16537).
was (Author: flightc):
Below are some minor nits/suggestions.
* Omit "processes" in:
{quote}*Automated node recovery processes* - basic operations
{color:#de350b}-processes-{color} such as restart, replace node, or replace an
instance are all automated.
{quote} * Disambiguate "operators" in:
{quote}*Customizable containers* - applying containerization best practice,
this enables {color:#de350b}*human*{color} operators to merge containers they
have built with what’s offered in the {color:#de350b}*cass-*{color}operator so
that they don’t have to deal with secrets/volumes.
{quote} * I feel like _"... existing open source ..."_ is missing a word, maybe
"tools"?
{quote}The operator leverages a number of existing open source
{color:#de350b}*tools*{color} in the OSS ecosystem ...
{quote} * Expand "RF" to "replication factor" to make it easier for new users
to understand:
{quote}NetworkTopologyStrategy is automatically applied with appropriate
{color:#de350b}-RF- *replication factor*{color} for system keyspaces.
{quote} * Looks like a grammatical error in:
{quote}Well documentat{color:#de350b}-ion-*ed*{color} cloud storage classes, ...
{quote} * Consider using #cassandra-kubernetes in the last paragraph:
{quote}... by joining the {color:#de350b}*#cassandra-kubernetes*{color} channel.
{quote}
Cheers!
> BLOG - Post about Cassandra & Kubernetes - SIG Update #2
>
>
> Key: CASSANDRA-16536
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16536
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Michael Semb Wever
>Priority: High
> Labels: pull-request-available
> Fix For: 4.0-beta5, 4.0
>
> Attachments: image-2021-03-24-18-57-08-450.png
>
>
> We're getting another update up for the Cassandra & Kubernetes SIG
>
> [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (4f809fc -> 37a22df)
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a change to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git.
discard 4f809fc generate docs for 4f02f64a
add 66972d8 World Party blog
new 37a22df generate docs for 66972d87
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (4f809fc)
\
N -- N -- N refs/heads/asf-staging (37a22df)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../world_party.html} | 53 ++-
content/blog/index.html| 18 ++--
content/blog/page2/index.html | 18 ++--
content/blog/page3/index.html | 18 ++--
content/blog/page4/index.html | 9 ++
content/feed.xml | 98 -
content/img/world-party-2021-footer.png| Bin 0 -> 197343 bytes
src/_posts/2021-03-25-world_party.markdown | 42 +
src/img/world-party-2021-footer.png| Bin 0 -> 197343 bytes
9 files changed, 149 insertions(+), 107 deletions(-)
copy content/blog/2021/03/{10/join_cassandra_gsoc_2021.html =>
25/world_party.html} (57%)
create mode 100755 content/img/world-party-2021-footer.png
create mode 100755 src/_posts/2021-03-25-world_party.markdown
create mode 100755 src/img/world-party-2021-footer.png
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch trunk updated: World Party blog
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-website.git The following commit(s) were added to refs/heads/trunk by this push: new 66972d8 World Party blog 66972d8 is described below commit 66972d875ce8a5b952b4347bc55c605d561b534d Author: Erick Ramirez AuthorDate: Thu Mar 25 16:00:15 2021 +1100 World Party blog patch by Chris Thornett, Erick Ramirez; reviewed by Erick Ramirez, Mick Semb Wever for CASSANDRA-16537 --- src/_posts/2021-03-25-world_party.markdown | 42 + src/img/world-party-2021-footer.png| Bin 0 -> 197343 bytes 2 files changed, 42 insertions(+) diff --git a/src/_posts/2021-03-25-world_party.markdown b/src/_posts/2021-03-25-world_party.markdown new file mode 100644 index 000..a2c57e4 --- /dev/null +++ b/src/_posts/2021-03-25-world_party.markdown @@ -0,0 +1,42 @@ +--- +layout: post +title: "Apache Cassandra World Party | April 2021" +date: 2021-03-25 +author: the Apache Cassandra Community +categories: blog +--- + +The COVID-19 pandemic has taken a toll on a lot of things and one of those is our ability to interact as a community. There has been no in-person conferences or meetups for over a year now. The Cassandra community has always thrived on sharing with each other at places like ApacheCon and the Cassandra Summit. With Cassandra 4.0, we have a lot to celebrate! + + + +This release will be the most stable database ever shipped, and Cassandra has become one of the most important databases running today. It is responsible for the biggest workloads in the world and because of that, we want to gather the worldwide community and have a party. + +We thought we would do something different for this special event that reflects who we are as a community. Our community lives and works in every timezone, and we want to make it as easy as possible for everyone to participate so we’ve decided to use an Ignite-style format. If you are new to this here’s how it works: + +* Each talk is only 5 minutes long. +* You get ten slides and they automatically advance every 30 seconds. +* To get you started, we have a template ready [here](https://docs.google.com/presentation/d/1cWta8H88xXolEdS-HFo9nzp1GI5v_VkCHo5dmoKqozY/edit#slide=id.gc922c7a35f_0_106). +* You can do your talk in the language of your choice. English is not required. +* Format: PDF (Please no GIFs or videos) + +When you are ready, you can use [this link to submit your talk idea](https://sessionize.com/cassandra) by April 9, 2021. It’s only five minutes but you can share a lot in that time. Have fun with the format and encourage other people in your network to participate. Diversity is what makes our community stronger so if you are a newcomer, don’t let that put you off -- we’d love you to share your experiences. + +## What? + +One-day virtual party on Wednesday, April 28 with three, hour-long sessions so you can celebrate with the Cassandra community in your time zone -- or attend all three! + +## When? + +Join us at the time most convenient for you on April 28: + +* 6:00am PT / 1:00pm UTC +* 2:00pm PT / 9:00pm UTC +* 10:00pm PT / 5:00am UTC + +A registration page will go live soon. In the meantime, please [submit your 5-minute Cassandra talk](https://sessionize.com/cassandra) by April 9! + +Whether you're attending or speaking, all Apache Cassandra™ World Party participants must adhere to the [code of conduct](https://www.apache.org/foundation/policies/anti-harassment.html). + +Got questions about the event? Please email [cassan...@constantia.io](mailto:cassan...@constantia.io). + diff --git a/src/img/world-party-2021-footer.png b/src/img/world-party-2021-footer.png new file mode 100644 index 000..bed2827 Binary files /dev/null and b/src/img/world-party-2021-footer.png differ - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2
[
https://issues.apache.org/jira/browse/CASSANDRA-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308527#comment-17308527
]
Erick Ramirez commented on CASSANDRA-16536:
---
Below are some minor nits/suggestions.
* Omit "processes" in:
{quote}*Automated node recovery processes* - basic operations
{color:#de350b}-processes-{color} such as restart, replace node, or replace an
instance are all automated.
{quote} * Disambiguate "operators" in:
{quote}*Customizable containers* - applying containerization best practice,
this enables {color:#de350b}*human*{color} operators to merge containers they
have built with what’s offered in the {color:#de350b}*cass-*{color}operator so
that they don’t have to deal with secrets/volumes.
{quote} * I feel like _"... existing open source ..."_ is missing a word, maybe
"tools"?
{quote}The operator leverages a number of existing open source
{color:#de350b}*tools*{color} in the OSS ecosystem ...
{quote} * Expand "RF" to "replication factor" to make it easier for new users
to understand:
{quote}NetworkTopologyStrategy is automatically applied with appropriate
{color:#de350b}-RF- *replication factor*{color} for system keyspaces.
{quote} * Looks like a grammatical error in:
{quote}Well documentat{color:#de350b}-ion-*ed*{color} cloud storage classes, ...
{quote} * Consider using #cassandra-kubernetes in the last paragraph:
{quote}... by joining the {color:#de350b}*#cassandra-kubernetes*{color} channel.
{quote}
Cheers!
> BLOG - Post about Cassandra & Kubernetes - SIG Update #2
>
>
> Key: CASSANDRA-16536
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16536
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Michael Semb Wever
>Priority: High
> Labels: pull-request-available
> Fix For: 4.0-beta5, 4.0
>
> Attachments: image-2021-03-24-18-57-08-450.png
>
>
> We're getting another update up for the Cassandra & Kubernetes SIG
>
> [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16537) BLOG - World Party 2021
[
https://issues.apache.org/jira/browse/CASSANDRA-16537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308502#comment-17308502
]
Michael Semb Wever commented on CASSANDRA-16537:
[~flightc] protip: you can add {{|width=300!}} to the images in your comments^
so they display better.
!blog-01-index.png!
> BLOG - World Party 2021
> ---
>
> Key: CASSANDRA-16537
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16537
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Erick Ramirez
>Assignee: Erick Ramirez
>Priority: Normal
> Labels: pull-request-available
> Attachments: blog-01-index.png, blog-02-post-world_party.png
>
>
> Submit PR for C* World Party blog post prepared by constantia.io.
--
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-16537) BLOG - World Party 2021
[
https://issues.apache.org/jira/browse/CASSANDRA-16537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308502#comment-17308502
]
Michael Semb Wever edited comment on CASSANDRA-16537 at 3/25/21, 8:57 AM:
--
[~flightc] protip: you can add {{|width=300!}} to the images in your comments^
so they display better.
was (Author: michaelsembwever):
[~flightc] protip: you can add {{|width=300!}} to the images in your comments^
so they display better.
!blog-01-index.png!
> BLOG - World Party 2021
> ---
>
> Key: CASSANDRA-16537
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16537
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Erick Ramirez
>Assignee: Erick Ramirez
>Priority: Normal
> Labels: pull-request-available
> Attachments: blog-01-index.png, blog-02-post-world_party.png
>
>
> Submit PR for C* World Party blog post prepared by constantia.io.
--
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-16532) Fix flaky testSkipScrubCorruptedCounterRowWithTool
[ https://issues.apache.org/jira/browse/CASSANDRA-16532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-16532: Reviewers: Andres de la Peña, Berenguer Blasi (was: Andres de la Peña) Status: Review In Progress (was: Patch Available) > Fix flaky testSkipScrubCorruptedCounterRowWithTool > -- > > Key: CASSANDRA-16532 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16532 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-rc > > Time Spent: 1.5h > Remaining Estimate: 0h > > Fix flaky > [testSkipScrubCorruptedCounterRowWithTool|https://ci-cassandra.apache.org/job/Cassandra-trunk/365/testReport/junit/org.apache.cassandra.db/ScrubTest/testSkipScrubCorruptedCounterRowWithTool_compression/] -- 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-16537) BLOG - World Party 2021
[ https://issues.apache.org/jira/browse/CASSANDRA-16537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-16537: -- Status: Review In Progress (was: Patch Available) > BLOG - World Party 2021 > --- > > Key: CASSANDRA-16537 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16537 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Attachments: blog-01-index.png, blog-02-post-world_party.png > > > Submit PR for C* World Party blog post prepared by constantia.io. -- 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-16537) BLOG - World Party 2021
[ https://issues.apache.org/jira/browse/CASSANDRA-16537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-16537: -- Status: Ready to Commit (was: Review In Progress) > BLOG - World Party 2021 > --- > > Key: CASSANDRA-16537 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16537 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Attachments: blog-01-index.png, blog-02-post-world_party.png > > > Submit PR for C* World Party blog post prepared by constantia.io. -- 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-16537) BLOG - World Party 2021
[ https://issues.apache.org/jira/browse/CASSANDRA-16537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308476#comment-17308476 ] Erick Ramirez commented on CASSANDRA-16537: --- I've successfully stage the blog post. I've verified that the listing displays correctly in the index page: !blog-01-index.png! and the elements of the blog itself renders as expected: !blog-02-post-world_party.png! > BLOG - World Party 2021 > --- > > Key: CASSANDRA-16537 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16537 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Attachments: blog-01-index.png, blog-02-post-world_party.png > > > Submit PR for C* World Party blog post prepared by constantia.io. -- 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-16537) BLOG - World Party 2021
[ https://issues.apache.org/jira/browse/CASSANDRA-16537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-16537: -- Attachment: blog-02-post-world_party.png > BLOG - World Party 2021 > --- > > Key: CASSANDRA-16537 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16537 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Attachments: blog-01-index.png, blog-02-post-world_party.png > > > Submit PR for C* World Party blog post prepared by constantia.io. -- 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-16537) BLOG - World Party 2021
[ https://issues.apache.org/jira/browse/CASSANDRA-16537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-16537: -- Attachment: blog-01-index.png > BLOG - World Party 2021 > --- > > Key: CASSANDRA-16537 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16537 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Attachments: blog-01-index.png > > > Submit PR for C* World Party blog post prepared by constantia.io. -- 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-15892) JAVA 8/11: test_resumable_rebuild - rebuild_test.TestRebuild
[ https://issues.apache.org/jira/browse/CASSANDRA-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308450#comment-17308450 ] Zhao Yang commented on CASSANDRA-15892: --- thanks for the explanation. the thread dump really helps. The fix looks good to me. Alternatively, we can remove the `synchronized` from `StreamSession#onChannelClose` as it doesn't have to be synchronized. > JAVA 8/11: test_resumable_rebuild - rebuild_test.TestRebuild > > > Key: CASSANDRA-15892 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15892 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Ekaterina Dimitrova >Assignee: Gianluca Righetto >Priority: Normal > Fix For: 4.0-rc > > Attachments: CASSANDRA-15892-07babf3c-node2-deadlock-thread-dump.txt, > Screenshot 2021-03-23 at 19.37.35.png, Screenshot 2021-03-23 at 19.53.51.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > JAVA 11: > test_resumable_rebuild - rebuild_test.TestRebuild > Fails locally and in > [CircleCI | > [https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/222/workflows/11202c7e-6c94-4d4e-bbbf-9e2fa9791ad0/jobs/1338]] -- 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-15892) JAVA 8/11: test_resumable_rebuild - rebuild_test.TestRebuild
[
https://issues.apache.org/jira/browse/CASSANDRA-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308450#comment-17308450
]
Zhao Yang edited comment on CASSANDRA-15892 at 3/25/21, 7:35 AM:
-
thanks for the explanation. the thread dump really helps. The fix looks good to
me. Alternatively, we can remove the {{synchronized}} from
{{StreamSession#onChannelClose}} as it doesn't have to be synchronized.
was (Author: jasonstack):
thanks for the explanation. the thread dump really helps. The fix looks good to
me. Alternatively, we can remove the `synchronized` from
`StreamSession#onChannelClose` as it doesn't have to be synchronized.
> JAVA 8/11: test_resumable_rebuild - rebuild_test.TestRebuild
>
>
> Key: CASSANDRA-15892
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15892
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Ekaterina Dimitrova
>Assignee: Gianluca Righetto
>Priority: Normal
> Fix For: 4.0-rc
>
> Attachments: CASSANDRA-15892-07babf3c-node2-deadlock-thread-dump.txt,
> Screenshot 2021-03-23 at 19.37.35.png, Screenshot 2021-03-23 at 19.53.51.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> JAVA 11:
> test_resumable_rebuild - rebuild_test.TestRebuild
> Fails locally and in
> [CircleCI |
> [https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/222/workflows/11202c7e-6c94-4d4e-bbbf-9e2fa9791ad0/jobs/1338]]
--
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-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2
[ https://issues.apache.org/jira/browse/CASSANDRA-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308437#comment-17308437 ] Erick Ramirez commented on CASSANDRA-16536: --- I'm in the middle of reviewing this. I hope to stage it in the next hour or so. Cheers! > BLOG - Post about Cassandra & Kubernetes - SIG Update #2 > > > Key: CASSANDRA-16536 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16536 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Michael Semb Wever >Priority: High > Labels: pull-request-available > Fix For: 4.0-beta5, 4.0 > > Attachments: image-2021-03-24-18-57-08-450.png > > > We're getting another update up for the Cassandra & Kubernetes SIG > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown] > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2
[ https://issues.apache.org/jira/browse/CASSANDRA-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16536: --- Change Category: Operability Priority: High (was: Normal) Status: Open (was: Triage Needed) > BLOG - Post about Cassandra & Kubernetes - SIG Update #2 > > > Key: CASSANDRA-16536 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16536 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Michael Semb Wever >Priority: High > Labels: pull-request-available > Fix For: 4.0-beta5, 4.0 > > Attachments: image-2021-03-24-18-57-08-450.png > > > We're getting another update up for the Cassandra & Kubernetes SIG > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown] > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2
[ https://issues.apache.org/jira/browse/CASSANDRA-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16536: --- Status: Review In Progress (was: Patch Available) > BLOG - Post about Cassandra & Kubernetes - SIG Update #2 > > > Key: CASSANDRA-16536 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16536 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Michael Semb Wever >Priority: High > Labels: pull-request-available > Fix For: 4.0-beta5, 4.0 > > Attachments: image-2021-03-24-18-57-08-450.png > > > We're getting another update up for the Cassandra & Kubernetes SIG > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown] > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2
[ https://issues.apache.org/jira/browse/CASSANDRA-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16536: --- Authors: (was: Michael Semb Wever) Status: Patch Available (was: Open) > BLOG - Post about Cassandra & Kubernetes - SIG Update #2 > > > Key: CASSANDRA-16536 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16536 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Michael Semb Wever >Priority: High > Labels: pull-request-available > Fix For: 4.0-beta5, 4.0 > > Attachments: image-2021-03-24-18-57-08-450.png > > > We're getting another update up for the Cassandra & Kubernetes SIG > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown] > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2
[ https://issues.apache.org/jira/browse/CASSANDRA-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16536: --- Issue Type: Task (was: Improvement) > BLOG - Post about Cassandra & Kubernetes - SIG Update #2 > > > Key: CASSANDRA-16536 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16536 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Michael Semb Wever >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-beta5, 4.0 > > Attachments: image-2021-03-24-18-57-08-450.png > > > We're getting another update up for the Cassandra & Kubernetes SIG > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown] > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2
[ https://issues.apache.org/jira/browse/CASSANDRA-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16536: --- Change Category: (was: Operability) > BLOG - Post about Cassandra & Kubernetes - SIG Update #2 > > > Key: CASSANDRA-16536 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16536 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Michael Semb Wever >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-beta5, 4.0 > > Attachments: image-2021-03-24-18-57-08-450.png > > > We're getting another update up for the Cassandra & Kubernetes SIG > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown] > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2
[ https://issues.apache.org/jira/browse/CASSANDRA-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16536: --- Reviewers: Erick Ramirez, Michael Semb Wever (was: Michael Semb Wever) > BLOG - Post about Cassandra & Kubernetes - SIG Update #2 > > > Key: CASSANDRA-16536 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16536 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Michael Semb Wever >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-beta5, 4.0 > > Attachments: image-2021-03-24-18-57-08-450.png > > > We're getting another update up for the Cassandra & Kubernetes SIG > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown] > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15892) JAVA 8/11: test_resumable_rebuild - rebuild_test.TestRebuild
[
https://issues.apache.org/jira/browse/CASSANDRA-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308415#comment-17308415
]
Gianluca Righetto commented on CASSANDRA-15892:
---
[~jasonstack] I attached a thread dump to this ticket which should make things
more clear, but this is the sequence of events:
Node 2 runs {{AsyncChannelOutputPlus#flush ->
AsyncStreamingOutputPlus#doFlush}} which contains the following
{code}
ChannelPromise promise = beginFlush(byteCount, 0, Integer.MAX_VALUE);
channel.writeAndFlush(GlobalBufferPoolAllocator.wrap(flush), promise);
{code}
That promise is responsible for unparking the thread in a later moment (it's
supposed to be called when the flush either completes or fails).
Still in {{AsyncChannelOutputPlus#flush}}, it calls {{waitUntilFlushed(0, 0)}}
and at this point the thread is parked.
Now it receives a SESSION_FAILED message, so it will try to close the channel,
but the problem is that the channel has a close listener that relies on a
synchronized method, {{StreamSession#onChannelClose}}, and since that thread is
parked, it blocks. In other words, netty can't properly close the channel and
the flush promise above is never called, so the thread is never unparked, hence
the deadlock.
> JAVA 8/11: test_resumable_rebuild - rebuild_test.TestRebuild
>
>
> Key: CASSANDRA-15892
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15892
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Ekaterina Dimitrova
>Assignee: Gianluca Righetto
>Priority: Normal
> Fix For: 4.0-rc
>
> Attachments: CASSANDRA-15892-07babf3c-node2-deadlock-thread-dump.txt,
> Screenshot 2021-03-23 at 19.37.35.png, Screenshot 2021-03-23 at 19.53.51.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> JAVA 11:
> test_resumable_rebuild - rebuild_test.TestRebuild
> Fails locally and in
> [CircleCI |
> [https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/222/workflows/11202c7e-6c94-4d4e-bbbf-9e2fa9791ad0/jobs/1338]]
--
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-16532) Fix flaky testSkipScrubCorruptedCounterRowWithTool
[
https://issues.apache.org/jira/browse/CASSANDRA-16532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308407#comment-17308407
]
Berenguer Blasi commented on CASSANDRA-16532:
-
Yep I had noticed the {{testScrubOutOfOrder}} failures both in this branch
_and_ in trunk. But notice how the failure for this ticket has gone away. I'd
vote to merge this one and open a new ticket for {{testScrubOutOfOrder}}. I
want to start merging fixes asap to see if ci-cass has indeed a problem of
misreporting failures. If this failure goes away but the new one pops up then
that'd be an indication it is so. Sounds ok?
> Fix flaky testSkipScrubCorruptedCounterRowWithTool
> --
>
> Key: CASSANDRA-16532
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16532
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Berenguer Blasi
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 4.0-rc
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Fix flaky
> [testSkipScrubCorruptedCounterRowWithTool|https://ci-cassandra.apache.org/job/Cassandra-trunk/365/testReport/junit/org.apache.cassandra.db/ScrubTest/testSkipScrubCorruptedCounterRowWithTool_compression/]
--
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
