You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Michael Stack (Jira)" <ji...@apache.org> on 2020/05/04 15:14:00 UTC
[jira] [Commented] (HBASE-24311) Add more details in
MultiVersionConcurrencyControl STUCK log message
[ https://issues.apache.org/jira/browse/HBASE-24311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17099027#comment-17099027 ]
Michael Stack commented on HBASE-24311:
---------------------------------------
IIRC, the context doesn't have Region name (I might be wrong). Interested in why you are seeing these. Anything going on special w/ your storage tier?
> 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, 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)