[jira] [Created] (CASSANDRA-15361) purge hints

2019-10-17 Thread xiaodong wang (Jira)
xiaodong wang created CASSANDRA-15361:
-

 Summary: purge hints
 Key: CASSANDRA-15361
 URL: https://issues.apache.org/jira/browse/CASSANDRA-15361
 Project: Cassandra
  Issue Type: Task
  Components: Consistency/Hints
Reporter: xiaodong wang


one DC has big sized hints(467G) and will use up the whole directory sooner or 
later and we need to delete it. I ran nodetool truncatehints but it's not 
working. I see from nodetool tpstats there is 2 active hintedhandoff and 40 
pending as follows:

HintedHandoff 2 40 0 0 0

it seems like there is an issue with hintedhandoff which is hung and caused 
nodetool truncatehints not working.

please advise!

Thanks



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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



[jira] [Commented] (CASSANDRA-10990) Support streaming of older version sstables in 3.0

2016-02-29 Thread xiaodong wang (JIRA)

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

xiaodong wang commented on CASSANDRA-10990:
---

Thanks for the prompt response, Yuki.

I did try the upgrade the SSTable and failed. And figured out that the SSTable 
has to be under ///.

After the upgrade,  a few table could be loaded.

I will keep updated if further issues.

> Support streaming of older version sstables in 3.0
> --
>
> Key: CASSANDRA-10990
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10990
> Project: Cassandra
>  Issue Type: Bug
>  Components: Streaming and Messaging
>Reporter: Jeremy Hanna
>Assignee: Paulo Motta
>
> In 2.0 we introduced support for streaming older versioned sstables 
> (CASSANDRA-5772).  In 3.0, because of the rewrite of the storage layer, this 
> became no longer supported.  So currently, while 3.0 can read sstables in the 
> 2.1/2.2 format, it cannot stream the older versioned sstables.  We should do 
> some work to make this still possible to be consistent with what 
> CASSANDRA-5772 provided.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CASSANDRA-10990) Support streaming of older version sstables in 3.0

2016-02-23 Thread xiaodong wang (JIRA)

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

xiaodong wang commented on CASSANDRA-10990:
---

Hi,
   I learnt that this issue has been worked on actively. Could you please share 
the updates/ETA of the fix release? 

   I am currently running into the same issue and get blocked when trying to 
migrating the data from C* 2.1.x to C* 3.3 

Did a few approaches:
* Running the "sstableupgrade" & "sstableloader" on the 2.1.x's snapshots won't 
work because of this issue;
* Due to the CASSANDRA-8110:  within the same 2.1.x cluster running "rebuild" 
on 3.3 DC won't work;


> Support streaming of older version sstables in 3.0
> --
>
> Key: CASSANDRA-10990
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10990
> Project: Cassandra
>  Issue Type: Bug
>  Components: Streaming and Messaging
>Reporter: Jeremy Hanna
>Assignee: Paulo Motta
>
> In 2.0 we introduced support for streaming older versioned sstables 
> (CASSANDRA-5772).  In 3.0, because of the rewrite of the storage layer, this 
> became no longer supported.  So currently, while 3.0 can read sstables in the 
> 2.1/2.2 format, it cannot stream the older versioned sstables.  We should do 
> some work to make this still possible to be consistent with what 
> CASSANDRA-5772 provided.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CASSANDRA-8110) Make streaming backwards compatible

2016-02-23 Thread xiaodong wang (JIRA)

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

xiaodong wang commented on CASSANDRA-8110:
--

Thanks for your prompt response, Paulo.

Some background:

Currently I have a C* 2.1.x cluster and try to migrate the data to C* 3.3. 

Already did a few approaches:

* Set up another 3.3 DC and ran the "rebuild";
* Set up a new 3.3 cluster and ran the "sstableupgrade" & "sstableloader" ;

Both didn't work. 

> Make streaming backwards compatible
> ---
>
> Key: CASSANDRA-8110
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8110
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Streaming and Messaging
>Reporter: Marcus Eriksson
>  Labels: gsoc2016, mentor
> Fix For: 3.x
>
>
> To be able to seamlessly upgrade clusters we need to make it possible to 
> stream files between nodes with different StreamMessage.CURRENT_VERSION



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Comment Edited] (CASSANDRA-8110) Make streaming backwards compatible

2016-02-23 Thread xiaodong wang (JIRA)

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

xiaodong wang edited comment on CASSANDRA-8110 at 2/23/16 8:33 AM:
---

Hi,

I have been facing the same issue while upgrading the C* from 2.1.x to 3.x. 
 Streaming isn't feasible due to the mismatch StreamMessage.CURRENT_VERSION. 

   And the CASSANDRA-10990 also blocks the offline snapshot -> upload 
approach,Yuki Morishita  could you please share the status of this issue?

Thanks!


was (Author: xiaodong):
Hi,

