[jira] [Created] (HDFS-4474) Command : "hadoop fs -ls / " suggesting local directories/files instead hdfs directories/files

[Pradeep Bhadani (JIRA)]

Pradeep Bhadani created HDFS-4474:
-

 Summary: Command : "hadoop fs -ls / " suggesting local 
directories/files instead hdfs directories/files
 Key: HDFS-4474
 URL: https://issues.apache.org/jira/browse/HDFS-4474
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: build
Affects Versions: 2.0.0-alpha
 Environment: Ubuntu 12.04 64bit
Reporter: Pradeep Bhadani
Priority: Minor


hadoop fs -ls / , suggesting local directories (when we press TAB key).
In earlier version, pressing TAB was not suggesting anything but in 
hadoop-2.0.0 (CDH4) is suggesting local filesystem directories.
 


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[Apache Jenkins Server]

See 

[jira] [Resolved] (HDFS-4474) Command : "hadoop fs -ls / " suggesting local directories/files instead hdfs directories/files

[Daryn Sharp (JIRA)]

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

Daryn Sharp resolved HDFS-4474.
---

Resolution: Invalid

> Command : "hadoop fs -ls / " suggesting local directories/files instead hdfs 
> directories/files
> --
>
> Key: HDFS-4474
> URL: https://issues.apache.org/jira/browse/HDFS-4474
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: build
>Affects Versions: 2.0.0-alpha
> Environment: Ubuntu 12.04 64bit
>Reporter: Pradeep Bhadani
>Priority: Minor
>
> hadoop fs -ls / , suggesting local directories (when we press TAB key).
> In earlier version, pressing TAB was not suggesting anything but in 
> hadoop-2.0.0 (CDH4) is suggesting local filesystem directories.
>  
> hadoop@hadoop-VirtualBox:~/CDH4/hadoop-2.0.0-mr1-cdh4.1.3$ hadoop fs -ls /   
> {Pressing TAB}
> bin/dev/initrd.img  lost+found/ opt/run/srv/  
>   usr/
> boot/   etc/lib/media/  proc/   sbin/   sys/  
>   var/
> cdrom/  home/   lib64/  mnt/root/   selinux/tmp/  
>   vmlinuz

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HDFS-4475) OutOfMemory by BPService.offerService() takes down DataNode

[Plamen Jeliazkov (JIRA)]

Plamen Jeliazkov created HDFS-4475:
--

 Summary: OutOfMemory by BPService.offerService() takes down 
DataNode
 Key: HDFS-4475
 URL: https://issues.apache.org/jira/browse/HDFS-4475
 Project: Hadoop HDFS
  Issue Type: Bug
Affects Versions: 3.0.0, 2.0.3-alpha
Reporter: Plamen Jeliazkov
Assignee: Plamen Jeliazkov
 Fix For: 3.0.0, 2.0.3-alpha


In DataNode, there are catchs around BPService.offerService() call but no catch 
for OutOfMemory as there is for the DataXeiver as introduced in 0.22.0.

The issue can be replicated like this:
1) Create a cluster of X DataNodes and 1 NameNode and low memory settings 
(-Xmx128M or something similar).
2) Flood HDFS with of file creation.
3) DataNodes will hit OoM, stop blockpool service, and shutdown.

The resolution is to catch the OoMException and handle it properly when calling 
BlockPool.offerService() in DataNode.java; like as done in 0.22.0 of Hadoop. 
DataNodes should not shutdown or crash but remain in a sort of frozen state 
until memory issues are resolved by GC.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HDFS-4473) don't create domain socket unless we need it

[Aaron T. Myers (JIRA)]

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

Aaron T. Myers resolved HDFS-4473.
--

  Resolution: Fixed
Hadoop Flags: Reviewed

I've just committed this to the HDFS-347 branch.

Thanks a lot for the contribution, Andy.

> don't create domain socket unless we need it
> 
>
> Key: HDFS-4473
> URL: https://issues.apache.org/jira/browse/HDFS-4473
> Project: Hadoop HDFS
>  Issue Type: Sub-task
>  Components: datanode, hdfs-client, performance
>Reporter: Colin Patrick McCabe
>Assignee: Colin Patrick McCabe
>Priority: Minor
> Attachments: HDFS-4473.001.patch
>
>
> If {{dfs.domain.socket.path}} is set, but we don't have anything enabled 
> which would need it (like {{dfs.client.read.shortcircuit}}), don't create the 
> socket.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HDFS-4476) HDFS-347: style cleanups

[Colin Patrick McCabe (JIRA)]

Colin Patrick McCabe created HDFS-4476:
--

 Summary: HDFS-347: style cleanups
 Key: HDFS-4476
 URL: https://issues.apache.org/jira/browse/HDFS-4476
 Project: Hadoop HDFS
  Issue Type: Sub-task
Reporter: Colin Patrick McCabe
Assignee: Colin Patrick McCabe
Priority: Minor


Clean up some code style issues in HDFS-347.

DomainSocket.java
  do not use AtomicInteger for status, add a new class
  rename fdRef(), fdUnref(boolean), jfds, jbuf, SND_BUF_SIZE, etc.
  do not override finalize().
  remove some dead code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Freezing 2.0.3-alpha

[Arun C Murthy]

I just created branch-2.0.3-alpha. 

Committers: please *do not* check-in anything else with a fix-version of 
2.0.3-alpha on jira.

thanks,
Arun

[VOTE] Release hadoop-2.0.3-alpha

[Arun C Murthy]

Folks,

I've created a release candidate (rc0) for hadoop-2.0.3-alpha that I would like 
to release.

This release contains several major enhancements such as QJM for HDFS HA, 
multi-resource scheduling for YARN, YARN ResourceManager restart etc.  
Also YARN has achieved significant stability at scale (more details from Y! 
folks here: http://s.apache.org/VYO).

The RC is available at: 
http://people.apache.org/~acmurthy/hadoop-2.0.3-alpha-rc0/
The RC tag in svn is here: 
http://svn.apache.org/viewvc/hadoop/common/tags/release-2.0.3-alpha-rc0/

The maven artifacts are available via repository.apache.org.

Please try the release and vote; the vote will run for the usual 7 days.

thanks,
Arun



--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/