[jira] Created: (HDFS-1378) Edit log replay should track and report file offsets in case of errors

[Todd Lipcon (JIRA)]

Edit log replay should track and report file offsets in case of errors
--

 Key: HDFS-1378
 URL: https://issues.apache.org/jira/browse/HDFS-1378
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: name-node
Affects Versions: 0.22.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon


Occasionally there are bugs or operational mistakes that result in corrupt edit 
logs which I end up having to repair by hand. In these cases it would be very 
handy to have the error message also print out the file offsets of the last 
several edit log opcodes so it's easier to find the right place to edit in the 
OP_INVALID marker. We could also use this facility to provide a rough estimate 
of how far along edit log replay the NN is during startup (handy when a 2NN has 
died and replay takes a while)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (HDFS-1369) Invalid javadoc reference in FSDatasetMBean.java

[Eli Collins (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HDFS-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eli Collins resolved HDFS-1369.
---

Hadoop Flags: [Reviewed]
  Resolution: Fixed

> Invalid javadoc reference in FSDatasetMBean.java 
> -
>
> Key: HDFS-1369
> URL: https://issues.apache.org/jira/browse/HDFS-1369
> Project: Hadoop HDFS
>  Issue Type: Improvement
>  Components: data-node
>Affects Versions: 0.22.0
>Reporter: Eli Collins
>Assignee: Eli Collins
>Priority: Trivial
> Fix For: 0.22.0
>
> Attachments: hdfs-1369-1.patch
>
>
> FSDatasetMBean.java references non-existant class DataNodeStatisticsMBean, I 
> believe it meant to reference DataNodeActivityMBean.
> After this patch the javadoc and javadoc-dev targets run cleanly:
> {noformat}
>  [exec] -1 overall.  
>  [exec] 
>  [exec] +1 @author.  The patch does not contain any @author tags.
>  [exec] 
>  [exec] -1 tests included.  The patch doesn't appear to include any 
> new or modified tests.
>  [exec] Please justify why no new tests are 
> needed for this patch.
>  [exec] Also please list what manual steps were 
> performed to verify this patch.
>  [exec] 
>  [exec] +1 javadoc.  The javadoc tool did not generate any warning 
> messages.
>  [exec] 
>  [exec] +1 javac.  The applied patch does not increase the total 
> number of javac compiler warnings.
>  [exec] 
>  [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
> warnings.
>  [exec] 
>  [exec] +1 release audit.  The applied patch does not increase the 
> total number of release audit warnings.
>  [exec] 
>  [exec] +1 system tests framework.  The patch passed system tests 
> framework compile.
> {noformat}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.