It's possible that you're hitting
https://issues.apache.org/jira/browse/CASSANDRA-13009 .
In (simplified) summary, the read query picks the right number of endpoints
fairly early in its execution. Because the down node has not been detected
as down yet, it may be one of the nodes. When this node d
wasn't aware of it earlier.
>
> Will a node in hibernating state that failed joining and subsequently was
> discarded get removed from gossip at some point?
>
> On Wed, Oct 12, 2016 at 5:23 PM, Joel Knighton > wrote:
>
>> 1. A hibernating node is participating in
1. A hibernating node is participating in gossip but intentionally hasn't
yet joined the ring. The two cases where a node would set a hibernating
status are when the node was started with "-Dcassandra.join_ring=False" and
has tokens or when the node was started to replace another node (using
"-Dcas
t; cqlsh:ks> select pk,a from test0 where pk=0 and a=2;
>
> pk | a
> +---
> 0 | 1
> 0 | 2
> 0 | 3
>
> We can verify this claim by applying 11513 Patch to 3.5 Tag and build &
> test for 12003. If it is fixed then we can guarantee the claim. Let me
> k
mn a and its not a static
> column:
>
> select * from test0 where pk=0 and a=2;
>
>
>
> On Wed, Jun 15, 2016 at 12:39 AM, Joel Knighton <
> joel.knigh...@datastax.com> wrote:
>
>> It doesn't seem to be an exact duplicate - CASSANDRA-11513 relies on you
>
DRA-11513
> <https://issues.apache.org/jira/browse/CASSANDRA-11513> locally on 3.5,
> possible duplicate.
>
> On Wed, Jun 15, 2016 at 12:29 AM, Joel Knighton <
> joel.knigh...@datastax.com> wrote:
>
>> There's some precedent for similar issues with static columns in
> validated : true,
>>>>> case_sensitive : false
>>>>> }
>>>>> }
>>>>> }'};
>>>>>
>>>>
>>>>
>>>>
>>>> -
sly, it IS supported because it works
> most of the time. Is this just a result of not enough replicas, and the
> error message is jacked up?
>
> I’m running 2.1.13.
>
> Thanks
>
> Robert
>
>
--
<http://www.datastax.com/>
Joel Knighton
Cassandra Developer | joel.
e the token ranges from down node to other node ? In
> other words in any situation, does repair operation *ever* change token
> ownership ?
>
>
>
> Thanks !
>
--
<http://www.datastax.com/>
Joel Knighton
Cassandra Developer | joel.knigh...@datastax.com
<h
g, Charles wrote:
> The version I’m running is datastax-ddc-3.3.0. It seems not an affected
> version…
>
>
>
> *From:* Joel Knighton [mailto:joel.knigh...@datastax.com]
> *Sent:* Tuesday, May 03, 2016 1:31 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re: Decommiss
02, 8719281186367503476,
> 8743407730212179670, 8782996992749946235, 8848834787326682329,
> 8913871967919712952, 9044250345847868181, 9184734792478964742,
> 955142821741666815, 998590089428154995] for /10.240.131.52
>
>
>
> 10.240.131.52 is the node I decommission
FO [GossipStage:83] 2016-04-07 16:38:07,861 StorageService.java:1914 -
> Removing tokens[*BLAH*] for /10.1.200.14
>
>
>
> Thanks !
>
--
<http://www.datastax.com/>
Joel Knighton
Cassandra Developer | joel.knigh...@datastax.com
<https://www.linkedin.com/com
gt; Thanks,
>
> Oleg
>
>
--
<http://www.datastax.com/>
Joel Knighton
Cassandra Developer | joel.knigh...@datastax.com
<https://www.linkedin.com/company/datastax>
<https://www.facebook.com/datastax> <https://twitter.com/datastax>
<https://plus.google.com/+Datastax/about>
<http://feeds.feedburner.com/datastax> <https://github.com/datastax/>
13 matches
Mail list logo
