[jira] [Commented] (HBASE-21628) memory leak risk when ClientAsyncPrefetchScanner not close

2019-01-14 Thread cong.han (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742796#comment-16742796 ] cong.han commented on HBASE-21628: -- [~stack]  add prefetch condition to scan is unnecessary, I will

[jira] [Commented] (HBASE-21628) memory leak risk when ClientAsyncPrefetchScanner not close

2019-01-14 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742807#comment-16742807 ] Hadoop QA commented on HBASE-21628: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (HBASE-21628) memory leak risk when ClientAsyncPrefetchScanner not close

2019-01-10 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739652#comment-16739652 ] stack commented on HBASE-21628: --- Took a quick look. A lot of new moving parts. Do we have to add prefetch

[jira] [Commented] (HBASE-21628) memory leak risk when ClientAsyncPrefetchScanner not close

2019-01-10 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739450#comment-16739450 ] Hadoop QA commented on HBASE-21628: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (HBASE-21628) memory leak risk when ClientAsyncPrefetchScanner not close

2019-01-09 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738333#comment-16738333 ] Hadoop QA commented on HBASE-21628: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (HBASE-21628) memory leak risk when ClientAsyncPrefetchScanner not close

2019-01-03 Thread cong.han (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733136#comment-16733136 ] cong.han commented on HBASE-21628: -- Change type to BUG,It's more like a potential bug. > memory leak

[jira] [Commented] (HBASE-21628) memory leak risk when ClientAsyncPrefetchScanner not close

2019-01-01 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16731624#comment-16731624 ] Hadoop QA commented on HBASE-21628: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (HBASE-21628) memory leak risk when ClientAsyncPrefetchScanner not close

2019-01-01 Thread cong.han (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16731566#comment-16731566 ] cong.han commented on HBASE-21628: -- Was the failed hbase-server tests caused by this patch? > memory

[jira] [Commented] (HBASE-21628) memory leak risk when ClientAsyncPrefetchScanner not close

2019-01-01 Thread cong.han (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16731562#comment-16731562 ] cong.han commented on HBASE-21628: -- reattach > memory leak risk when ClientAsyncPrefetchScanner not

[jira] [Commented] (HBASE-21628) memory leak risk when ClientAsyncPrefetchScanner not close

2019-01-01 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16731541#comment-16731541 ] Hadoop QA commented on HBASE-21628: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (HBASE-21628) memory leak risk when ClientAsyncPrefetchScanner not close

2019-01-01 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16731540#comment-16731540 ] Hadoop QA commented on HBASE-21628: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (HBASE-21628) memory leak risk when ClientAsyncPrefetchScanner not close

2018-12-31 Thread cong.han (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16731522#comment-16731522 ] cong.han commented on HBASE-21628: -- Fix the style problem。 > memory leak risk when

[jira] [Commented] (HBASE-21628) memory leak risk when ClientAsyncPrefetchScanner not close

2018-12-30 Thread cong.han (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16731139#comment-16731139 ] cong.han commented on HBASE-21628: -- Sorry，I forgot to fix the style of the patch,I will work on it

[jira] [Commented] (HBASE-21628) memory leak risk when ClientAsyncPrefetchScanner not close

2018-12-24 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728297#comment-16728297 ] Hadoop QA commented on HBASE-21628: --- | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (HBASE-21628) memory leak risk when ClientAsyncPrefetchScanner not close

2018-12-23 Thread cong.han (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728180#comment-16728180 ] cong.han commented on HBASE-21628: -- [~stack] To the first question, the old version

[jira] [Commented] (HBASE-21628) memory leak risk when ClientAsyncPrefetchScanner not close

2018-12-22 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16727547#comment-16727547 ] stack commented on HBASE-21628: --- Looks good. Want to say in one line how you've changed the behavior

[jira] [Commented] (HBASE-21628) memory leak risk when ClientAsyncPrefetchScanner not close

2018-12-21 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16727278#comment-16727278 ] Hadoop QA commented on HBASE-21628: --- | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (HBASE-21628) memory leak risk when ClientAsyncPrefetchScanner not close

2018-12-21 Thread cong.han (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16727218#comment-16727218 ] cong.han commented on HBASE-21628: -- reattach, 1 fix check style and license problem 2 check prefetch

[jira] [Commented] (HBASE-21628) memory leak risk when ClientAsyncPrefetchScanner not close

2018-12-21 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726725#comment-16726725 ] Hadoop QA commented on HBASE-21628: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem