cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5171) Save EC2Snitch topology information in system table
Date Tue, 09 Jul 2013 17:47:49 GMT


Vijay commented on CASSANDRA-5171:

I've never been thrilled with the default "UNKNOWN-DC" 

I am not a fan either, if we throw an exception node will never start the gossiping.... 
Back in the days, it made sense with the old way of versioning etc. We should probably open
another ticket to discuses this if needed.

I will commit with the nit in few min. Thanks!
> Save EC2Snitch topology information in system table
> ---------------------------------------------------
>                 Key: CASSANDRA-5171
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7.1
>         Environment: EC2
>            Reporter: Vijay
>            Assignee: Vijay
>            Priority: Critical
>             Fix For: 1.2.7
>         Attachments: 0001-CASSANDRA-5171.patch, 0001-CASSANDRA-5171-v2.patch
> EC2Snitch currently waits for the Gossip information to understand the cluster information
every time we restart. It will be nice to use already available system table info similar
to GPFS.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message