I have been facing the same issue while upgrading the C* from 2.1.x to 3.x. 
 Streaming isn't feasible due to the mismatch StreamMessage.CURRENT_VERSION. 

   And the CASSANDRA-10990 also blocks the offline snapshot -> upload 
approach,@Yuki Morishita  could you please share the status of this issue?

Thanks!

> Make streaming backwards compatible
> ---
>
> Key: CASSANDRA-8110
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8110
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Streaming and Messaging
>Reporter: Marcus Eriksson
>  Labels: gsoc2016, mentor
> Fix For: 3.x
>
>
> To be able to seamlessly upgrade clusters we need to make it possible to 
> stream files between nodes with different StreamMessage.CURRENT_VERSION



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CASSANDRA-8110) Make streaming backwards compatible

2016-02-23 Thread xiaodong wang (JIRA)

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

xiaodong wang commented on CASSANDRA-8110:
--

Hi,

I have been facing the same issue while upgrading the C* from 2.1.x to 3.x. 
 Streaming isn't feasible due to the mismatch StreamMessage.CURRENT_VERSION. 

   And the CASSANDRA-10990 also blocks the offline snapshot -> upload 
approach,@Yuki Morishita  could you please share the status of this issue?

Thanks!

> Make streaming backwards compatible
> ---
>
> Key: CASSANDRA-8110
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8110
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Streaming and Messaging
>Reporter: Marcus Eriksson
>  Labels: gsoc2016, mentor
> Fix For: 3.x
>
>
> To be able to seamlessly upgrade clusters we need to make it possible to 
> stream files between nodes with different StreamMessage.CURRENT_VERSION



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CASSANDRA-10940) sstableloader shuold skip streaming SSTable generated in < 3.0.0

2016-02-22 Thread xiaodong wang (JIRA)

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

xiaodong wang commented on CASSANDRA-10940:
---

Hi,

   I am running into the same issue when trying to load the <3.0 snapshot 
(which seems not be upgradable by sstableupgrade). Could you please share the 
status on the issue? Is it patch available and resolved? Or  still under 
progress?

Thanks,

> sstableloader shuold skip streaming SSTable generated in < 3.0.0
> 
>
> Key: CASSANDRA-10940
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10940
> Project: Cassandra
>  Issue Type: Bug
>  Components: Streaming and Messaging, Tools
>Reporter: Yuki Morishita
>Assignee: Yuki Morishita
>Priority: Minor
> Fix For: 3.0.x, 3.x
>
>
> Since 3.0.0, [streaming does not support SSTable from version less than 
> 3.0.0|https://github.com/apache/cassandra/blob/0f5e780781ce3f0cb3732515dacc7e467571a7c9/src/java/org/apache/cassandra/io/sstable/SSTableSimpleIterator.java#L116].
> {{sstableloader}} should skip those files to be streamed, instead of erroring 
> out like below:
> {code}
> Failed to list files in 
> /home/yuki/.ccm/2.1.11/node1/data/keyspace1/standard1-5242ae50a9b311e585b29dc952593398
> java.lang.NullPointerException
> java.lang.RuntimeException: Failed to list files in 
> /home/yuki/.ccm/2.1.11/node1/data/keyspace1/standard1-5242ae50a9b311e585b29dc952593398
> at 
> org.apache.cassandra.db.lifecycle.LogAwareFileLister.list(LogAwareFileLister.java:53)
> at 
> org.apache.cassandra.db.lifecycle.LifecycleTransaction.getFiles(LifecycleTransaction.java:544)
> at 
> org.apache.cassandra.io.sstable.SSTableLoader.openSSTables(SSTableLoader.java:76)
> at 
> org.apache.cassandra.io.sstable.SSTableLoader.stream(SSTableLoader.java:165)
> at org.apache.cassandra.tools.BulkLoader.main(BulkLoader.java:101)
> Caused by: java.lang.NullPointerException
> at 
> org.apache.cassandra.io.sstable.format.SSTableReader.openForBatch(SSTableReader.java:421)
> at 
> org.apache.cassandra.io.sstable.SSTableLoader.lambda$openSSTables$186(SSTableLoader.java:121)
> at 
> org.apache.cassandra.io.sstable.SSTableLoader$$Lambda$18/712974096.apply(Unknown
>  Source)
> at 
> org.apache.cassandra.db.lifecycle.LogAwareFileLister.lambda$innerList$178(LogAwareFileLister.java:75)
> at 
> org.apache.cassandra.db.lifecycle.LogAwareFileLister$$Lambda$29/1191654595.test(Unknown
>  Source)
> at 
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174)
> at 
> java.util.TreeMap$EntrySpliterator.forEachRemaining(TreeMap.java:2965)
> at 
> java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:512)
> at 
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:502)
> at 
> java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
> at 
> java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at 
> java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
> at 
> org.apache.cassandra.db.lifecycle.LogAwareFileLister.innerList(LogAwareFileLister.java:77)
> at 
> org.apache.cassandra.db.lifecycle.LogAwareFileLister.list(LogAwareFileLister.java:49)
> ... 4 more
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)