[jira] [Resolved] (HDFS-2394) Add tests for Namenode active standby states

[ https://issues.apache.org/jira/browse/HDFS-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved HDFS-2394. --- Resolution: Invalid > Add tests for Namenode active standby states > -

[jira] [Resolved] (HDFS-3) processIOError() may cause infinite loop.

[ https://issues.apache.org/jira/browse/HDFS-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-3. Resolution: Not A Problem Looking at trunk {{NNStorage}}, this doesn't seem to be a problem anymore. Neither do we do

[jira] [Resolved] (HDFS-21) unresponsive namenode because of not finding places to replicate

[ https://issues.apache.org/jira/browse/HDFS-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-21. - Resolution: Won't Fix This is a clear effect of tweaking dfs.replication.min. You want your HDFS to guarantee X rep

[jira] [Resolved] (HDFS-10) DFS logging in NameSystem.pendingTransfer consumes all disk space

[ https://issues.apache.org/jira/browse/HDFS-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-10. - Resolution: Won't Fix These things help ops determine HDFS activity. If you do not wish to see them ever, you may t

[jira] [Resolved] (HDFS-9) distcp job failed

[ https://issues.apache.org/jira/browse/HDFS-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-9. Resolution: Incomplete This could've very well been a transient issue. Lets open a new JIRA if this is too frequent. T

[jira] [Created] (HDFS-2727) hdfs.c uses deprecated property dfs.block.size

hdfs.c uses deprecated property dfs.block.size -- Key: HDFS-2727 URL: https://issues.apache.org/jira/browse/HDFS-2727 Project: Hadoop HDFS Issue Type: Sub-task Affects Versions: 0.23.0

[jira] [Resolved] (HDFS-82) recentInvalidateSets in FSNamesystem is not required

[ https://issues.apache.org/jira/browse/HDFS-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-82. - Resolution: Not A Problem This has been resolved on trunk. We only have one set. > recentInvalidate

[jira] [Resolved] (HDFS-92) if hadoop.tmp.dir is under your dfs.data.dir, HDFS will silently wipe out your "name" directory

[ https://issues.apache.org/jira/browse/HDFS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-92. - Resolution: Not A Problem This goes against all recommendations in configuring the directories. I don't see why one

[jira] [Resolved] (HDFS-35) Confusing set replication message

[ https://issues.apache.org/jira/browse/HDFS-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-35. - Resolution: Incomplete Unsure what seems to be the problem here. Those logs are in if-else clauses and represent th

[jira] [Resolved] (HDFS-22) Help information of refreshNodes does not show how to decomission nodes

[ https://issues.apache.org/jira/browse/HDFS-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-22. - Resolution: Not A Problem The current docs: {code} Updates the set of hosts allowed to connect to namenode. Re-read

[jira] [Resolved] (HDFS-47) dead datanodes because of OutOfMemoryError

[ https://issues.apache.org/jira/browse/HDFS-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-47. - Resolution: Not A Problem This has gone stale. FWIW, haven't seen DNs go OOM on its own in recent years. Probably a

Hadoop-Hdfs-22-branch - Build # 124 - Still Failing

See https://builds.apache.org/job/Hadoop-Hdfs-22-branch/124/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 3438 lines...] [mkdir] Created dir: /home/jenkins

[jira] [Resolved] (HDFS-12) "hadoop dfs -put" does not return nonzero status on failure

[ https://issues.apache.org/jira/browse/HDFS-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-12. - Resolution: Not A Problem Fix Version/s: 0.23.0 This has been fixed by the FsCommand revamp on 0.23+.

[jira] [Resolved] (HDFS-55) Change all references of dfs to hdfs in configs

[ https://issues.apache.org/jira/browse/HDFS-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-55. - Resolution: Won't Fix Its all dfs.* and its in Hadoop, and the settings go to hdfs-site.xml. I think that is suffic

[jira] [Resolved] (HDFS-105) Streaming task stuck in MapTask$DirectMapOutputCollector.close

[ https://issues.apache.org/jira/browse/HDFS-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-105. -- Resolution: Cannot Reproduce Hasn't had a similar failure report in two years now. Gone stale, so closing out as

[jira] [Resolved] (HDFS-97) DFS should detect slow links(nodes) and avoid them

[ https://issues.apache.org/jira/browse/HDFS-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-97. - Resolution: Not A Problem We do tend to avoid highly loaded DataNodes (via xceiver counts) which may almost do the

[jira] [Resolved] (HDFS-58) DistributedFileSystem.listPaths with some paths causes directory to be cleared

[ https://issues.apache.org/jira/browse/HDFS-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-58. - Resolution: Cannot Reproduce This has gone stale, and looking at listStatus impls, looks like it could not happen.

[jira] [Resolved] (HDFS-20) fsck -delete doesn't report failures

[ https://issues.apache.org/jira/browse/HDFS-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-20. - Resolution: Not A Problem Currently in NamenodeFsck, if any operation under check() throws an exception, I can veri

[jira] [Resolved] (HDFS-146) Regression: TestInjectionForSimulatedStorage fails with IllegalMonitorStateException

[ https://issues.apache.org/jira/browse/HDFS-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-146. -- Resolution: Cannot Reproduce Hasn't had a failure report in two years now. Gone stale, closing out this and rela

[jira] [Resolved] (HDFS-59) No recovery when trying to replicate on marginal datanode

[ https://issues.apache.org/jira/browse/HDFS-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-59. - Resolution: Not A Problem This has gone stale. We haven't seen this lately. Lets file a new one if we see this agai

[jira] [Resolved] (HDFS-64) delete on dfs hung

[ https://issues.apache.org/jira/browse/HDFS-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-64. - Resolution: Not A Problem This has gone stale, and given that we haven't seen this recently at all, looks like it m

[jira] [Resolved] (HDFS-102) high cpu usage in ReplicationMonitor thread

[ https://issues.apache.org/jira/browse/HDFS-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-102. -- Resolution: Cannot Reproduce This has gone stale. The current structure within BlockManager isn't a list anymore

[jira] [Resolved] (HDFS-36) Handling of deprecated dfs.info.bindAddress and dfs.info.port

[ https://issues.apache.org/jira/browse/HDFS-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-36. - Resolution: Cannot Reproduce Can't reproduce on 1.0+. Setting dfs.http(s).address suffices. > Handl

[jira] [Resolved] (HDFS-104) TestInjectionForSimulatedStorage fails once in a while

[ https://issues.apache.org/jira/browse/HDFS-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-104. -- Resolution: Cannot Reproduce Hasn't had a failure report in two years now. Gone stale, closing out this and rela

[jira] [Created] (HDFS-2729) Update BlockManager's comments regarding the invalid block set

Update BlockManager's comments regarding the invalid block set -- Key: HDFS-2729 URL: https://issues.apache.org/jira/browse/HDFS-2729 Project: Hadoop HDFS Issue Type: Improvement

[jira] [Resolved] (HDFS-93) NameNode should not serve up a bad edits log

[ https://issues.apache.org/jira/browse/HDFS-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-93. - Resolution: Cannot Reproduce This isn't a problem in the current version anymore. Errors in the dfs.namenode.name.d

[jira] [Resolved] (HDFS-44) Unit test failed: TestInjectionForSimulatedStorage

[ https://issues.apache.org/jira/browse/HDFS-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-44. - Resolution: Cannot Reproduce Hasn't had a failure report in two years now. Gone stale, closing out this and related

[jira] [Resolved] (HDFS-2728) Remove dfsadmin -printTopology from branch-1 docs since it does not exist

[ https://issues.apache.org/jira/browse/HDFS-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-2728. --- Resolution: Fixed Fix Version/s: 1.1.0 Committed revision 1225589. Thanks Eli! > Remov

[jira] [Resolved] (HDFS-19) Unhandled exceptions in DFSClient

[ https://issues.apache.org/jira/browse/HDFS-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-19. - Resolution: Invalid This has gone stale. I do not find these methods in the current DFSOutputStream. Do open a new

[jira] [Resolved] (HDFS-103) handle return value of globStatus() to be uniform.

[ https://issues.apache.org/jira/browse/HDFS-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-103. -- Resolution: Not A Problem Looking at the current impl. of globStatus, we always return an empty FileStatus[] out

[jira] [Reopened] (HDFS-97) DFS should detect slow links(nodes) and avoid them

[ https://issues.apache.org/jira/browse/HDFS-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J reopened HDFS-97: - Oh well, didn't notice the 'read' issue too. We cover writes with that, not reads. Reopening. > DFS sh

[jira] [Resolved] (HDFS-61) Datanode shutdown is called multiple times

[ https://issues.apache.org/jira/browse/HDFS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-61. - Resolution: Cannot Reproduce On trunk, looks like we only call it once now. This has gone stale, closing out.

[jira] [Resolved] (HDFS-57) A Datanode's datadir could have lots of blocks in the top-level directory

[ https://issues.apache.org/jira/browse/HDFS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-57. - Resolution: Not A Problem Not a problem in the current {{FSDataset}} operations (neither on branch-1).

[jira] [Created] (HDFS-2728) Remove dfsadmin -printTopology from branch-1 docs since it does not exist

Remove dfsadmin -printTopology from branch-1 docs since it does not exist - Key: HDFS-2728 URL: https://issues.apache.org/jira/browse/HDFS-2728 Project: Hadoop HDFS Issu

[jira] [Resolved] (HDFS-67) /tmp/hadoop-${user}/dfs/tmp/tmp/client-${long}.tmp is not cleanup correctly

[ https://issues.apache.org/jira/browse/HDFS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-67. - Resolution: Not A Problem Not a problem after Dhruba's HDFS-1707. > /tmp/hadoop-${user}/dfs/tmp/tmp

[jira] [Resolved] (HDFS-5) Check that network topology is updated when new data-nodes are joining the cluster

[ https://issues.apache.org/jira/browse/HDFS-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-5. Resolution: Cannot Reproduce The mapping is done pretty much properly as far as I've noticed. With caching enabled tho

[jira] [Resolved] (HDFS-2714) HA: Fix test cases which use standalone FSNamesystems

[ https://issues.apache.org/jira/browse/HDFS-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved HDFS-2714. --- Resolution: Fixed Fix Version/s: HA branch (HDFS-1623) Hadoop Flags: Reviewed > HA: Fi

[jira] [Created] (HDFS-2730) HA: Refactor shared HA-related test code into HATestUtils class

HA: Refactor shared HA-related test code into HATestUtils class --- Key: HDFS-2730 URL: https://issues.apache.org/jira/browse/HDFS-2730 Project: Hadoop HDFS Issue Type: Sub-task

[jira] [Resolved] (HDFS-2692) HA: Bugs related to failover from/into safe-mode

[ https://issues.apache.org/jira/browse/HDFS-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved HDFS-2692. --- Resolution: Fixed Fix Version/s: HA branch (HDFS-1623) Hadoop Flags: Reviewed Committed to

[jira] [Created] (HDFS-2731) Autopopulate standby name dirs if they're empty

Autopopulate standby name dirs if they're empty --- Key: HDFS-2731 URL: https://issues.apache.org/jira/browse/HDFS-2731 Project: Hadoop HDFS Issue Type: Sub-task Components: ha Affect

[jira] [Created] (HDFS-2732) Add support for the standby in the bin scripts

Add support for the standby in the bin scripts -- Key: HDFS-2732 URL: https://issues.apache.org/jira/browse/HDFS-2732 Project: Hadoop HDFS Issue Type: Sub-task Components: ha Affects

[jira] [Created] (HDFS-2733) Document HA configuration and CLI

Document HA configuration and CLI - Key: HDFS-2733 URL: https://issues.apache.org/jira/browse/HDFS-2733 Project: Hadoop HDFS Issue Type: Sub-task Components: documentation, ha Affects Versions: H

[jira] [Resolved] (HDFS-2732) Add support for the standby in the bin scripts

[ https://issues.apache.org/jira/browse/HDFS-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins resolved HDFS-2732. --- Resolution: Won't Fix > Add support for the standby in the bin scripts > -

[jira] [Created] (HDFS-2734) Even if we configure the property fs.checkpoint.size in both core-site.xml and hdfs-site.xml the values are not been considered

Even if we configure the property fs.checkpoint.size in both core-site.xml and hdfs-site.xml the values are not been considered Key: HDFS-2734