[ https://issues.apache.org/jira/browse/CASSANDRA-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylvain Lebresne resolved CASSANDRA-4351. ----------------------------------------- Resolution: Fixed Reviewer: jbellis Assignee: Sylvain Lebresne Alright, 0002 committed. I don't know if we want to bother with the change to M3P then, but we can always do that in another ticket in any case, so closing that one now. > Consider storing more informations on peers in system tables > ------------------------------------------------------------- > > Key: CASSANDRA-4351 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4351 > Project: Cassandra > Issue Type: Improvement > Components: Core > Reporter: Sylvain Lebresne > Assignee: Sylvain Lebresne > Priority: Minor > Fix For: 1.2.0 beta 2 > > Attachments: 0001-4351.txt, 0002-Save-tokens-as-strings.txt > > > Currently, the only thing we keep in system tables about other peers is their > token and IP addresses. We should probably also record the new ring_id, but > since CASSANDRA-4018 makes system table easily queriable, may it could be > worth adding some more information (basically most of what we gossip could be > a candidate (schema UUID, status, C* version, ...)) as a simple way to expose > the ring state to users (even if it's just a "view" of the ring state from > one specific node I believe it's still nice). > Of course that means storing information that may not be absolutely needed by > the server, but I'm not sure there is much harm to that. > Note that doing this cleanly may require changing the schema of current > system tables but as long as we do that in the 1.2 timeframe it's ok (since > the concerned system table 'local' and 'peers' are news anyway). -- 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