[
https://issues.apache.org/jira/browse/PHOENIX-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16466262#comment-16466262
]
Vincent Poon commented on PHOENIX-4726:
---------------------------------------
[~xucang] it looks like there are two cases where we can be in 'b' state for
async builds:
"ALTER INDEX...REBUILD" which sets ASYNC_REBUILD_TIMESTAMP
"CREATE INDEX...ASYNC" which sets ASYNC_CREATED_DATE
I believe the only other time an index is in 'b' is for synchronous creations
"CREATE INDEX..." (without the ASYNC). There's a possibility we get stuck in
that too - I don't know if there's an easy way to get the start timestamp for
that. But for now let's focus on when we get stuck in the prior two, which
should be an easy check against those two timestamps I listed.
> save index build timestamp
> --------------------------
>
> Key: PHOENIX-4726
> URL: https://issues.apache.org/jira/browse/PHOENIX-4726
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Xu Cang
> Priority: Minor
>
> save index build timestamp, similar to ASYNC_REBUILD_TIMESTAMP,
> Check IndexUtil.java for related code.
> The reason this can be useful is: We saw a case index state stuck in 'b' for
> quite some long time. And without a timestamp to indicate where it started,
> it's hard to tell if this is a legit running task or stuck...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
