incubator-accumulo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John W Vines <john.w.vi...@ugov.gov>
Subject Re: init new instance on EC2
Date Thu, 22 Dec 2011 18:28:08 GMT
The bin/start-all.sh script seeds the initial goal state for the master as of 1.4. Goal state
is what drives the actions of the master.

John

----- Original Message -----
| From: "Aaron Cordova" <aaron@cordovas.org>
| To: accumulo-user@incubator.apache.org
| Sent: Thursday, December 22, 2011 1:14:20 PM
| Subject: init new instance on EC2
| I'm setting up a new instance of Accumulo 1.3.5, using the binary
| distribution available on the downloads page, on EC2, using Cloudera's
| distribution of hadoop and zookeeper, and after initialization, upon
| trying to start the master get this error:
| 
| ERROR: Problem getting real goal state:
| org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode
| = NoNode for
| /accumulo/68ce2daf-57ee-401f-91c6-dc0df0fcaac9/masters/goal_state
| 
| which repeats endlessly. Is the master not creating the right nodes
| under zookeeper? This happens when using a cluster of three zookeeper
| servers as well as when using a single stand-alone, local zookeeper
| server. Also, I'm starting Accumulo thus:
| 
| bin/accumulo logger &
| bin/accumulo tserver &
| bin/accumulo master &
| 
| Could that be the source of the problem? Does one of the startup
| scripts create the proper master nodes? bin/start-here.sh seems to
| have no effect - i.e. no services are started.
| 
| Aaron

Mime
View raw message