Jeff Kubina wrote:
If you are doing a lot of ingesting via batch writes (which the Upsess
implies), you might consider increasing tserver.walog.max.size to 2G
instead of 1G (but doing so will cause the loss of more data if a
There is only dataloss if you lose each datanode which is hosting the
blocks of that WAL. Losing a TabletServer does *not* imply data loss.
In the common case, increasing the size of the WAL will just increase
the amount of time it takes to perform recovery of the WAL after a
documentation with accumulo is helpful in finding latency issues too.