cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7205) Node never know a table has been DROP or CREATE if its gossip is disabled while executing this query
Date Tue, 13 May 2014 15:51:16 GMT

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

Brandon Williams commented on CASSANDRA-7205:
---------------------------------------------

It very well could be, yes.  If we can't repro on 2.0 head let's close this.

> Node never know a table has been DROP or CREATE if its gossip is disabled while executing
this query
> ----------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-7205
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7205
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Cassandra 2.0.6
>            Reporter: Zhe Yang
>            Assignee: Michael Shuler
>
> I'm using Cassandra 2.0.6 and I have 8 nodes. I'm doing some tests by using operations
below:
> disable gossip of node A;
> check the status by nodetool in other node, node A is Down now;
> use cqlsh connecting an "Up" node and create a table;
> enable gossip of node A;
> check the status, all nodes are "Up" now.
> Then I find that node A doesn't know this table has been created. Both its own cql shell
and nodetool cfstats tell me the table doesn't exist. Even waiting for a few minutes to get
the "eventual consistency" final status, node A still doesn't know this table.  And I find
if each node knows there is a table but I drop it when one node's gossip is disabled, this
node will never know the table has been dropped.
> Is this a bug?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message