Github user dlmarion commented on the issue:
https://github.com/apache/accumulo/pull/176
May want to point out https://issues.apache.org/jira/browse/HDFS-3702 as an
option starting with Hadoop 2.8, so that if the node goes down and can't be
brought back up, you can still recover using
Github user joshelser commented on the issue:
https://github.com/apache/accumulo/pull/176
> so that if the node goes down and can't be brought back up, you can still
recover using the WAL.
I'm not sure I understand the reasoning behind that logic (admittedly, it's
"early"). S
Github user dlmarion commented on the issue:
https://github.com/apache/accumulo/pull/176
> I'm not sure I understand the reasoning behind that logic (admittedly,
it's "early"). Specifically, how would a failure of the local node be any
different than a failure of a non-local DN in the
Github user joshelser commented on the issue:
https://github.com/apache/accumulo/pull/176
> It might be how we create/use the WAL. It's possible that a tserver can
create a WAL and open an output stream to the first block, but never actually
write any data to it (see ACCUMULO-4004). I
Github user dlmarion commented on the issue:
https://github.com/apache/accumulo/pull/176
ACCUMULO-4000 has some information too. It's not always seen during
decommissioning though.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user keith-turner commented on the issue:
https://github.com/apache/accumulo/pull/176
> May want to point out https://issues.apache.org/jira/browse/HDFS-3702 as
an option starting with Hadoop 2.8, so that if the node goes down and can't be
brought back up, you can still recover
Github user keith-turner commented on the issue:
https://github.com/apache/accumulo/pull/176
merged these changes in commit e0447313ae503925c28b5164c27163009274f03f
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
