[
https://issues.apache.org/jira/browse/CASSANDRA-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13704538#comment-13704538
]
Jason Brown edited comment on CASSANDRA-5171 at 7/10/13 1:22 PM:
-----------------------------------------------------------------
I thought the patch was reasonable enough for 1.2. If you give me a few days, I
can test it out in our env, and let you know if it borks everything or not.
EDIT: Yeah, will definitely want to test to make sure it's cool with
CASSANDRA-5669 (i.e. they don't collide to not connect at all).
was (Author: jasobrown):
I thought the patch was reasonable enough for 1.2. If you give me a few
days, I can test it out in our env, and let you know if it borks everything or
not.
> Save EC2Snitch topology information in system table
> ---------------------------------------------------
>
> Key: CASSANDRA-5171
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5171
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7.1
> Environment: EC2
> Reporter: Vijay
> Assignee: Vijay
> Priority: Critical
> Fix For: 2.0
>
> 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: http://www.atlassian.com/software/jira
