Re: Thinking ahead to 2.4

Update: We are now down to just 8 blockers of which 4 are already PA. I know it's getting in good shape per our QE gang too. If things go well, I plan to create an RC later half of next week. thanks, Arun On Mar 11, 2014, at 7:11 AM, Arun C Murthy wrote: > Sorry, the previous link had a bug,

[jira] [Created] (HDFS-6106) Reduce default for dfs.namenode.path.based.cache.refresh.interval.ms

Colin Patrick McCabe created HDFS-6106: -- Summary: Reduce default for dfs.namenode.path.based.cache.refresh.interval.ms Key: HDFS-6106 URL: https://issues.apache.org/jira/browse/HDFS-6106 Project:

[jira] [Resolved] (HDFS-6104) TestFsLimits#testDefaultMaxComponentLength Fails on branch-2

[ https://issues.apache.org/jira/browse/HDFS-6104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA resolved HDFS-6104. - Resolution: Invalid Assignee: (was: Mit Desai) Closing this issue because the test was r

[jira] [Created] (HDFS-6105) NN web UI for DN list loads the same jmx page three times.

Kihwal Lee created HDFS-6105: Summary: NN web UI for DN list loads the same jmx page three times. Key: HDFS-6105 URL: https://issues.apache.org/jira/browse/HDFS-6105 Project: Hadoop HDFS Issue Ty

Jenkins build is back to normal : Hadoop-Hdfs-trunk #1701

See

[jira] [Created] (HDFS-6104) TestFsLimits#testDefaultMaxComponentLength Fails on branch-2

Mit Desai created HDFS-6104: --- Summary: TestFsLimits#testDefaultMaxComponentLength Fails on branch-2 Key: HDFS-6104 URL: https://issues.apache.org/jira/browse/HDFS-6104 Project: Hadoop HDFS Issue T