[jira] [Commented] (HADOOP-17905) Modify Text.ensureCapacity() to efficiently max out the backing array size

[ https://issues.apache.org/jira/browse/HADOOP-17905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17413527#comment-17413527 ] Peter Bacsko commented on HADOOP-17905: --- [~elgoiri] PR is available for review. cc [~snemeth].

[jira] [Updated] (HADOOP-17905) Modify Text.ensureCapacity() to efficiently max out the backing array size

[ https://issues.apache.org/jira/browse/HADOOP-17905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Bacsko updated HADOOP-17905: -- Description: This is a continuation of HADOOP-17901. Right now we use a factor of 1.5x to

[jira] [Created] (HADOOP-17905) Modify Text.ensureCapacity() to efficiently max out the backing array size

Peter Bacsko created HADOOP-17905: - Summary: Modify Text.ensureCapacity() to efficiently max out the backing array size Key: HADOOP-17905 URL: https://issues.apache.org/jira/browse/HADOOP-17905

[jira] [Commented] (HADOOP-17901) Performance degradation in Text.append() after HADOOP-16951

[ https://issues.apache.org/jira/browse/HADOOP-17901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17412483#comment-17412483 ] Peter Bacsko commented on HADOOP-17901: --- Thanks [~elgoiri]. I was also thinking about the

[jira] [Commented] (HADOOP-17901) Performance degradation in Text.append() after HADOOP-16951

[ https://issues.apache.org/jira/browse/HADOOP-17901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17411883#comment-17411883 ] Peter Bacsko commented on HADOOP-17901: --- cc [~belugabehr] [~elgoiri] you guys worked on the

[jira] [Updated] (HADOOP-17901) Performance degradation in Text.append() after HADOOP-16951

[ https://issues.apache.org/jira/browse/HADOOP-17901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Bacsko updated HADOOP-17901: -- Status: Patch Available (was: Open) > Performance degradation in Text.append() after

[jira] [Updated] (HADOOP-17901) Performance degradation in Text.append() after HADOOP-16951

[ https://issues.apache.org/jira/browse/HADOOP-17901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Bacsko updated HADOOP-17901: -- Attachment: HADOOP-17901-001.patch > Performance degradation in Text.append() after

[jira] [Created] (HADOOP-17901) Performance degradation in Text.append() after HADOOP-16951

Peter Bacsko created HADOOP-17901: - Summary: Performance degradation in Text.append() after HADOOP-16951 Key: HADOOP-17901 URL: https://issues.apache.org/jira/browse/HADOOP-17901 Project: Hadoop

[jira] [Commented] (HADOOP-17573) Fix compilation error of OBSFileSystem in trunk

[ https://issues.apache.org/jira/browse/HADOOP-17573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17298800#comment-17298800 ] Peter Bacsko commented on HADOOP-17573: --- I've just seen this problem. The PR fixed the build

[jira] [Commented] (HADOOP-17324) Don't relocate org.bouncycastle in shaded client jars

[ https://issues.apache.org/jira/browse/HADOOP-17324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17230071#comment-17230071 ] Peter Bacsko commented on HADOOP-17324: --- [~csun] I think the commit

[jira] [Commented] (HADOOP-16683) Disable retry of FailoverOnNetworkExceptionRetry in case of wrapped AccessControlException

[ https://issues.apache.org/jira/browse/HADOOP-16683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16975157#comment-16975157 ] Peter Bacsko commented on HADOOP-16683: --- [~adam.antal] we don't have build results for

[jira] [Commented] (HADOOP-16683) Disable retry of FailoverOnNetworkExceptionRetry in case of wrapped AccessControlException

[ https://issues.apache.org/jira/browse/HADOOP-16683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16968412#comment-16968412 ] Peter Bacsko commented on HADOOP-16683: --- +1 (non-binding) > Disable retry of

[jira] [Commented] (HADOOP-16683) Disable retry of FailoverOnNetworkExceptionRetry in case of wrapped AccessControlException

[ https://issues.apache.org/jira/browse/HADOOP-16683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16968247#comment-16968247 ] Peter Bacsko commented on HADOOP-16683: --- Just a question: do we know for sure that

[jira] [Commented] (HADOOP-16683) Disable retry of FailoverOnNetworkExceptionRetry in case of wrapped AccessControlException

[ https://issues.apache.org/jira/browse/HADOOP-16683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16967666#comment-16967666 ] Peter Bacsko commented on HADOOP-16683: --- [~adam.antal] I think the return value of this function

[jira] [Commented] (HADOOP-16580) Disable retry of FailoverOnNetworkExceptionRetry in case of AccessControlException

[ https://issues.apache.org/jira/browse/HADOOP-16580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16935841#comment-16935841 ] Peter Bacsko commented on HADOOP-16580: --- +1 (non-binding) > Disable retry of

[jira] [Commented] (HADOOP-16211) Update guava to 27.0-jre in hadoop-project branch-3.2

[ https://issues.apache.org/jira/browse/HADOOP-16211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863090#comment-16863090 ] Peter Bacsko commented on HADOOP-16211: --- On my machine,

[jira] [Commented] (HADOOP-16213) Update guava to 27.0-jre in hadoop-project branch-3.1

[ https://issues.apache.org/jira/browse/HADOOP-16213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863060#comment-16863060 ] Peter Bacsko commented on HADOOP-16213: --- Created YARN-9621 to track 

[jira] [Commented] (HADOOP-16211) Update guava to 27.0-jre in hadoop-project branch-3.2

[ https://issues.apache.org/jira/browse/HADOOP-16211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863035#comment-16863035 ] Peter Bacsko commented on HADOOP-16211: --- https://issues.apache.org/jira/browse/YARN-8672

[jira] [Updated] (HADOOP-16238) Add the possbility to set SO_REUSEADDR in IPC Server Listener

[ https://issues.apache.org/jira/browse/HADOOP-16238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Bacsko updated HADOOP-16238: -- Attachment: HADOOP-16238-005.patch > Add the possbility to set SO_REUSEADDR in IPC Server

[jira] [Commented] (HADOOP-16238) Add the possbility to set SO_REUSEADDR in IPC Server Listener

[ https://issues.apache.org/jira/browse/HADOOP-16238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16833641#comment-16833641 ] Peter Bacsko commented on HADOOP-16238: --- I uploaded patch v5 where the default is "true". > Add

[jira] [Commented] (HADOOP-16238) Add the possbility to set SO_REUSEADDR in IPC Server Listener

[ https://issues.apache.org/jira/browse/HADOOP-16238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16820794#comment-16820794 ] Peter Bacsko commented on HADOOP-16238: --- [~jojochuang] could you review this patch please? > Add

[jira] [Commented] (HADOOP-16238) Add the possbility to set SO_REUSEADDR in IPC Server Listener

[ https://issues.apache.org/jira/browse/HADOOP-16238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16817970#comment-16817970 ] Peter Bacsko commented on HADOOP-16238: --- [~adam.antal] based on a quick analysis, this socket

[jira] [Commented] (HADOOP-16238) Add the possbility to set SO_REUSEADDR in IPC Server Listener

[ https://issues.apache.org/jira/browse/HADOOP-16238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814468#comment-16814468 ] Peter Bacsko commented on HADOOP-16238: --- Thanks [~wilfreds], handled the newline stuff. > Add

[jira] [Updated] (HADOOP-16238) Add the possbility to set SO_REUSEADDR in IPC Server Listener

[ https://issues.apache.org/jira/browse/HADOOP-16238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Bacsko updated HADOOP-16238: -- Attachment: HADOOP-16238-004.patch > Add the possbility to set SO_REUSEADDR in IPC Server

[jira] [Commented] (HADOOP-16237) Fix new findbugs issues after update guava to 27.0-jre in hadoop-project trunk

[ https://issues.apache.org/jira/browse/HADOOP-16237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16810775#comment-16810775 ] Peter Bacsko commented on HADOOP-16237: --- *CosmosDBDocumentStoreReader /* 

[jira] [Commented] (HADOOP-16238) Add the possbility to set SO_REUSEADDR in IPC Server Listener

[ https://issues.apache.org/jira/browse/HADOOP-16238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16810746#comment-16810746 ] Peter Bacsko commented on HADOOP-16238: --- [~wilfreds] / [~ste...@apache.org] could you review this

[jira] [Updated] (HADOOP-16238) Add the possbility to set SO_REUSEADDR in IPC Server Listener

[ https://issues.apache.org/jira/browse/HADOOP-16238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Bacsko updated HADOOP-16238: -- Attachment: HADOOP-16238-003.patch > Add the possbility to set SO_REUSEADDR in IPC Server

[jira] [Updated] (HADOOP-16238) Add the possbility to set SO_REUSEADDR in IPC Server Listener

[ https://issues.apache.org/jira/browse/HADOOP-16238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Bacsko updated HADOOP-16238: -- Attachment: HADOOP-16238-002.patch > Add the possbility to set SO_REUSEADDR in IPC Server

[jira] [Updated] (HADOOP-16238) Add the possbility to set SO_REUSEADDR in IPC Server Listener

[ https://issues.apache.org/jira/browse/HADOOP-16238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Bacsko updated HADOOP-16238: -- Status: Patch Available (was: Open) > Add the possbility to set SO_REUSEADDR in IPC Server

[jira] [Updated] (HADOOP-16238) Add the possbility to set SO_REUSEADDR in IPC Server Listener

[ https://issues.apache.org/jira/browse/HADOOP-16238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Bacsko updated HADOOP-16238: -- Attachment: HADOOP-16238-001.patch > Add the possbility to set SO_REUSEADDR in IPC Server

[jira] [Created] (HADOOP-16238) Add the possbility to set SO_REUSEADDR in IPC Server Listener

Peter Bacsko created HADOOP-16238: - Summary: Add the possbility to set SO_REUSEADDR in IPC Server Listener Key: HADOOP-16238 URL: https://issues.apache.org/jira/browse/HADOOP-16238 Project: Hadoop

[jira] [Commented] (HADOOP-15822) zstd compressor can fail with a small output buffer

[ https://issues.apache.org/jira/browse/HADOOP-15822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16643416#comment-16643416 ] Peter Bacsko commented on HADOOP-15822: --- [~jlowe] you were right, it's not related to zstandard.

[jira] [Commented] (HADOOP-15822) zstd compressor can fail with a small output buffer

[ https://issues.apache.org/jira/browse/HADOOP-15822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642106#comment-16642106 ] Peter Bacsko commented on HADOOP-15822: --- No, I still haven't had the time to check out with other

[jira] [Comment Edited] (HADOOP-15822) zstd compressor can fail with a small output buffer

[ https://issues.apache.org/jira/browse/HADOOP-15822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642000#comment-16642000 ] Peter Bacsko edited comment on HADOOP-15822 at 10/8/18 3:28 PM: I

[jira] [Commented] (HADOOP-15822) zstd compressor can fail with a small output buffer

[ https://issues.apache.org/jira/browse/HADOOP-15822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642000#comment-16642000 ] Peter Bacsko commented on HADOOP-15822: --- I reproduced the problem. This is what happens if the

[jira] [Comment Edited] (HADOOP-15822) zstd compressor can fail with a small output buffer

[ https://issues.apache.org/jira/browse/HADOOP-15822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16640338#comment-16640338 ] Peter Bacsko edited comment on HADOOP-15822 at 10/5/18 8:58 PM:

[jira] [Commented] (HADOOP-15822) zstd compressor can fail with a small output buffer

[ https://issues.apache.org/jira/browse/HADOOP-15822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16640338#comment-16640338 ] Peter Bacsko commented on HADOOP-15822: --- [~jlowe] what strange coincidence. I was also testing

[jira] [Updated] (HADOOP-14982) Clients using FailoverOnNetworkExceptionRetry can go into a loop if they're used without authenticating with kerberos in HA env

[ https://issues.apache.org/jira/browse/HADOOP-14982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Bacsko updated HADOOP-14982: -- Attachment: HADOOP-14982-003.patch > Clients using FailoverOnNetworkExceptionRetry can go

[jira] [Updated] (HADOOP-14982) Clients using FailoverOnNetworkExceptionRetry can go into a loop if they're used without authenticating with kerberos in HA env

[ https://issues.apache.org/jira/browse/HADOOP-14982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Bacsko updated HADOOP-14982: -- Attachment: HADOOP-14892-002.patch > Clients using FailoverOnNetworkExceptionRetry can go

[jira] [Commented] (HADOOP-14982) Clients using FailoverOnNetworkExceptionRetry can go into a loop if they're used without authenticating with kerberos in HA env

[ https://issues.apache.org/jira/browse/HADOOP-14982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1657#comment-1657 ] Peter Bacsko commented on HADOOP-14982: --- [~daryn] how do you get 1011 lines of output? I set the

[jira] [Commented] (HADOOP-14982) Clients using FailoverOnNetworkExceptionRetry can go into a loop if they're used without authenticating with kerberos in HA env

[ https://issues.apache.org/jira/browse/HADOOP-14982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16220762#comment-16220762 ] Peter Bacsko commented on HADOOP-14982: --- Thanks [~daryn], will modify the patch accordingly. >

[jira] [Updated] (HADOOP-14982) Clients using FailoverOnNetworkExceptionRetry can go into a loop if they're used without authenticating with kerberos in HA env

[ https://issues.apache.org/jira/browse/HADOOP-14982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Bacsko updated HADOOP-14982: -- Status: Patch Available (was: Open) > Clients using FailoverOnNetworkExceptionRetry can go

[jira] [Updated] (HADOOP-14982) Clients using FailoverOnNetworkExceptionRetry can go into a loop if they're used without authenticating with kerberos in HA env

[ https://issues.apache.org/jira/browse/HADOOP-14982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Bacsko updated HADOOP-14982: -- Attachment: HADOOP-14892-001.patch > Clients using FailoverOnNetworkExceptionRetry can go

[jira] [Created] (HADOOP-14982) Clients using FailoverOnNetworkExceptionRetry can go into a loop if they're used without authenticating with kerberos in HA env

Peter Bacsko created HADOOP-14982: - Summary: Clients using FailoverOnNetworkExceptionRetry can go into a loop if they're used without authenticating with kerberos in HA env Key: HADOOP-14982 URL: