Most likely than not, your tservers are registering themselves in zookeeper as 127.0.0.1. This will cause the master, or any node really, to think the tserver is local.
When a tserver starts, it will register it's location in zookeeper. They will use the location in the slaves file as a guidance for which IP address it should use to report as. So if you update the slaves file to use actual ip/hosts instead of localhost, it should resolve this issue. John On Sat, Sep 21, 2013 at 5:36 PM, buttercream <[email protected] > wrote: > I am new to Accumulo, so you'll have to forgive some of the naive > questions. > When I see the master trying to connect to it's own 9996, does that > indicate > that it thinks there should be a tablet server running on that node? If so, > what do I need to configure to specify that a tablet server is not running > on the master node? If that is not the case, what exactly is the master > trying to do connecting to its own 9996 port? > > > > -- > View this message in context: > http://apache-accumulo.1065345.n5.nabble.com/Thrift-Transport-Exception-on-Master-tp5488p5490.html > Sent from the Users mailing list archive at Nabble.com. >
