Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 29 May 2014 17:41:02 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12669528.1379620393011.40473.1401385262850@arcas>
In-Reply-To: <JIRA.12669528.1379620393011@arcas>
References: <JIRA.12669528.1379620393011@arcas>
Subject: [jira] [Resolved] (CASSANDRA-6064) Separate single-partition and
 multiple-partition (incl. batch) write timeouts
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Yeschenko resolved CASSANDRA-6064.
------------------------------------------

    Resolution: Not a Problem

"Not a Problem"-ing the issue for now, because I've changed my mind on this.

> Separate single-partition and multiple-partition (incl. batch) write timeouts
> -----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-6064
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6064
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Aleksey Yeschenko
>            Priority: Minor
>             Fix For: 2.0.9
>
>
> We do currently have separate read_request_timeout_in_ms and range_request_timeout_in_ms setting in cassandra.yaml. It would make sense to have similar separation for regular vs. batch writes (incl. inserts with IN on the last part of the partition key), particularly because of the logged batches overhead.


--
This message was sent by Atlassian JIRA
(v6.2#6252)