Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 12 Jun 2014 17:29:08 +0000 (UTC)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12717747.1401566304397.119284.1402594148440@arcas>
In-Reply-To: <JIRA.12717747.1401566304397@arcas>
References: <JIRA.12717747.1401566304397@arcas>
Subject: [jira] [Updated] (CASSANDRA-7333) gossipinfo should include the
 generation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-7333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brandon Williams updated CASSANDRA-7333:
----------------------------------------

    Attachment: 7333.txt

Added both the generation and the heartbeat, but kept them lowercase to distinguish them from actual application states.

> gossipinfo should include the generation
> ----------------------------------------
>
>                 Key: CASSANDRA-7333
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7333
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>            Priority: Minor
>             Fix For: 1.2.17, 2.0.9, 2.1 rc2
>
>         Attachments: 7333.txt
>
>
> As the title says, we should include this information in gossipinfo so it's easier to diagnose the generation-from-future type problems.


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