tephra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Poorna Chandra (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TEPHRA-270) Avoid transaction state cache refresh on co-procesor startup
Date Thu, 26 Apr 2018 00:10:00 GMT

     [ https://issues.apache.org/jira/browse/TEPHRA-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Poorna Chandra updated TEPHRA-270:
----------------------------------
    Description: 
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.


  was:
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.



> 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)

Mime
View raw message