[
https://issues.apache.org/jira/browse/HBASE-24311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17100704#comment-17100704
]
Hudson commented on HBASE-24311:
--------------------------------
Results for branch branch-1
[build #1293 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/1293/]:
(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-1/1293//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/1293//JDK7_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-1/1293//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 source release artifact{color}
-- See build output for details.
> Add more details in MultiVersionConcurrencyControl STUCK log message
> --------------------------------------------------------------------
>
> Key: HBASE-24311
> URL: https://issues.apache.org/jira/browse/HBASE-24311
> Project: HBase
> Issue Type: Improvement
> Reporter: Anoop Sam John
> Assignee: Anoop Sam John
> Priority: Major
> Fix For: 3.0.0-alpha-1, 1.7.0, 2.4.0
>
>
> Now the warn logs look like
> {code}
> STUCK: MultiVersionConcurrencyControl{readPoint=30944485, writePoint=30944498}
> {code}
> We don't have any details on which region the writes are stuck. It would be
> better to include the region name detail also in this log.
> May be we can even log for how long we are waiting for the read point to
> catch up.
> cc [~stack]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
