[
https://issues.apache.org/jira/browse/CASSANDRA-16718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17719875#comment-17719875
]
Brandon Williams commented on CASSANDRA-16718:
----------------------------------------------
{noformat}
node1: ERROR [main] 2023-05-05 10:29:38,129 CassandraDaemon.java:910 -
Exception encountered during startup
org.apache.cassandra.exceptions.ConfigurationException: JavaScript user-defined
functions were removed in CASSANDRA-18252. Hooks are planned to be introduced
as part of CASSANDRA-17280
{noformat}
I'm not sure what's going on here, it doesn't seem to be from this patch. I
see other upgrade issues on CASSANDRA-18499, perhaps this is related. I
started the jvm upgrade tests anyway, let's see how that goes.
> Changing listen_address with prefer_local may lead to issues
> ------------------------------------------------------------
>
> Key: CASSANDRA-16718
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16718
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Config
> Reporter: Jan Karlsson
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.x
>
>
> Many container based solution function by assigning new listen_addresses when
> nodes are stopped. Changing the listen_address is usually as simple as
> turning off the node and changing the yaml file.
> However, if prefer_local is enabled, I observed that nodes were unable to
> join the cluster and fail with 'Unable to gossip with any seeds'.
> Trace shows that the changing node will try to communicate with the existing
> node but the response is never received. I assume it is because the existing
> node attempts to communicate with the local address during the shadow round.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
