I found the message in tserver*.out. tserver*.err has 0 in it.
I posted last night, life was good, sat down this morning and saw that
another tserver had crashed, over night, with no activity. ?? In tserver*.out
it again says out of heap space.
ACCUMULO_TSERVER_OPTS=-Xmx2G -Xms1G. I would
You can use start-here.sh on the host in question or `start-server.sh
$hostname tserver`. FWIW, re-invoking start-all should just ignored the
hosts which already have processes running and just start a tserver on
the host that died.
2G should be enough to get a connector and read a table.
Hello everyone! There is going to be an Accumulo Meetup at Hadoop World
next week. I hope you can stop by. Let me know if you have any questions.
http://www.meetup.com/Accumulo-Users-DC/events/206727592/
-Don
Strata NY 2014 Apache Accumulo Meetup
Thursday, October 16, 2014
6:30 PM to 8:30 PM
So start-here.sh does it. Thanks for pointing that out. I was looking all
through the shell commands .
I did try, from the master, start-all.sh and it worked for starting the
tserver, but I noticed that on the master, it increased the number of
processes labeled Main from the usual five to
(for archival purposes)
I (re)stumbled on this and, after digging some more, realized that there
is bigger issue.
https://issues.apache.org/jira/browse/ACCUMULO-3215
Ultimately, the import process in 1.6.0 and 1.6.1 are incorrect and
generate incorrect entries in the accumulo.metadata table
The Fluo project is happy to announce the 1.0.0-alpha-1 release of Fluo.
Fluo is a transaction layer that enables incremental processing on top of
Accumulo. It integrates into Yarn using Apache Twill.
This is the first release of Fluo and is not ready for production use. We
invite developers to
woohoo
Look forward to getting to use this!
On Thu, Oct 9, 2014 at 4:54 PM, Corey Nolet cjno...@gmail.com wrote:
The Fluo project is happy to announce the 1.0.0-alpha-1 release of Fluo.
Fluo is a transaction layer that enables incremental processing on top of
Accumulo. It integrates into
