[jira] [Commented] (HBASE-26525) Use unique thread name for group WALs
[
https://issues.apache.org/jira/browse/HBASE-26525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848480#comment-17848480
]
Hudson commented on HBASE-26525:
Results for branch branch-2
[build #1060 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1060/]:
(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/1060/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/1060/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/1060/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/1060/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}
> Use unique thread name for group WALs
> -
>
> Key: HBASE-26525
> URL: https://issues.apache.org/jira/browse/HBASE-26525
> Project: HBase
> Issue Type: Improvement
> Components: wal
>Affects Versions: 3.0.0-alpha-1, 2.0.0
>Reporter: Xiaolin Ha
>Assignee: Xiaolin Ha
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0-alpha-2, 2.4.9, 2.7.0, 2.6.1, 2.5.9
>
> Attachments: image-2021-12-01-16-20-18-912.png,
> image-2021-12-01-16-21-18-032.png, image-2021-12-02-17-38-21-959.png
>
>
> The consumer threads for each WAL group has the same name, since they only
> use the WAL root dir in the thread name.
> {code:java}
> new ThreadFactoryBuilder().setNameFormat("AsyncFSWAL-%d-" +
> rootDir.toString()).
> setDaemon(true).build()); {code}
> For example, for BoundedGroupingStrategy, the consumer threads names are as
> follows,
> !image-2021-12-01-16-20-18-912.png|width=1199,height=130!
> We can use the log prefix instead, the consumer threads names will be changed
> to
> !image-2021-12-02-17-38-21-959.png|width=1102,height=197!
> So we can clearly see what happens from the log and the jstack info if
> something wrong with the WAL.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-26525) Use unique thread name for group WALs
[
https://issues.apache.org/jira/browse/HBASE-26525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848448#comment-17848448
]
Hudson commented on HBASE-26525:
Results for branch branch-2.6
[build #122 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/122/]:
(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.6/122/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.6/122/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.6/122/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.6/122/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}
> Use unique thread name for group WALs
> -
>
> Key: HBASE-26525
> URL: https://issues.apache.org/jira/browse/HBASE-26525
> Project: HBase
> Issue Type: Improvement
> Components: wal
>Affects Versions: 3.0.0-alpha-1, 2.0.0
>Reporter: Xiaolin Ha
>Assignee: Xiaolin Ha
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0-alpha-2, 2.4.9, 2.7.0, 2.6.1, 2.5.9
>
> Attachments: image-2021-12-01-16-20-18-912.png,
> image-2021-12-01-16-21-18-032.png, image-2021-12-02-17-38-21-959.png
>
>
> The consumer threads for each WAL group has the same name, since they only
> use the WAL root dir in the thread name.
> {code:java}
> new ThreadFactoryBuilder().setNameFormat("AsyncFSWAL-%d-" +
> rootDir.toString()).
> setDaemon(true).build()); {code}
> For example, for BoundedGroupingStrategy, the consumer threads names are as
> follows,
> !image-2021-12-01-16-20-18-912.png|width=1199,height=130!
> We can use the log prefix instead, the consumer threads names will be changed
> to
> !image-2021-12-02-17-38-21-959.png|width=1102,height=197!
> So we can clearly see what happens from the log and the jstack info if
> something wrong with the WAL.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-26525) Use unique thread name for group WALs
[
https://issues.apache.org/jira/browse/HBASE-26525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848335#comment-17848335
]
Hudson commented on HBASE-26525:
Results for branch branch-2.5
[build #533 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/533/]:
(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.5/533/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.5/533/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.5/533/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/533/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}
> Use unique thread name for group WALs
> -
>
> Key: HBASE-26525
> URL: https://issues.apache.org/jira/browse/HBASE-26525
> Project: HBase
> Issue Type: Improvement
> Components: wal
>Affects Versions: 3.0.0-alpha-1, 2.0.0
>Reporter: Xiaolin Ha
>Assignee: Xiaolin Ha
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0-alpha-2, 2.4.9, 2.7.0, 2.6.1, 2.5.9
>
> Attachments: image-2021-12-01-16-20-18-912.png,
> image-2021-12-01-16-21-18-032.png, image-2021-12-02-17-38-21-959.png
>
>
> The consumer threads for each WAL group has the same name, since they only
> use the WAL root dir in the thread name.
> {code:java}
> new ThreadFactoryBuilder().setNameFormat("AsyncFSWAL-%d-" +
> rootDir.toString()).
> setDaemon(true).build()); {code}
> For example, for BoundedGroupingStrategy, the consumer threads names are as
> follows,
> !image-2021-12-01-16-20-18-912.png|width=1199,height=130!
> We can use the log prefix instead, the consumer threads names will be changed
> to
> !image-2021-12-02-17-38-21-959.png|width=1102,height=197!
> So we can clearly see what happens from the log and the jstack info if
> something wrong with the WAL.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-26525) Use unique thread name for group WALs
[
https://issues.apache.org/jira/browse/HBASE-26525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848096#comment-17848096
]
Duo Zhang commented on HBASE-26525:
---
We missed the commit on branch-2 in the past so we need to reset the fix
versions.
Thanks [~szucsvillo] for helping!
> Use unique thread name for group WALs
> -
>
> Key: HBASE-26525
> URL: https://issues.apache.org/jira/browse/HBASE-26525
> Project: HBase
> Issue Type: Improvement
> Components: wal
>Affects Versions: 3.0.0-alpha-1, 2.0.0
>Reporter: Xiaolin Ha
>Assignee: Xiaolin Ha
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0-alpha-2, 2.4.9, 2.7.0, 2.6.1, 2.5.9
>
> Attachments: image-2021-12-01-16-20-18-912.png,
> image-2021-12-01-16-21-18-032.png, image-2021-12-02-17-38-21-959.png
>
>
> The consumer threads for each WAL group has the same name, since they only
> use the WAL root dir in the thread name.
> {code:java}
> new ThreadFactoryBuilder().setNameFormat("AsyncFSWAL-%d-" +
> rootDir.toString()).
> setDaemon(true).build()); {code}
> For example, for BoundedGroupingStrategy, the consumer threads names are as
> follows,
> !image-2021-12-01-16-20-18-912.png|width=1199,height=130!
> We can use the log prefix instead, the consumer threads names will be changed
> to
> !image-2021-12-02-17-38-21-959.png|width=1102,height=197!
> So we can clearly see what happens from the log and the jstack info if
> something wrong with the WAL.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-26525) Use unique thread name for group WALs
[
https://issues.apache.org/jira/browse/HBASE-26525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17455234#comment-17455234
]
Hudson commented on HBASE-26525:
Results for branch master
[build #463 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/463/]:
(/) *{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/463/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/463/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/463/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}
> Use unique thread name for group WALs
> -
>
> Key: HBASE-26525
> URL: https://issues.apache.org/jira/browse/HBASE-26525
> Project: HBase
> Issue Type: Improvement
> Components: wal
>Affects Versions: 3.0.0-alpha-1, 2.0.0
>Reporter: Xiaolin Ha
>Assignee: Xiaolin Ha
>Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-2, 2.4.9
>
> Attachments: image-2021-12-01-16-20-18-912.png,
> image-2021-12-01-16-21-18-032.png, image-2021-12-02-17-38-21-959.png
>
>
> The consumer threads for each WAL group has the same name, since they only
> use the WAL root dir in the thread name.
> {code:java}
> new ThreadFactoryBuilder().setNameFormat("AsyncFSWAL-%d-" +
> rootDir.toString()).
> setDaemon(true).build()); {code}
> For example, for BoundedGroupingStrategy, the consumer threads names are as
> follows,
> !image-2021-12-01-16-20-18-912.png|width=1199,height=130!
> We can use the log prefix instead, the consumer threads names will be changed
> to
> !image-2021-12-02-17-38-21-959.png|width=1102,height=197!
> So we can clearly see what happens from the log and the jstack info if
> something wrong with the WAL.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (HBASE-26525) Use unique thread name for group WALs
[
https://issues.apache.org/jira/browse/HBASE-26525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17454938#comment-17454938
]
Hudson commented on HBASE-26525:
Results for branch branch-2.4
[build #254 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/254/]:
(/) *{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/254/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/254/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/254/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/254/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}
> Use unique thread name for group WALs
> -
>
> Key: HBASE-26525
> URL: https://issues.apache.org/jira/browse/HBASE-26525
> Project: HBase
> Issue Type: Improvement
> Components: wal
>Affects Versions: 3.0.0-alpha-1, 2.0.0
>Reporter: Xiaolin Ha
>Assignee: Xiaolin Ha
>Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-2, 2.4.9
>
> Attachments: image-2021-12-01-16-20-18-912.png,
> image-2021-12-01-16-21-18-032.png, image-2021-12-02-17-38-21-959.png
>
>
> The consumer threads for each WAL group has the same name, since they only
> use the WAL root dir in the thread name.
> {code:java}
> new ThreadFactoryBuilder().setNameFormat("AsyncFSWAL-%d-" +
> rootDir.toString()).
> setDaemon(true).build()); {code}
> For example, for BoundedGroupingStrategy, the consumer threads names are as
> follows,
> !image-2021-12-01-16-20-18-912.png|width=1199,height=130!
> We can use the log prefix instead, the consumer threads names will be changed
> to
> !image-2021-12-02-17-38-21-959.png|width=1102,height=197!
> So we can clearly see what happens from the log and the jstack info if
> something wrong with the WAL.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
