[
https://issues.apache.org/jira/browse/CASSANDRA-15263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16901912#comment-16901912
]
Benedict commented on CASSANDRA-15263:
--------------------------------------
Thanks [[email protected]]. When you say this is one of the oldest and
very first Cassandra implementations, and that legacy mode was thrift, do you
mean that this schema was converted from a thrift schema, and that in the past
it was written to using the thrift data model?
If so, this could very well explain the problem.
The problem appears to relate to range tombstones, i.e. those that cover a
range of CQL rows within a partition. These were intended to permit row
deletions in the CQL data model, but it _was_ possible to construct them
yourself using the thrift data model API, and it was possible to create range
tombstones that could cause problems.
It's _possible_ this is what is happening, but more information would help us
figure out if so, and if so in what way and how it might be mitigated for you.
More information about how you delete data, particularly if you delete multiple
rows (essentially range deletions), and preferably access to some affected
sstables would be really helpful. It may be hard to establish which sstables
are affected, but we could potentially supply you with a build that would
report this information in the error, although this would require you to
upgrade again, perhaps in a development environment.
> 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
> Priority: Normal
> Labels: 2.1.16, 3.11.4
> Attachments: schema.txt, stack_trace.txt
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
