Benedict commented on CASSANDRA-15263:

Sorry [~ferozshaik...@gmail.com], I should have been clearer.  This may have a 
user visible impact, with the affected queries not responding from 3.0 nodes 
contacted by a 2.1 node when this error occurs.  This will have an availability 
impact, which might result in failed queries.  Once fully upgraded the problem 
will resolve, and there will be no lasting impact.  Depending on your cluster 
topology, you might be able to upgrade without any queries failing, only having 
reduced tolerance to node failures until the upgrade completes.

> LegacyLayout RangeTombstoneList throws java.lang.NullPointerException: null
> ---------------------------------------------------------------------------
>                 Key: CASSANDRA-15263
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15263
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Cluster/Schema
>            Reporter: feroz shaik
>            Assignee: Benedict
>            Priority: Normal
>              Labels: 2.1.16, 3.11.4
>         Attachments: sample.system.log, schema.txt, 
> sstabledump_sal_purge_d03.json, sstablemetadata_sal_purge_d03, 
> stack_trace.txt, system.log, system.log, system.log, system.log, 
> system_latest.log
> We have  hit a problem today while upgrading from 2.1.16 to 3.11.4.
> we encountered this as soon as the first node started up with 3.11.4 
> The full error stack is attached - [^stack_trace.txt] 
> The below errors continued in the log file as long as the process was up.
> ERROR [Native-Transport-Requests-12] 2019-08-06 03:00:47,135 
> ErrorMessage.java:384 - Unexpected exception during request
>  java.lang.NullPointerException: null
>  ERROR [Native-Transport-Requests-8] 2019-08-06 03:00:48,778 
> ErrorMessage.java:384 - Unexpected exception during request
>  java.lang.NullPointerException: null
>  ERROR [Native-Transport-Requests-13] 2019-08-06 03:00:57,454 
> The nodetool version says 3.11.4 and the no of connections on native por t- 
> 9042 was similar to other nodes. The exceptions were scary that we had to 
> call off the change. Any help and insights to this problem from the community 
> is appreciated.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to