Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 24 Sep 2013 20:35:03 +0000 (UTC)
From: "Cyril Scetbon (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12670107.1379957085684.11738.1380054903184@arcas>
In-Reply-To: <JIRA.12670107.1379957085684@arcas>
References: <JIRA.12670107.1379957085684@arcas>
Subject: [jira] [Commented] (CASSANDRA-6084) java.io.IOException: Could not
 get input splits
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13776714#comment-13776714 ] 

Cyril Scetbon commented on CASSANDRA-6084:
------------------------------------------

I confirm that I can't reproduce the issue without vnodes. So, with vnodes it works sporadically whereas it always work without. Can you tell me if when you'll work on the vnode support ? in a few days ? a few weeks ? a few hours :)

Thanks Alex
                
> java.io.IOException: Could not get input splits
> -----------------------------------------------
>
>                 Key: CASSANDRA-6084
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6084
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Hadoop
>         Environment: Osx 10.8.5
> Java 1.7
> Cassandra 1.2.10
> Pig 0.9.2/0.11.1
>            Reporter: Cyril Scetbon
>            Assignee: Alex Liu
>
> see http://www.mail-archive.com/user@cassandra.apache.org/msg32414.html
> I've noticed that if I restart Cassandra I get more errors for the first minutes, although it's accessible through cqlsh without issue.
> I have tested on a 1-node (Osx Laptop) and 4-nodes (Ubuntu servers) and got the same error. I tried with version 1.2.6, 1.2.8, 1.2.9, 1.2.10 without success

--
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: http://www.atlassian.com/software/jira