[ 
https://issues.apache.org/jira/browse/PHOENIX-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472668#comment-16472668
 ] 

Xu Cang commented on PHOENIX-4726:
----------------------------------

"[~xucang] Can you use EnvironmentEdgeManager.currentTimeMillis() instead of 
System.currentTimeMillis() ?

Thanks!"

 

--Xu: will do.

> 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
>            Assignee: Xu Cang
>            Priority: Minor
>         Attachments: PHOENIX-4726.patch.1, PHOENIX-4726.patch.2, 
> PHOENIX-4726.patch.3
>
>
> 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)

Reply via email to