[jira] [Commented] (HBASE-27491) AsyncProcess should not clear meta cache for RejectedExecutionException
[
https://issues.apache.org/jira/browse/HBASE-27491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17655180#comment-17655180
]
Hudson commented on HBASE-27491:
Results for branch branch-2.4
[build #486 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/486/]:
(/) *{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/486/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/486/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/486/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/486/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> AsyncProcess should not clear meta cache for RejectedExecutionException
> ---
>
> Key: HBASE-27491
> URL: https://issues.apache.org/jira/browse/HBASE-27491
> Project: HBase
> Issue Type: Improvement
>Reporter: Bryan Beaudreault
>Assignee: Briana Augenreich
>Priority: Major
> Fix For: 2.4.16, 2.5.3
>
>
> Batch requests using AsyncProcess get submitted to a thread pool. If the pool
> is too small or backing regionservers are overloaded, the pool may reject
> requests. Currently this causes a cache clear, which only exacerbates issues
> in most cases.
> If there's a real reason to clear cache, the individual failing tasks that
> actually get accepted into the pool should be enough to appropriately clear
> the cache. So let's special case REE in AsyncRequestFutureImpl to not clear
> cache.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-27491) AsyncProcess should not clear meta cache for RejectedExecutionException
[
https://issues.apache.org/jira/browse/HBASE-27491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645663#comment-17645663
]
Hudson commented on HBASE-27491:
Results for branch branch-2.5
[build #264 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/264/]:
(/) *{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/264/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/264/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/264/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/264/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> AsyncProcess should not clear meta cache for RejectedExecutionException
> ---
>
> Key: HBASE-27491
> URL: https://issues.apache.org/jira/browse/HBASE-27491
> Project: HBase
> Issue Type: Improvement
>Reporter: Bryan Beaudreault
>Assignee: Briana Augenreich
>Priority: Major
> Fix For: 2.4.16, 2.5.3
>
>
> Batch requests using AsyncProcess get submitted to a thread pool. If the pool
> is too small or backing regionservers are overloaded, the pool may reject
> requests. Currently this causes a cache clear, which only exacerbates issues
> in most cases.
> If there's a real reason to clear cache, the individual failing tasks that
> actually get accepted into the pool should be enough to appropriately clear
> the cache. So let's special case REE in AsyncRequestFutureImpl to not clear
> cache.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-27491) AsyncProcess should not clear meta cache for RejectedExecutionException
[
https://issues.apache.org/jira/browse/HBASE-27491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645548#comment-17645548
]
Hudson commented on HBASE-27491:
Results for branch branch-2
[build #700 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/700/]:
(/) *{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/700/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/700/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/700/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/700/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> AsyncProcess should not clear meta cache for RejectedExecutionException
> ---
>
> Key: HBASE-27491
> URL: https://issues.apache.org/jira/browse/HBASE-27491
> Project: HBase
> Issue Type: Improvement
>Reporter: Bryan Beaudreault
>Assignee: Briana Augenreich
>Priority: Major
> Fix For: 2.4.16, 2.5.3
>
>
> Batch requests using AsyncProcess get submitted to a thread pool. If the pool
> is too small or backing regionservers are overloaded, the pool may reject
> requests. Currently this causes a cache clear, which only exacerbates issues
> in most cases.
> If there's a real reason to clear cache, the individual failing tasks that
> actually get accepted into the pool should be enough to appropriately clear
> the cache. So let's special case REE in AsyncRequestFutureImpl to not clear
> cache.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-27491) AsyncProcess should not clear meta cache for RejectedExecutionException
[
https://issues.apache.org/jira/browse/HBASE-27491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645494#comment-17645494
]
Hudson commented on HBASE-27491:
Results for branch branch-2.4
[build #476 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/476/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/476/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/476/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/476/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/476/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> AsyncProcess should not clear meta cache for RejectedExecutionException
> ---
>
> Key: HBASE-27491
> URL: https://issues.apache.org/jira/browse/HBASE-27491
> Project: HBase
> Issue Type: Improvement
>Reporter: Bryan Beaudreault
>Assignee: Briana Augenreich
>Priority: Major
> Fix For: 2.4.16, 2.5.3
>
>
> Batch requests using AsyncProcess get submitted to a thread pool. If the pool
> is too small or backing regionservers are overloaded, the pool may reject
> requests. Currently this causes a cache clear, which only exacerbates issues
> in most cases.
> If there's a real reason to clear cache, the individual failing tasks that
> actually get accepted into the pool should be enough to appropriately clear
> the cache. So let's special case REE in AsyncRequestFutureImpl to not clear
> cache.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-27491) AsyncProcess should not clear meta cache for RejectedExecutionException
[ https://issues.apache.org/jira/browse/HBASE-27491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642613#comment-17642613 ] Briana Augenreich commented on HBASE-27491: --- Picking this up! > AsyncProcess should not clear meta cache for RejectedExecutionException > --- > > Key: HBASE-27491 > URL: https://issues.apache.org/jira/browse/HBASE-27491 > Project: HBase > Issue Type: Improvement >Reporter: Bryan Beaudreault >Assignee: Briana Augenreich >Priority: Major > > Batch requests using AsyncProcess get submitted to a thread pool. If the pool > is too small or backing regionservers are overloaded, the pool may reject > requests. Currently this causes a cache clear, which only exacerbates issues > in most cases. > If there's a real reason to clear cache, the individual failing tasks that > actually get accepted into the pool should be enough to appropriately clear > the cache. So let's special case REE in AsyncRequestFutureImpl to not clear > cache. -- This message was sent by Atlassian Jira (v8.20.10#820010)
