[jira] [Commented] (HBASE-20232) [LOGGING] Formatting around close and flush
[
https://issues.apache.org/jira/browse/HBASE-20232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16416677#comment-16416677
]
Hudson commented on HBASE-20232:
Results for branch HBASE-19064
[build #77 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> [LOGGING] Formatting around close and flush
> ---
>
> Key: HBASE-20232
> URL: https://issues.apache.org/jira/browse/HBASE-20232
> Project: HBase
> Issue Type: Sub-task
>Reporter: stack
>Assignee: stack
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-20232.branch-2.001.patch
>
>
> More log formatting. Fix issue where we had a param too many identified in
> parent issue. Remove some redundancy logging around flush and close. Use
> encoded regionname instead of full beast. Use SLF4J params. Remove some if
> debug tests. Use same formatter everywhere in flush when printing out data
> sizes (we had two types). A miscellany.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20232) [LOGGING] Formatting around close and flush
[
https://issues.apache.org/jira/browse/HBASE-20232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407834#comment-16407834
]
Hudson commented on HBASE-20232:
Results for branch master
[build #268 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/268/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/268//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/268//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/268//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> [LOGGING] Formatting around close and flush
> ---
>
> Key: HBASE-20232
> URL: https://issues.apache.org/jira/browse/HBASE-20232
> Project: HBase
> Issue Type: Sub-task
>Reporter: stack
>Assignee: stack
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-20232.branch-2.001.patch
>
>
> More log formatting. Fix issue where we had a param too many identified in
> parent issue. Remove some redundancy logging around flush and close. Use
> encoded regionname instead of full beast. Use SLF4J params. Remove some if
> debug tests. Use same formatter everywhere in flush when printing out data
> sizes (we had two types). A miscellany.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20232) [LOGGING] Formatting around close and flush
[
https://issues.apache.org/jira/browse/HBASE-20232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407348#comment-16407348
]
Hudson commented on HBASE-20232:
Results for branch branch-2.0
[build #65 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/65/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/65//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/65//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/65//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> [LOGGING] Formatting around close and flush
> ---
>
> Key: HBASE-20232
> URL: https://issues.apache.org/jira/browse/HBASE-20232
> Project: HBase
> Issue Type: Sub-task
>Reporter: stack
>Assignee: stack
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-20232.branch-2.001.patch
>
>
> More log formatting. Fix issue where we had a param too many identified in
> parent issue. Remove some redundancy logging around flush and close. Use
> encoded regionname instead of full beast. Use SLF4J params. Remove some if
> debug tests. Use same formatter everywhere in flush when printing out data
> sizes (we had two types). A miscellany.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20232) [LOGGING] Formatting around close and flush
[
https://issues.apache.org/jira/browse/HBASE-20232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407300#comment-16407300
]
Hudson commented on HBASE-20232:
Results for branch branch-2
[build #509 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/509/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/509//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/509//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/509//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> [LOGGING] Formatting around close and flush
> ---
>
> Key: HBASE-20232
> URL: https://issues.apache.org/jira/browse/HBASE-20232
> Project: HBase
> Issue Type: Sub-task
>Reporter: stack
>Assignee: stack
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-20232.branch-2.001.patch
>
>
> More log formatting. Fix issue where we had a param too many identified in
> parent issue. Remove some redundancy logging around flush and close. Use
> encoded regionname instead of full beast. Use SLF4J params. Remove some if
> debug tests. Use same formatter everywhere in flush when printing out data
> sizes (we had two types). A miscellany.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
