[
https://issues.apache.org/jira/browse/HBASE-24311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anoop Sam John updated HBASE-24311:
-----------------------------------
Description:
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]
was:
Now the warn logs look like
STUCK: MultiVersionConcurrencyControl{readPoint=30944485, writePoint=30944498}
We dont 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]
> Add more details in MultiVersionConcurrencyControl STUCK 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)
