[ 
https://issues.apache.org/jira/browse/CASSANDRA-15263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16903746#comment-16903746
 ] 

Benedict commented on CASSANDRA-15263:
--------------------------------------

Thanks [~ferozshaik...@gmail.com], this has the complete messages.  
Unfortunately I just noticed I didn't push my most recent version for you to 
use, and so we do not have the affected table name in the message.  If you pull 
the branch again and rebuild, these messages should print the table name as 
well, so you can more easily source the affected sstables (and I can take a 
look at the relevant schema definition)

> 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, stack_trace.txt, 
> system.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
(v7.6.14#76016)

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

Reply via email to