Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CAF34D9D4 for ; Tue, 23 Oct 2012 20:29:14 +0000 (UTC) Received: (qmail 78535 invoked by uid 500); 23 Oct 2012 20:29:14 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 78504 invoked by uid 500); 23 Oct 2012 20:29:14 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 78439 invoked by uid 99); 23 Oct 2012 20:29:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Oct 2012 20:29:14 +0000 Date: Tue, 23 Oct 2012 20:29:14 +0000 (UTC) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Message-ID: <830225651.17896.1351024154538.JavaMail.jiratomcat@arcas> In-Reply-To: <295995226.50683.1350377943877.JavaMail.jiratomcat@arcas> Subject: [jira] [Updated] (CASSANDRA-4813) Problem using BulkOutputFormat while streaming several SSTables simultaneously from a given node. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-4813: -------------------------------------- Priority: Minor (was: Major) Affects Version/s: (was: 1.1.5) (was: 1.1.3) 1.1.0 Fix Version/s: 1.2.0 If we need to change streaming protocol to fix this then we should target 1.2. > 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 > > > 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