cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ivan (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1664) NetworkTopologyStrategy + DCQUORUM
Date Sat, 20 Nov 2010 02:33:14 GMT


ivan commented on CASSANDRA-1664:

The need patch was born to optimize read when networktopologystrategy is used. Optimization
is done in NetrworkTopologyStrategy.calculateNaturalEndpoint (for a read request just servers
in local dc provided). I think we must separate read and write requests in this method.
All other modificaton is needed because StorageProxy  can decide which type of request arrived.

> NetworkTopologyStrategy + DCQUORUM
> ----------------------------------
>                 Key: CASSANDRA-1664
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7 beta 1
>         Environment: Linux 2.6.18
> JVM 6b11
>            Reporter: ivan
>             Fix For: 0.7.1
>         Attachments: 1664_v2.txt, ntrs.patch
> We experience TSocket: timed out reading expections randomly using DCQUORUM.
> In log we see that sometimes responses are not sent to client.
> Read requests are sent to all cluster members instead of member of a DC.
> Attached patch adds a new commandType argument to *NaturalEndpoint methods.
> It's needed to separate endpoint list for read and write commands, so for read requests
endpoint list will contain servers in local DC.
> For write requests endpoints provided in all DCs.
> In DatacenterQuorumResponseHandler.response signal is not sent in some cases.
> (In this case we experienced timed out reading exceptions.)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message