[jira] Created: (HADOOP-7088) JMX Bean that exposes version and build information

JMX Bean that exposes version and build information --- Key: HADOOP-7088 URL: https://issues.apache.org/jira/browse/HADOOP-7088 Project: Hadoop Common Issue Type: New Feature Report

[jira] Updated: (HADOOP-7088) JMX Bean that exposes version and build information

[ https://issues.apache.org/jira/browse/HADOOP-7088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-7088: -- Priority: Minor (was: Major) Affects Version/s: 0.23.0 > JMX Bean that exposes v

[jira] Created: (HADOOP-6983) Update balancer docs

Update balancer docs Key: HADOOP-6983 URL: https://issues.apache.org/jira/browse/HADOOP-6983 Project: Hadoop Common Issue Type: Improvement Reporter: Dmytro Molkov Assignee: Dmytro Molkov

[jira] Updated: (HADOOP-6983) Update balancer docs

[ https://issues.apache.org/jira/browse/HADOOP-6983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6983: -- Attachment: HADOOP-6983.patch > Update balancer docs > > >

[jira] Updated: (HADOOP-6764) Add number of reader threads and queue length as configuration parameters in RPC.getServer

[ https://issues.apache.org/jira/browse/HADOOP-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6764: -- Status: Patch Available (was: Open) Doing hudson again > Add number of reader threads and qu

[jira] Updated: (HADOOP-6764) Add number of reader threads and queue length as configuration parameters in RPC.getServer

[ https://issues.apache.org/jira/browse/HADOOP-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6764: -- Status: Open (was: Patch Available) > Add number of reader threads and queue length as config

[jira] Commented: (HADOOP-6764) Add number of reader threads and queue length as configuration parameters in RPC.getServer

[ https://issues.apache.org/jira/browse/HADOOP-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916658#action_12916658 ] Dmytro Molkov commented on HADOOP-6764: --- System tests failed because of the timeout

[jira] Updated: (HADOOP-6764) Add number of reader threads and queue length as configuration parameters in RPC.getServer

[ https://issues.apache.org/jira/browse/HADOOP-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6764: -- Attachment: HADOOP-6764.2.patch Changed the name of the parameter. And I am now using -1 as th

[jira] Updated: (HADOOP-6764) Add number of reader threads and queue length as configuration parameters in RPC.getServer

[ https://issues.apache.org/jira/browse/HADOOP-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6764: -- Attachment: HADOOP-6764.patch Please have a look at the patch. It is a rather simple one. Just

[jira] Commented: (HADOOP-6870) Add FileSystem#listLocatedStatus to list a directory's content together with each file's block locations

[ https://issues.apache.org/jira/browse/HADOOP-6870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893320#action_12893320 ] Dmytro Molkov commented on HADOOP-6870: --- I looked over the patch and overall looks g

[jira] Commented: (HADOOP-6796) FileStatus allows null srcPath but crashes if that's done

[ https://issues.apache.org/jira/browse/HADOOP-6796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874175#action_12874175 ] Dmytro Molkov commented on HADOOP-6796: --- Did you think of using an empty string inst

[jira] Updated: (HADOOP-6761) Improve Trash Emptier

[ https://issues.apache.org/jira/browse/HADOOP-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6761: -- Status: Patch Available (was: Open) This should fix the javac warning > Improve Trash Emptie

[jira] Updated: (HADOOP-6761) Improve Trash Emptier

[ https://issues.apache.org/jira/browse/HADOOP-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6761: -- Status: Open (was: Patch Available) > Improve Trash Emptier > - > >

[jira] Updated: (HADOOP-6761) Improve Trash Emptier

[ https://issues.apache.org/jira/browse/HADOOP-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6761: -- Attachment: HADOOP-6761.5.patch > Improve Trash Emptier > - > >

[jira] Updated: (HADOOP-6761) Improve Trash Emptier

[ https://issues.apache.org/jira/browse/HADOOP-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6761: -- Status: Patch Available (was: Open) > Improve Trash Emptier > - > >

[jira] Updated: (HADOOP-6761) Improve Trash Emptier

[ https://issues.apache.org/jira/browse/HADOOP-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6761: -- Attachment: HADOOP-6761.4.patch Addressing all the comments > Improve Trash Emptier > ---

[jira] Updated: (HADOOP-6761) Improve Trash Emptier

[ https://issues.apache.org/jira/browse/HADOOP-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6761: -- Status: Open (was: Patch Available) > Improve Trash Emptier > - > >

[jira] Updated: (HADOOP-6761) Improve Trash Emptier

[ https://issues.apache.org/jira/browse/HADOOP-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6761: -- Status: Patch Available (was: Open) Submitting to Hudson, can someone review the code please?

[jira] Updated: (HADOOP-6761) Improve Trash Emptier

[ https://issues.apache.org/jira/browse/HADOOP-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6761: -- Attachment: HADOOP-6761.3.patch To have backward compatible behaviour the default value of the

[jira] Created: (HADOOP-6764) Add number of reader threads and queue length as configuration parameters in RPC.getServer

Add number of reader threads and queue length as configuration parameters in RPC.getServer -- Key: HADOOP-6764 URL: https://issues.apache.org/jira/browse/HADOOP-6764

[jira] Resolved: (HADOOP-6469) Multiple RPC Servers using same object instance

[ https://issues.apache.org/jira/browse/HADOOP-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov resolved HADOOP-6469. --- Resolution: Not A Problem I will close this one since I already solved HDFS-599 by simply us

[jira] Updated: (HADOOP-6761) Improve Trash Emptier

[ https://issues.apache.org/jira/browse/HADOOP-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6761: -- Attachment: HADOOP-6761.2.patch This patch has a unittest and the modifications to core-defaul

[jira] Commented: (HADOOP-6761) Improve Trash Emptier

[ https://issues.apache.org/jira/browse/HADOOP-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866410#action_12866410 ] Dmytro Molkov commented on HADOOP-6761: --- Sure Ravi, what is it that you want me to m

[jira] Updated: (HADOOP-6761) Improve Trash Emptier

[ https://issues.apache.org/jira/browse/HADOOP-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6761: -- Attachment: HADOOP-6761.patch The fix itself is very simple. Please see patch attached. Have t

[jira] Created: (HADOOP-6761) Improve Trash Emptier

Improve Trash Emptier - Key: HADOOP-6761 URL: https://issues.apache.org/jira/browse/HADOOP-6761 Project: Hadoop Common Issue Type: Improvement Reporter: Dmytro Molkov There are two inefficiencies in the Tras

[jira] Commented: (HADOOP-6743) Create a Writable class that stores a possibly incomplete list of FileStatus objects

[ https://issues.apache.org/jira/browse/HADOOP-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864556#action_12864556 ] Dmytro Molkov commented on HADOOP-6743: --- The code looks good +1 > Create a Writable

[jira] Updated: (HADOOP-6713) The RPC server Listener thread is a scalability bottleneck

[ https://issues.apache.org/jira/browse/HADOOP-6713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6713: -- Status: Patch Available (was: Open) Resubmitting for Hudson > The RPC server Listener thread

[jira] Updated: (HADOOP-6713) The RPC server Listener thread is a scalability bottleneck

[ https://issues.apache.org/jira/browse/HADOOP-6713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6713: -- Status: Open (was: Patch Available) > The RPC server Listener thread is a scalability bottlen

[jira] Updated: (HADOOP-6713) The RPC server Listener thread is a scalability bottleneck

[ https://issues.apache.org/jira/browse/HADOOP-6713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6713: -- Attachment: HADOOP-6713.2.patch modifying the patch to address Hairong's comments: 1. Removed

[jira] Commented: (HADOOP-6713) The RPC server Listener thread is a scalability bottleneck

[ https://issues.apache.org/jira/browse/HADOOP-6713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859935#action_12859935 ] Dmytro Molkov commented on HADOOP-6713: --- We were running performance test on our tes

[jira] Updated: (HADOOP-6713) The RPC server Listener thread is a scalability bottleneck

[ https://issues.apache.org/jira/browse/HADOOP-6713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6713: -- Status: Patch Available (was: Open) Affects Version/s: 0.21.0

[jira] Updated: (HADOOP-6713) The RPC server Listener thread is a scalability bottleneck

[ https://issues.apache.org/jira/browse/HADOOP-6713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6713: -- Attachment: HADOOP-6713.patch Please have a look. We did the same change on hadoop-0.20 and ra

[jira] Updated: (HADOOP-6470) JMX Context for Metrics

[ https://issues.apache.org/jira/browse/HADOOP-6470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6470: -- Attachment: JMX.patch I created the first iteration of the context for JMX, any comments are w

[jira] Created: (HADOOP-6470) JMX Context for Metrics

JMX Context for Metrics --- Key: HADOOP-6470 URL: https://issues.apache.org/jira/browse/HADOOP-6470 Project: Hadoop Common Issue Type: New Feature Reporter: Dmytro Molkov The way metrics are currently expose

[jira] Created: (HADOOP-6469) Multiple RPC Servers using same object instance

Multiple RPC Servers using same object instance --- Key: HADOOP-6469 URL: https://issues.apache.org/jira/browse/HADOOP-6469 Project: Hadoop Common Issue Type: New Feature Reporter: Dmyt

[jira] Updated: (HADOOP-6216) HDFS Web UI displays comments from dfs.exclude file and counts them as dead nodes

[ https://issues.apache.org/jira/browse/HADOOP-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6216: -- Affects Version/s: 0.21.0 Status: Patch Available (was: Open) > HDFS Web UI di

[jira] Updated: (HADOOP-6216) HDFS Web UI displays comments from dfs.exclude file and counts them as dead nodes

[ https://issues.apache.org/jira/browse/HADOOP-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6216: -- Attachment: HADOOP-6216.patch There was something terribly wrong with the tabs formatting in m

[jira] Updated: (HADOOP-6216) HDFS Web UI displays comments from dfs.exclude file and counts them as dead nodes

[ https://issues.apache.org/jira/browse/HADOOP-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Molkov updated HADOOP-6216: -- Attachment: HADOOP-6216.patch I added the possibility of inline comments (hostname # reason fo

[jira] Commented: (HADOOP-6216) HDFS Web UI displays comments from dfs.exclude file and counts them as dead nodes

[ https://issues.apache.org/jira/browse/HADOOP-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750019#action_12750019 ] Dmytro Molkov commented on HADOOP-6216: --- What about adding inline comments handling?