[jira] Reopened: (HADOOP-6662) hadoop zlib compression does not fully utilize the buffer

[ https://issues.apache.org/jira/browse/HADOOP-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Kang reopened HADOOP-6662: --- Thanks for Hong Tang. Patch is not attached in HADOOP-4196 and the issue is still unresolved in release

[jira] Updated: (HADOOP-6662) hadoop zlib compression does not fully utilize the buffer

[ https://issues.apache.org/jira/browse/HADOOP-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Kang updated HADOOP-6662: -- Attachment: ZlibCompressor.patch Patch attached. needsInput() check the uncompressedDirectBuf, if it

[jira] Commented: (HADOOP-6662) hadoop zlib compression does not fully utilize the buffer

[ https://issues.apache.org/jira/browse/HADOOP-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851277#action_12851277 ] Xiao Kang commented on HADOOP-6662: --- Thank you for your notice! However no patch attache

[jira] Commented: (HADOOP-6640) FileSystem.get() does RPC retries within a static synchronized block

[ https://issues.apache.org/jira/browse/HADOOP-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851120#action_12851120 ] Tsz Wo (Nicholas), SZE commented on HADOOP-6640: I have no problem if you

[jira] Commented: (HADOOP-6640) FileSystem.get() does RPC retries within a static synchronized block

[ https://issues.apache.org/jira/browse/HADOOP-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851116#action_12851116 ] Hairong Kuang commented on HADOOP-6640: --- This solution will add cost to each rpc cal

[jira] Commented: (HADOOP-6640) FileSystem.get() does RPC retries within a static synchronized block

[ https://issues.apache.org/jira/browse/HADOOP-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851101#action_12851101 ] Tsz Wo (Nicholas), SZE commented on HADOOP-6640: Yes, it needs to check a

[jira] Commented: (HADOOP-6640) FileSystem.get() does RPC retries within a static synchronized block

[ https://issues.apache.org/jira/browse/HADOOP-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851085#action_12851085 ] Hairong Kuang commented on HADOOP-6640: --- Then this means every future RPC call of DF

[jira] Commented: (HADOOP-6640) FileSystem.get() does RPC retries within a static synchronized block

[ https://issues.apache.org/jira/browse/HADOOP-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851083#action_12851083 ] Tsz Wo (Nicholas), SZE commented on HADOOP-6640: > The RPC is issued by th

[jira] Commented: (HADOOP-6640) FileSystem.get() does RPC retries within a static synchronized block

[ https://issues.apache.org/jira/browse/HADOOP-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851077#action_12851077 ] Hairong Kuang commented on HADOOP-6640: --- > Change DistributedFileSystem so that it d

[jira] Commented: (HADOOP-6664) fs.inmemory.size.mb not listed in conf. Cluster setup page gives wrong advice.

[ https://issues.apache.org/jira/browse/HADOOP-6664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851053#action_12851053 ] Edward Capriolo commented on HADOOP-6664: - It is confusing to me. Usually I deter

[jira] Updated: (HADOOP-6569) FsShell#cat should avoid calling unecessary getFileStatus before opening a file to read

[ https://issues.apache.org/jira/browse/HADOOP-6569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hairong Kuang updated HADOOP-6569: -- Resolution: Fixed Status: Resolved (was: Patch Available) I've committed this for a w

[jira] Commented: (HADOOP-6664) fs.inmemory.size.mb not listed in conf. Cluster setup page gives wrong advice.

[ https://issues.apache.org/jira/browse/HADOOP-6664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851031#action_12851031 ] Chris Douglas commented on HADOOP-6664: --- Oh, I see what you mean. {{io.sort.factor}}

[jira] Resolved: (HADOOP-6664) fs.inmemory.size.mb not listed in conf. Cluster setup page gives wrong advice.

[ https://issues.apache.org/jira/browse/HADOOP-6664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved HADOOP-6664. --- Resolution: Invalid > fs.inmemory.size.mb not listed in conf. Cluster setup page gives wrong

[jira] Resolved: (HADOOP-6662) hadoop zlib compression does not fully utilize the buffer

[ https://issues.apache.org/jira/browse/HADOOP-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hong Tang resolved HADOOP-6662. --- Resolution: Duplicate > hadoop zlib compression does not fully utilize the buffer >

[jira] Commented: (HADOOP-6662) hadoop zlib compression does not fully utilize the buffer

[ https://issues.apache.org/jira/browse/HADOOP-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851016#action_12851016 ] Hong Tang commented on HADOOP-6662: --- This is duplicate for HADOOP-4196. > hadoop zlib c

[jira] Commented: (HADOOP-6664) fs.inmemory.size.mb not listed in conf. Cluster setup page gives wrong advice.

[ https://issues.apache.org/jira/browse/HADOOP-6664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851001#action_12851001 ] Chris Douglas commented on HADOOP-6664: --- bq. fs.inmemory.size.mb does not appear in

[jira] Created: (HADOOP-6664) fs.inmemory.size.mb not listed in conf. Cluster setup page gives wrong advice.

fs.inmemory.size.mb not listed in conf. Cluster setup page gives wrong advice. -- Key: HADOOP-6664 URL: https://issues.apache.org/jira/browse/HADOOP-6664 Project: Hadoop Commo

[jira] Updated: (HADOOP-6663) BlockDecompressorStream get EOF exception when decompressing the file compressed from empty file

[ https://issues.apache.org/jira/browse/HADOOP-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Kang updated HADOOP-6663: -- Attachment: BlockDecompressorStream.patch Patch attached. Return -1 to indicate EOF when reading a 0

[jira] Commented: (HADOOP-6663) BlockDecompressorStream get EOF exception when decompressing the file compressed from empty file

[ https://issues.apache.org/jira/browse/HADOOP-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850835#action_12850835 ] Xiao Kang commented on HADOOP-6663: --- The EOF exception caused as follow: BlockCompresso

[jira] Created: (HADOOP-6663) BlockDecompressorStream get EOF exception when decompressing the file compressed from empty file

BlockDecompressorStream get EOF exception when decompressing the file compressed from empty file Key: HADOOP-6663 URL: https://issues.apache.org/jira/browse/HADOOP-66

[jira] Created: (HADOOP-6662) hadoop zlib compression does not fully utilize the buffer

hadoop zlib compression does not fully utilize the buffer - Key: HADOOP-6662 URL: https://issues.apache.org/jira/browse/HADOOP-6662 Project: Hadoop Common Issue Type: Improvement