[jira] [Created] (CASSANDRA-18075) Upgraded (C* 4.0.4) node stops communicating with older version (3.11.4) nodes during upgrade
Alaykumar Barochia created CASSANDRA-18075:
--
Summary: Upgraded (C* 4.0.4) node stops communicating with older
version (3.11.4) nodes during upgrade
Key: CASSANDRA-18075
URL: https://issues.apache.org/jira/browse/CASSANDRA-18075
Project: Cassandra
Issue Type: Bug
Components: Feature/Encryption
Reporter: Alaykumar Barochia
Attachments: cassandra-env.sh_3114, cassandra-env.sh_404,
cassandra.yaml_3114, cassandra.yaml_404, system.log_10.110.44.207
We are testing upgrade from Cassandra 3.11.4 to 4.0.4 on our test cluster which
is SSL enabled and facing an issue.
Our cluster size is 3x3.
{noformat}
Datacenter: abssl_dev_tap_ttc
=
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- AddressLoad Tokens Owns (effective) Host ID
Rack
UN 10.109.6.153 94.27 KiB 16 100.0%
130e59d2-2a9a-4039-a42f-deb20afcf288 rack1
UN 10.109.45.8104.43 KiB 16 100.0%
35274a2c-f915-4308-9981-d207a4e2108f rack1
UN 10.109.66.149 104.23 KiB 16 100.0%
ea0151bc-fb6c-425d-af42-75c10e52f941 rack1
Datacenter: abssl_dev_tap_tte
=
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- AddressLoad Tokens Owns (effective) Host ID
Rack
UN 10.110.4.110 104.44 KiB 16 100.0%
fd4a9fa8-f2a9-494c-afb8-7cb8a08c7554 rack1
UN 10.110.44.220 99.33 KiB 16 100.0%
f1dc35c0-a1c2-45fe-9f65-b1cc3d7f6947 rack1
UN 10.110.49.242 65.57 KiB 16 100.0%
72bc4ae5-876d-4d0a-91ac-6cf8b531b4dd rack1
dbaasprod-ca-abssl-de-393671-v001-yqlvf:~# nodetool describecluster
Cluster Information:
Name: abssl_dev
Snitch: org.apache.cassandra.locator.GossipingPropertyFileSnitch
DynamicEndPointSnitch: enabled
Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
Schema versions:
f68fbc0c-c9d6-3709-8075-c5a0d74192f2: [10.110.4.110,
10.110.44.220, 10.109.6.153, 10.109.45.8, 10.109.66.149, 10.110.49.242]
{noformat}
During the upgrade, we re-run the pipeline in which we get new server (with
different IP) that will have Cassandra 4.0.4 binary.
Disk '/data' (contains data files, commitlogs etc.) will get detached from the
old server and get attached to the new server.
This process works fine on non-SSL cluster but when we perform this on SSL
cluster, new node stops communicating with the rest of the nodes.
In this example, after upgrade, node 10.110.4.110 got replaced with new server
with new IP 10.110.44.207.
*Output from 3.11.4 node:*
{noformat}
dbaasprod-ca-abssl-dc-437097-v001-7mump:~# hostname -i
10.109.6.153
dbaasprod-ca-abssl-dc-437097-v001-7mump:~# java -version
openjdk version "1.8.0_322"
OpenJDK Runtime Environment (Temurin)(build 1.8.0_322-b06)
OpenJDK 64-Bit Server VM (Temurin)(build 25.322-b06, mixed mode)
dbaasprod-ca-abssl-dc-437097-v001-7mump:~# nodetool status
Datacenter: abssl_dev_tap_ttc
=
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- AddressLoad Tokens Owns (effective) Host ID
Rack
UN 10.109.6.153 135.24 KiB 16 100.0%
130e59d2-2a9a-4039-a42f-deb20afcf288 rack1
UN 10.109.45.8135.35 KiB 16 100.0%
35274a2c-f915-4308-9981-d207a4e2108f rack1
UN 10.109.66.149 135.25 KiB 16 100.0%
ea0151bc-fb6c-425d-af42-75c10e52f941 rack1
Datacenter: abssl_dev_tap_tte
=
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- AddressLoad Tokens Owns (effective) Host ID
Rack
DN 10.110.4.110 104.44 KiB 16 100.0%
fd4a9fa8-f2a9-494c-afb8-7cb8a08c7554 rack1
UN 10.110.44.220 104.44 KiB 16 100.0%
f1dc35c0-a1c2-45fe-9f65-b1cc3d7f6947 rack1
UN 10.110.49.242 65.57 KiB 16 100.0%
72bc4ae5-876d-4d0a-91ac-6cf8b531b4dd rack1
dbaasprod-ca-abssl-dc-437097-v001-7mump:~# nodetool describecluster
Cluster Information:
Name: abssl_dev
Snitch: org.apache.cassandra.locator.GossipingPropertyFileSnitch
DynamicEndPointSnitch: enabled
Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
Schema versions:
f68fbc0c-c9d6-3709-8075-c5a0d74192f2: [10.110.44.220,
10.109.6.153, 10.109.45.8, 10.109.66.149, 10.110.49.242]
UNREACHABLE: [10.110.4.110]
{noformat}
*Output from 4.0.4 node:*
{noformat}
dbaasprod-ca-abssl-de-393671-v003-dxpyv:~# hostname -i
10.110.44.207
dbaasprod-ca-abssl-de-393671-v003-dxpyv:~# java -version
openjdk version "11.0.15" 2022-04-19
OpenJDK Runtime Environment
[jira] [Updated] (CASSANDRA-17848) LIST PERMISSION can display incorrect resource name
[
https://issues.apache.org/jira/browse/CASSANDRA-17848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Berenguer Blasi updated CASSANDRA-17848:
Reviewers: Berenguer Blasi, Sam Tunnicliffe (was: Sam Tunnicliffe)
> LIST PERMISSION can display incorrect resource name
> ---
>
> Key: CASSANDRA-17848
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17848
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Yifan Cai
>Assignee: Yifan Cai
>Priority: Normal
>
> When producing the resource name, it seems to assume that the content in the
> `[]` is the function's input type, where it could also be part of the
> function name, as long as it is quoted. Here is an example to reproduce. In
> cqlsh,
> {code:java}
> > CREATE FUNCTION
> > test."admin_created_udf[org.apache.cassandra.db.marshal.LongType]"(input
> > int) RETURNS NULL ON NULL INPUT RETURNS int LANGUAGE java AS 'return 42;';
> > LIST EXECUTE OF user;
> role | username | resource| permission
> ---+--+-+
> user |user | |EXECUTE
> (1 rows)
> {code}
> The input should be "int", but in the output, it says "long".
> If the content enclosed by "[]" is not a valid class, the LIST PERMISSION
> request always fails for the user with "ConfigurationException: Unable to
> find abstract-type class".
> The bug is discovered by Piotr Sarna.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17848) LIST PERMISSION can display incorrect resource name
[
https://issues.apache.org/jira/browse/CASSANDRA-17848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639808#comment-17639808
]
Berenguer Blasi commented on CASSANDRA-17848:
-
I have been looking at this one also. I would only add we'd need to run j11 CI
as well, j8 is already green, but +1 otherwise.
> LIST PERMISSION can display incorrect resource name
> ---
>
> Key: CASSANDRA-17848
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17848
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Yifan Cai
>Assignee: Yifan Cai
>Priority: Normal
>
> When producing the resource name, it seems to assume that the content in the
> `[]` is the function's input type, where it could also be part of the
> function name, as long as it is quoted. Here is an example to reproduce. In
> cqlsh,
> {code:java}
> > CREATE FUNCTION
> > test."admin_created_udf[org.apache.cassandra.db.marshal.LongType]"(input
> > int) RETURNS NULL ON NULL INPUT RETURNS int LANGUAGE java AS 'return 42;';
> > LIST EXECUTE OF user;
> role | username | resource| permission
> ---+--+-+
> user |user | |EXECUTE
> (1 rows)
> {code}
> The input should be "int", but in the output, it says "long".
> If the content enclosed by "[]" is not a valid class, the LIST PERMISSION
> request always fails for the user with "ConfigurationException: Unable to
> find abstract-type class".
> The bug is discovered by Piotr Sarna.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17547) Documentation from Partition Denylist Lost in Document Migration + Minor Fixes
[ https://issues.apache.org/jira/browse/CASSANDRA-17547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639728#comment-17639728 ] Josh McKenzie commented on CASSANDRA-17547: --- Review feedback left on PR. A little whitespace trouble leading to some bad formatting (at least in intellij previewer) but once resolved LGTM. > Documentation from Partition Denylist Lost in Document Migration + Minor Fixes > -- > > Key: CASSANDRA-17547 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17547 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Jordan West >Assignee: Sharan Foga >Priority: Normal > Time Spent: 20m > Remaining Estimate: 0h > > The documentation added in > https://issues.apache.org/jira/browse/CASSANDRA-12106 went missing when the > documents were migrated to the new format. We just need to bring the doc > back. Along with this fix there are a couple minor edits to make to the > document itself to correct the examples. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17547) Documentation from Partition Denylist Lost in Document Migration + Minor Fixes
[ https://issues.apache.org/jira/browse/CASSANDRA-17547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17547: -- Test and Documentation Plan: Stage locally for verification Status: Patch Available (was: Open) > Documentation from Partition Denylist Lost in Document Migration + Minor Fixes > -- > > Key: CASSANDRA-17547 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17547 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Jordan West >Assignee: Sharan Foga >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > The documentation added in > https://issues.apache.org/jira/browse/CASSANDRA-12106 went missing when the > documents were migrated to the new format. We just need to bring the doc > back. Along with this fix there are a couple minor edits to make to the > document itself to correct the examples. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17547) Documentation from Partition Denylist Lost in Document Migration + Minor Fixes
[ https://issues.apache.org/jira/browse/CASSANDRA-17547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639665#comment-17639665 ] Sharan Foga commented on CASSANDRA-17547: - Hi [~jmckenzie]. Please can you take a look at [https://github.com/apache/cassandra/pull/2028] and let me have any feedback. > Documentation from Partition Denylist Lost in Document Migration + Minor Fixes > -- > > Key: CASSANDRA-17547 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17547 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Jordan West >Assignee: Sharan Foga >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > The documentation added in > https://issues.apache.org/jira/browse/CASSANDRA-12106 went missing when the > documents were migrated to the new format. We just need to bring the doc > back. Along with this fix there are a couple minor edits to make to the > document itself to correct the examples. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
