[CASSANDRA-2819] Split rpc timeout for read and write ops - ASF JIRA

XML

Word

Printable

JSON

Details

Type: New Feature
Status: Resolved
Priority: Normal
Resolution: Fixed
Fix Version/s: 1.2.0 beta 1
Component/s: None
Labels:
None

Description

Given the vastly different latency characteristics of reads and writes, it makes sense for them to have independent rpc timeouts internally.

Attachments

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

0001-additional-fix-for-2819.patch
22/Jun/12 02:13
4 kB
Vijay
2819-v4.txt
31/Jul/11 20:54
5 kB
Jonathan Ellis
2819-v5-rebased.txt
07/Oct/11 21:28
12 kB
Jonathan Ellis
2819-v8.txt
16/May/12 20:44
24 kB
Jonathan Ellis
2819-v9.txt
21/Jun/12 05:39
26 kB
Jonathan Ellis
c2819.patch
08/Sep/11 03:18
12 kB
Michael Wu
c2819-v6
20/Oct/11 01:37
11 kB
Michael Wu
c2819-v7
17/Nov/11 01:41
14 kB
Michael Wu
rpc-jira.patch
31/Jul/11 05:09
5 kB
Michael Wu

Issue Links

is related to

CASSANDRA-2848 Make the Client API support passing down timeouts

Open

CASSANDRA-3079 Allow the client request scheduler to throw Timeouts

Resolved

relates to

CASSANDRA-959 Allow different timeouts for different classes of operation

Resolved

Activity

People

Assignee:: Jonathan Ellis

Reporter:: Stu Hood

Authors:: Jonathan Ellis

Reviewers:: Vijay

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 24/Jun/11 01:12

Updated:: 16/Apr/19 09:32

Resolved:: 22/Jun/12 17:32