cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Schuller (Updated) (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-3892) improve TokenMetadata abstraction, naming - audit current uses
Date Mon, 13 Feb 2012 07:18:59 GMT


Peter Schuller updated CASSANDRA-3892:

    Attachment: CASSANDRA-3892-draft-v4.txt

{{v4}} uses the terminology "joined endpoints" for what was previously the un-named things
in the tokenToEndpointMap (they did not quite correspond to "normal", because a node could
simultaneously be moving and be in the tokenToEndpointMap - same for leaving).

We now have:

* Joined endpoints - fully joined, taking reads (previously unnamed, was in tokenToEndpointMap)
* Moving endpoints - joined endpoints that are also currently moving.
* Joining endpoints - not yet joined, in the process of joining (previously "bootstrap tokens").
* Leaving endpoints

Some of the methods have a bit less obnoxious names now than in {{v3}}.

> improve TokenMetadata abstraction, naming - audit current uses
> --------------------------------------------------------------
>                 Key: CASSANDRA-3892
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Peter Schuller
>            Assignee: Peter Schuller
>         Attachments: CASSANDRA-3892-draft-v2.txt, CASSANDRA-3892-draft-v3.txt, CASSANDRA-3892-draft-v4.txt,
> CASSANDRA-3417 has some background. I want to make the distinction more clear between
looking at the ring from different perspectives (reads, writes, others) and adjust naming
to be more clear on this. I also want to go through each use case and try to spot any subtle
pre-existing bugs that I almost introduced in CASSANDRA-3417, had not Jonathan caught me.
> I will submit a patch soonish.

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


View raw message