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

feroz shaik commented on CASSANDRA-15263:
-----------------------------------------

I figured out that the app deletes using : "DELETE FROM \"sal_purge\" USING 
TIMESTAMP ? WHERE key=? AND column1=?;"; is actually causing range bound 
tombstones. I used sstabledump to know that.

"rows" : [
 {
 "type" : "range_tombstone_bound",
 "start" : {
 "type" : "inclusive",
 "clustering" : [ 
"15e0088cdb99f399290e531a452e4c2c32d547a852607cb2819ff8fbd565ed53", "*" ],
 "deletion_info" : \{ "marked_deleted" : "2019-09-27T06:20:16.033334Z", 
"local_delete_time" : "2019-09-27T06:38:02Z" }
 }
 },

 

But other problems i have is that the sstabledump is erroring out with below 
which may be another problem.bug itself:

Exception in thread "main" java.lang.NullPointerException
 at org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:156)
 at org.apache.cassandra.db.marshal.UTF8Type.toJSONString(UTF8Type.java:66)
 at 
org.apache.cassandra.tools.JsonTransformer.serializeClustering(JsonTransformer.java:347)
 at 
org.apache.cassandra.tools.JsonTransformer.serializeRow(JsonTransformer.java:244)
 at 
org.apache.cassandra.tools.JsonTransformer.serializePartition(JsonTransformer.java:211)
 at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
 at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
 at java.util.Iterator.forEachRemaining(Iterator.java:116)
 at 
java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
 at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
 at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
 at 
java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
 at 
java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
 at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
 at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:485)
 at org.apache.cassandra.tools.JsonTransformer.toJson(JsonTransformer.java:101)
 at org.apache.cassandra.tools.SSTableExport.main(SSTableExport.java:240)

 

My main point of concern now is that I cannot reproduce the error on my lab by 
cqlsh driver with CL-all. 

[~benedict] - since we know this is for sure a bug , when can we expect any 
fix/patch for this? Kindly let us know.

 

 

> 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 Elliott Smith
>            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
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to