[
https://issues.apache.org/jira/browse/CASSANDRA-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026896#comment-13026896
]
Sylvain Lebresne commented on CASSANDRA-2536:
---------------------------------------------
I'll hijack this conversation by saying that I think we should start
advertising that people should try to keep their server clocks in sync unless
they have a good reason not too (which would legitimize the fact that
"timestamp comparison is good enough"). Counter removes for instance use server
side timestamps and would be screwed up by diverging clocks (and by that I mean
more screwed up than they already are by design). And really, is there any
reason not to install a ntpd server in the first place anyway?
> Schema disagreements when using connections to multiple hosts
> -------------------------------------------------------------
>
> Key: CASSANDRA-2536
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2536
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8 beta 1
> Environment: Two node 0.8-beta1 cluster with one seed and JNA.
> Reporter: Tyler Hobbs
> Assignee: Tyler Hobbs
> Attachments: 2536-compare-timestamp.txt, schema_disagree.py
>
>
> If you have two thrift connections open to different nodes and you create a
> KS using the first, then a CF in that KS using the second, you wind up with a
> schema disagreement even if you wait/sleep after creating the KS.
> The attached script reproduces the issue using pycassa (1.0.6 should work
> fine, although it has the 0.7 thrift-gen code). It's also reproducible by
> hand with two cassandra-cli sessions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
