cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samarth Gahire (Created) (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-3740) While using BulkOutputFormat unneccessarily look for the cassandra.yaml file.
Date Fri, 13 Jan 2012 12:14:40 GMT
While using BulkOutputFormat  unneccessarily look for the cassandra.yaml file.

                 Key: CASSANDRA-3740
             Project: Cassandra
          Issue Type: Bug
          Components: Hadoop
    Affects Versions: 1.1
            Reporter: Samarth Gahire
             Fix For: 1.1

I am trying to use BulkOutputFormat to stream the data from map of Hadoop job. I have set
the cassandra related configuration using ConfigHelper ,Also have looked into Cassandra code
seems Cassandra has taken care that it should not look for the cassandra.yaml file.
But still when I run the job i get the following error:

12/01/13 11:30:04 WARN mapred.JobClient: Use GenericOptionsParser for parsing the arguments.
Applications should implement Tool for the same.
12/01/13 11:30:04 INFO input.FileInputFormat: Total input paths to process : 1
12/01/13 11:30:04 INFO mapred.JobClient: Running job: job_201201130910_0015
12/01/13 11:30:05 INFO mapred.JobClient:  map 0% reduce 0%
12/01/13 11:30:23 INFO mapred.JobClient: Task Id : attempt_201201130910_0015_m_000000_0, Status
java.lang.Throwable: Child Error
Caused by: Task process exit with nonzero status of 1.

attempt_201201130910_0015_m_000000_0: Cannot locate cassandra.yaml
attempt_201201130910_0015_m_000000_0: Fatal configuration error; unable to start server.

Also let me know how can i make this cassandra.yaml file available to Hadoop mapreduce job?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message