Hypertable+KFS configure logs.
Now, the hypertable can run as bin/start-all -servers.sh local
but can't run as bin/start-all-servers.sh kosmos.
Error Logs:
if conf/hypertable.cfg change the wrong kfs ports, the errors of
Hypertable.Master.log seems like the following.
1215947994 ERROR Hypertable.Master : run (/root/hypertable/hypertable/src/cc/Hypertable/Master/RequestHandlerRegisterServer.cc:49): Hypertable::Exception: Error mkdirs DFS directory /hypertable/tables/METADATA/default - DFS BROKER i/o error
at virtual void Hypertable::DfsBroker::Client::mkdirs(const Hypertable::String&) (/root/hypertable/hypertable/src/cc/DfsBroker/Lib/Client.cc:513)
at virtual void Hypertable::DfsBroker::Client::mkdirs(const Hypertable::String&) (/root/hypertable/hypertable/src/cc/DfsBroker/Lib/Client.cc:510): No route to host
now the kfs up and hypertable.master.log ERROR is :
1215948200 ERROR Hypertable.Master : (/root/hypertable/hypertable/src/cc/Hypertable/Master/Master.cc:451) METADATA update error (row_key = 0: : DFS BROKER i/o error)
so lead to the Hypertable.master can't up
1215948306 ERROR hypertable : (/root/hypertable/hypertable/src/cc/AsyncComm/Comm.cc:207) No connection for 10.0.0.205:38050
1215948306 WARN hypertable : (/root/hypertable/hypertable/src/cc/Hypertable/Lib/MasterClient.cc:224) Comm::send_request to 10.0.0.205:38050 failed - COMM not connected
1 Comments:
Above problems caused by KFS
there is sth wrong with configure
after add chunkdir in the machine.cfg, the problems go away.
Post a Comment
Subscribe to Post Comments [Atom]
<< Home