[
https://issues.apache.org/jira/browse/CASSANDRA-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johan Oskarsson updated CASSANDRA-1072:
---------------------------------------
Attachment: CASSANDRA-1072.patch
All good points. We have reviewed them and the code, replies below.
1. Is this the kind of ip address situation you are referring to?
A cluster of nodes: A (127.0.0.1), B (127.0.0.2), and C (127.0.0.3) have been
running and are not fully consistent. They're brought back up w/ shuffled ips,
like so: A (127.0.0.2), B (127.0.0.3), and C (127.0.0.1). A has the most
up-to-date view of writes to 127.0.0.1, however, C is now in-charge of writes
to 127.0.0.1. i.e. any writes to A that C had not seen, previously, have now
been lost.
While this is possible, it's not very likely that a production situation would
shuffle the ip addresses of nodes in this way.
A fix with UUIDs is possible but it's beyond the scope of this jira.
2. Valid issue, but it does sound like something of an edge case. For a first
version of 1072 it seems reasonable that instructions for ops would be
sufficient for this problem. If the community then still feels it's a problem
we can look at how to improve the code.
3. To resolve this issue we have borrowed the implementation from
CASSANDRA-1546 (with the added deadlock fix).
4. Brought over implementation written earlier into this patch. Adds a stage
and task that does "repair on write".
We've also refreshed the design doc to reflect these changes.
> Increment counters
> ------------------
>
> Key: CASSANDRA-1072
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1072
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: Johan Oskarsson
> Assignee: Kelvin Kakugawa
> Attachments: CASSANDRA-1072.patch, increment_test.py,
> Incrementcountersdesigndoc.pdf
>
>
> Break out the increment counters out of CASSANDRA-580. Classes are shared
> between the two features but without the plain version vector code the
> changeset becomes smaller and more manageable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
