Ok, I will open a JIRA for that later today...
On the RS side, should we break the loop? Or kill the server? Because not
being able to read the log might end with rs inconsistencies?
JM
Le 1 mai 2013 14:51, Ted Yu yuzhih...@gmail.com a écrit :
Ideally HBCK should sideline corrupted log file
end with rs inconsistencies?
JM
Le 1 mai 2013 14:51, Ted Yu yuzhih...@gmail.com a écrit :
Ideally HBCK should sideline corrupted log file so that region server can
start.
Cheers
On Wed, May 1, 2013 at 11:48 AM, Nick Dimiduk ndimi...@gmail.com wrote:
Detecting the condition, printing
Ideally HBCK should sideline corrupted log file so that region server can
start.
Cheers
On Wed, May 1, 2013 at 11:48 AM, Nick Dimiduk ndimi...@gmail.com wrote:
Detecting the condition, printing the warning, and breaking the loop sounds
like an urgent bandaid solution to me.
-n
On Tue, Apr
When a log file (into /hbase/.logs) is corrupted, HBase is not able to
start because it tries to read it again and again.
Also, there is nothing into HBCK to detect that.
Should we have something to check that? Like in hbck, we can simply try to
open the log file, and read it? To report the
