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

Michael Kjellman commented on CASSANDRA-4813:
---------------------------------------------

Also, while we don't throw the EOF anymore further down the stack as far as I 
can tell from my testing, the net result is an IOException being thrown in the 
Reducer.
                
> Problem using BulkOutputFormat while streaming several SSTables 
> simultaneously from a given node.
> -------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-4813
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4813
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.1.0
>         Environment: I am using SLES 10 SP3, Java 6, 4 Cassandra + Hadoop 
> nodes, 3 Hadoop only nodes (datanodes/tasktrackers), 1 namenode/jobtracker. 
> The machines used are Six-Core AMD Opteron(tm) Processor 8431, 24 cores and 
> 33 GB of RAM. I get the issue on both cassandra 1.1.3, 1.1.5 and I am using 
> Hadoop 0.20.2.
>            Reporter: Ralph Romanos
>            Assignee: Yuki Morishita
>            Priority: Minor
>              Labels: Bulkoutputformat, Hadoop, SSTables
>             Fix For: 1.2.0
>
>         Attachments: 4813.txt
>
>
> The issue occurs when streaming simultaneously SSTables from the same node to 
> a cassandra cluster using SSTableloader. It seems to me that Cassandra cannot 
> handle receiving simultaneously SSTables from the same node. However, when it 
> receives simultaneously SSTables from two different nodes, everything works 
> fine. As a consequence, when using BulkOutputFormat to generate SSTables and 
> stream them to a cassandra cluster, I cannot use more than one reducer per 
> node otherwise I get a java.io.EOFException in the tasktracker's logs and a 
> java.io.IOException: Broken pipe in the Cassandra logs.

--
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

Reply via email to