Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <8168060.195461295979766662.JavaMail.jira@thor>
Date: Tue, 25 Jan 2011 13:22:46 -0500 (EST)
From: "Jeremy Hanna (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Resolved: (CASSANDRA-2052) Add configurable retry count to
 Hadoop code
In-Reply-To: <2857099.193351295976643885.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jeremy Hanna resolved CASSANDRA-2052.
-------------------------------------

    Resolution: Won't Fix

like Jonathan mentioned, the problems with timing out should be handled with the existing configuration options.

> Add configurable retry count to Hadoop code
> -------------------------------------------
>
>                 Key: CASSANDRA-2052
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2052
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Hadoop
>    Affects Versions: 0.6.9, 0.7.0
>            Reporter: Jeremy Hanna
>
> The Hadoop integration code doesn't do a retry if it times out.  Often people have to tune the batch size and the rpc timeout in order to get it to work.  We should probably have a configurable timeout in there (credit to Jairam - http://www.mail-archive.com/user@cassandra.apache.org/msg08938.html) so that it doesn't just fail the job with a timeout exception.

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