[jira] [Created] (HDFS-4525) Provide an API for knowing that whether file is closed or not.

Uma Maheswara Rao G created HDFS-4525: - Summary: Provide an API for knowing that whether file is closed or not. Key: HDFS-4525 URL: https://issues.apache.org/jira/browse/HDFS-4525 Project: Hadoop

[jira] [Resolved] (HDFS-4524) Update SnapshotManager#snapshottables when loading fsimage

[ https://issues.apache.org/jira/browse/HDFS-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE resolved HDFS-4524. -- Resolution: Fixed Fix Version/s: Snapshot (HDFS-2802) I have committed th

Re: VOTE: HDFS-347 merge

On Fri, Feb 22, 2013 at 6:32 PM, Tsz Wo Sze wrote: > Another > substantive concern is that HDFS-347 is not as well tested as > HDFS-2246. So, we should keep HDFS-2246 around for sometime and remove > it later. Is this the usual practice? > I'm proposing we do just that - keep HDFS-2246 around

Re: VOTE: HDFS-347 merge

Eli, please see my earlier response below. On Wed, Feb 20, 2013 at 5:12 PM, Aaron T. Myers wrote: > Given that the only substantive concerns with HDFS-347 seem to be about > Windows support for local reads, for now we only merge this branch to trunk. Another substantive concern is that HDFS-3

[jira] [Created] (HDFS-4524) Update SnapshotManager#snapshottables when loading fsimage

Jing Zhao created HDFS-4524: --- Summary: Update SnapshotManager#snapshottables when loading fsimage Key: HDFS-4524 URL: https://issues.apache.org/jira/browse/HDFS-4524 Project: Hadoop HDFS Issue Type

[jira] [Created] (HDFS-4523) Fix concat for snapshots

Tsz Wo (Nicholas), SZE created HDFS-4523: Summary: Fix concat for snapshots Key: HDFS-4523 URL: https://issues.apache.org/jira/browse/HDFS-4523 Project: Hadoop HDFS Issue Type: Sub-ta

[jira] [Resolved] (HDFS-4269) DatanodeManager#registerDatanode rejects all datanode registrations from localhost in single-node developer setup

[ https://issues.apache.org/jira/browse/HDFS-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik resolved HDFS-4269. -- Resolution: Fixed Committed to branch-2. Thanks Chris. > DatanodeManage

Re: VOTE: HDFS-347 merge

On Thu, Feb 21, 2013 at 1:24 PM, Chris Douglas wrote: > On Wed, Feb 20, 2013 at 5:12 PM, Aaron T. Myers wrote: >> Given that the only substantive concerns with HDFS-347 seem to be about >> Windows support for local reads, for now we only merge this branch to >> trunk. Support for doing HDFS-2246

[jira] [Created] (HDFS-4522) LightWeightGSet expects incrementing a volatile to be atomic

Colin Patrick McCabe created HDFS-4522: -- Summary: LightWeightGSet expects incrementing a volatile to be atomic Key: HDFS-4522 URL: https://issues.apache.org/jira/browse/HDFS-4522 Project: Hadoop

Re: VOTE: HDFS-347 merge

On Thu, Feb 21, 2013 at 1:24 PM, Chris Douglas wrote: > On Wed, Feb 20, 2013 at 5:12 PM, Aaron T. Myers wrote: >> Given that the only substantive concerns with HDFS-347 seem to be about >> Windows support for local reads, for now we only merge this branch to >> trunk. Support for doing HDFS-2246

Build failed in Jenkins: Hadoop-Hdfs-trunk #1324

See Changes: [suresh] HDFS-4222. NN is unresponsive and loses heartbeats from DNs when configured to use LDAP and LDAP has issues. Contributed by Xiaobo Peng and Suresh Srinivas. [bobby] amendment to HADOOP-9112 fix return codes (S

Hadoop-Hdfs-trunk - Build # 1324 - Failure

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1324/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 10815 lines...] Running org.apache.hadoop.fs.viewfs.TestV

[jira] [Resolved] (HDFS-2124) Namenode HA using Backup Namenode as Hot Standby

[ https://issues.apache.org/jira/browse/HDFS-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G resolved HDFS-2124. --- Resolution: Won't Fix Hot standby functionality acheived by shared storage approach in

[jira] [Resolved] (HDFS-2166) Datanodes should send block reports to both Active and Standby Namenodes.

[ https://issues.apache.org/jira/browse/HDFS-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G resolved HDFS-2166. --- Resolution: Duplicate This is also addressed by HDFS-1971 > Datanodes

[jira] [Resolved] (HDFS-2165) The Intelligent Clients should switch dynamically according to the Namenode switchover & the operations that fail during the switching should be retried on the newly Acti

[ https://issues.apache.org/jira/browse/HDFS-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G resolved HDFS-2165. --- Resolution: Duplicate HDFS-1973 implemented such mechanism.. > The In

[jira] [Resolved] (HDFS-2164) Namenode supports Active and Standby modes; Standby Namenode should be able to able to take up the Active role dynamically, without losing any data.

[ https://issues.apache.org/jira/browse/HDFS-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G resolved HDFS-2164. --- Resolution: Won't Fix HDFS-1623 already have such machanism by keeping states

[jira] [Resolved] (HDFS-2163) HA Agent should perform Active Namenode Election and should trigger the failover when Active Namenode goes down

[ https://issues.apache.org/jira/browse/HDFS-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G resolved HDFS-2163. --- Resolution: Duplicate HDFS-3042 already addressed this.. > HA Agent s