[
https://issues.apache.org/jira/browse/PHOENIX-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xu Cang updated PHOENIX-4726:
-----------------------------
Description:
save index build timestamp, similar to ASYNC_REBUILD_TIMESTAMP, or
ASYNC_CREATED_DATE
("SYNC_INDEX_CREATED_DATE" is my proposed name for SYNC case.)
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...
was:
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...
Summary: save index build timestamp -- for SYNC case only. (was: save
index build timestamp)
> save index build timestamp -- for SYNC case only.
> -------------------------------------------------
>
> 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, or
> ASYNC_CREATED_DATE
> ("SYNC_INDEX_CREATED_DATE" is my proposed name for SYNC case.)
>
> 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)
