[jira] [Commented] (HDFS-13904) ContentSummary does not always respect processing limit, resulting in long lock acquisitions

2021-04-26 Thread Qi Zhu (Jira)
[ https://issues.apache.org/jira/browse/HDFS-13904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17331878#comment-17331878 ] Qi Zhu commented on HDFS-13904: --- Is this going on? I met the problem also.-- Thanks. > ContentSummary

[jira] [Commented] (HDFS-13904) ContentSummary does not always respect processing limit, resulting in long lock acquisitions

2020-09-16 Thread Srinivasu Majeti (Jira)
[ https://issues.apache.org/jira/browse/HDFS-13904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17196876#comment-17196876 ] Srinivasu Majeti commented on HDFS-13904: - Hi [~xyao], Atleast if there is slowness due to

[jira] [Commented] (HDFS-13904) ContentSummary does not always respect processing limit, resulting in long lock acquisitions

2020-05-07 Thread Xiaoyu Yao (Jira)
[ https://issues.apache.org/jira/browse/HDFS-13904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17101902#comment-17101902 ] Xiaoyu Yao commented on HDFS-13904: --- Before the recursive dir.getContentSummary, there is a recursive

[jira] [Commented] (HDFS-13904) ContentSummary does not always respect processing limit, resulting in long lock acquisitions

2020-05-06 Thread Erik Krogen (Jira)
[ https://issues.apache.org/jira/browse/HDFS-13904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17100870#comment-17100870 ] Erik Krogen commented on HDFS-13904: Looks like I must have confused {{getReadHoldCount()}} and

[jira] [Commented] (HDFS-13904) ContentSummary does not always respect processing limit, resulting in long lock acquisitions

2020-05-05 Thread Uma Maheswara Rao G (Jira)
[ https://issues.apache.org/jira/browse/HDFS-13904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17100366#comment-17100366 ] Uma Maheswara Rao G commented on HDFS-13904: Thanks [~xkrogen] for the reply. BTW, Just for

[jira] [Commented] (HDFS-13904) ContentSummary does not always respect processing limit, resulting in long lock acquisitions

2020-05-04 Thread Erik Krogen (Jira)
[ https://issues.apache.org/jira/browse/HDFS-13904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17099220#comment-17099220 ] Erik Krogen commented on HDFS-13904: Hi [~umamaheswararao], I'm not actively working on this. I don't

[jira] [Commented] (HDFS-13904) ContentSummary does not always respect processing limit, resulting in long lock acquisitions

2020-05-04 Thread Uma Maheswara Rao G (Jira)
[ https://issues.apache.org/jira/browse/HDFS-13904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17099204#comment-17099204 ] Uma Maheswara Rao G commented on HDFS-13904: Hi [~xkrogen], Any updates on this? Just a

[jira] [Commented] (HDFS-13904) ContentSummary does not always respect processing limit, resulting in long lock acquisitions

2018-09-07 Thread Erik Krogen (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-13904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16607707#comment-16607707 ] Erik Krogen commented on HDFS-13904: Thanks [~arpitagarwal] and [~kihwal] for taking a look! {quote}

[jira] [Commented] (HDFS-13904) ContentSummary does not always respect processing limit, resulting in long lock acquisitions

2018-09-07 Thread Kihwal Lee (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-13904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16607629#comment-16607629 ] Kihwal Lee commented on HDFS-13904: --- Your proposal sounds reasonable, although I wonder what is

[jira] [Commented] (HDFS-13904) ContentSummary does not always respect processing limit, resulting in long lock acquisitions

2018-09-07 Thread Arpit Agarwal (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-13904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16607627#comment-16607627 ] Arpit Agarwal commented on HDFS-13904: -- Nice find [~xkrogen]. Yes I think we can remove those