[
https://issues.apache.org/jira/browse/HBASE-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliott Clark updated HBASE-8468:
---------------------------------
Attachment: HBASE-8468-0.patch
Copy the config of the context in so that hbase zookeeper info is usable in the
comitter.
> IntegrationTestImportTsv fails on a cluster
> -------------------------------------------
>
> Key: HBASE-8468
> URL: https://issues.apache.org/jira/browse/HBASE-8468
> Project: HBase
> Issue Type: Bug
> Components: test
> Affects Versions: 0.95.0
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Attachments: HBASE-8468-0.patch
>
>
> It appears that the JobLaunchingOuputCommitter is not properly picking up the
> configuration.
> the quorum is set in the job conf when I look at it in the yarn mr history
> manager. However as you can see below the zk session is still defaulting to
> 127.0.0.1
> {code}
> 2013-04-30 10:18:54,728 INFO [CommitterEvent Processor #1-SendThread()]
> org.apache.zookeeper.ClientCnxn: Opening socket connection to server
> /127.0.0.1:2181
> 2013-04-30 10:18:54,729 INFO [CommitterEvent Processor #1]
> org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: The identifier of
> this process is hconnection-0x1704de3e
> 2013-04-30 10:18:54,731 WARN [CommitterEvent Processor
> #1-SendThread(localhost:2181)] org.apache.zookeeper.ClientCnxn: Session 0x0
> for server null, unexpected error, closing socket connection and attempting
> reconnect
> java.net.ConnectException: Connection refused
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> at
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
> at
> org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:286)
> at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1041)
> 2013-04-30 10:18:54,847 WARN [CommitterEvent Processor #1]
> org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: Possibly transient
> ZooKeeper, quorum=localhost:2181,
> exception=org.apache.zookeeper.KeeperException$ConnectionLossException:
> KeeperErrorCode = ConnectionLoss for /hbase/hbaseid
> 2013-04-30 10:18:54,847 INFO [CommitterEvent Processor #1]
> org.apache.hadoop.hbase.util.RetryCounter: Sleeping 2000ms before retry #1...
> 2013-04-30 10:18:54,882 INFO [RMCommunicator Allocator]
> org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: Before
> Scheduling: PendingReds:0 ScheduledMaps:0 ScheduledReds:0 AssignedMaps:0
> AssignedReds:1 CompletedMaps:1 CompletedReds:1 ContAlloc:2 ContRel:0
> HostLocal:0 RackLocal:1
> 2013-04-30 10:18:55,839 INFO [CommitterEvent Processor
> #1-SendThread(localhost:2181)] org.apache.zookeeper.ClientCnxn: Opening
> socket connection to server localhost/127.0.0.1:2181
> 2013-04-30 10:18:55,840 WARN [CommitterEvent Processor
> #1-SendThread(localhost:2181)] org.apache.zookeeper.ClientCnxn: Session 0x0
> for server null, unexpected error, closing socket connection and attempting
> reconnect
> java.net.ConnectException: Connection refused
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> at
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
> at
> org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:286)
> at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1041)
> 2013-04-30 10:18:55,887 INFO [RMCommunicator Allocator]
> org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: Received
> completed container container_1367340870656_0004_01_000003
> 2013-04-30 10:18:55,888 INFO [RMCommunicator Allocator]
> org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: After Scheduling:
> PendingReds:0 ScheduledMaps:0 ScheduledReds:0 AssignedMaps:0 AssignedReds:0
> CompletedMaps:1 CompletedReds:1 ContAlloc:2 ContRel:0 HostLocal:0 RackLocal:1
> 2013-04-30 10:18:55,888 INFO [AsyncDispatcher event handler]
> org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl: Diagnostics
> report from attempt_1367340870656_0004_r_000000_0: Container killed by the
> ApplicationMaster.
> {code}
--
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
