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

ASF GitHub Bot commented on TEPHRA-270:
---------------------------------------

Github user anew commented on a diff in the pull request:

    https://github.com/apache/incubator-tephra/pull/72#discussion_r184323707
  
    --- Diff: tephra-core/src/main/java/org/apache/tephra/coprocessor/TransactionStateCache.java ---
    @@ -78,6 +78,7 @@ protected void startUp() throws Exception {
       protected void shutDown() throws Exception {
         if (refreshService != null) {
           refreshService.interrupt();
    +      refreshService.join(1000);
    --- End diff --
    
    this means, if the refreshService does not finish within a second, shutdown() will throw exception? And the remainder of the shutdown sequence is not performed? Is that intentional?


> Avoid transaction state cache refresh on co-procesor startup
> ------------------------------------------------------------
>
>                 Key: TEPHRA-270
>                 URL: https://issues.apache.org/jira/browse/TEPHRA-270
>             Project: Tephra
>          Issue Type: Improvement
>          Components: core
>            Reporter: Poorna Chandra
>            Assignee: Poorna Chandra
>            Priority: Major
>             Fix For: 0.14.0-incubating
>
>
> Transaction state cache, on startup, refreshes the transaction snapshot from HDFS. The transaction state cache startup is called during HBase co-processor startup. The refresh of the transaction snapshot can block, thus blocking the co-processor startup. 
> The subsequent transaction snapshot refreshes happen in the background. Also - there is no guarantee that a snapshot will be present during the refresh on startup. Hence it is okay not to refresh the snapshot during snapshot, but do it in background.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)