[jira] [Commented] (HDFS-12533) NNThroughputBenchmark threads get stuck on UGI.getCurrentUser()

2019-01-07 Thread Erik Krogen (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-12533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736522#comment-16736522 ] Erik Krogen commented on HDFS-12533: I looked into this a bit further, and attempted to fix it by

[jira] [Commented] (HDFS-12533) NNThroughputBenchmark threads get stuck on UGI.getCurrentUser()

2018-11-07 Thread Erik Krogen (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-12533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16678603#comment-16678603 ] Erik Krogen commented on HDFS-12533: Just an update on this, I tried running the same experiments I

[jira] [Commented] (HDFS-12533) NNThroughputBenchmark threads get stuck on UGI.getCurrentUser()

2017-10-03 Thread Konstantin Shvachko (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-12533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190626#comment-16190626 ] Konstantin Shvachko commented on HDFS-12533: We may still want to fix this for

[jira] [Commented] (HDFS-12533) NNThroughputBenchmark threads get stuck on UGI.getCurrentUser()

2017-09-26 Thread Erik Krogen (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-12533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16181275#comment-16181275 ] Erik Krogen commented on HDFS-12533: Hm yes, HADOOP-9747 should definitely help the issue >

[jira] [Commented] (HDFS-12533) NNThroughputBenchmark threads get stuck on UGI.getCurrentUser()

2017-09-24 Thread Xiao Chen (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-12533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178502#comment-16178502 ] Xiao Chen commented on HDFS-12533: -- I think HADOOP-9747 would get this solved. (I have always wanted to