cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-4812) Require enabling cross-node timeouts
Date Wed, 17 Oct 2012 17:36:04 GMT


Vijay updated CASSANDRA-4812:

    Attachment: 0001-CASSANDRA-4812-v2.patch

Why not just have each node use local config file's value instead of messing w/ header?
Some how i expected this question :), the idea was to save some bytes by using header. (Now
i am thinking it is micro optimization :))

v2 attached doesn't mess with header
> Require enabling cross-node timeouts
> ------------------------------------
>                 Key: CASSANDRA-4812
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.2.0 beta 1
>            Reporter: Jonathan Ellis
>            Assignee: Vijay
>            Priority: Minor
>             Fix For: 1.2.0 beta 2
>         Attachments: 0001-CASSANDRA-4812.patch, 0001-CASSANDRA-4812-v2.patch
> Deploying 1.2 against a cluster whose clocks are not synchronized will cause *every*
request to timeout.  Suggest adding a {{cross_node_timeout}} option defaulting to false that
users must explicitly enable after installing ntpd.  Otherwise we fall back to the pessimistic
case of assuming the request was forwarded to the replica instantly by the coordinator.

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:

View raw message