[
https://issues.apache.org/jira/browse/HCATALOG-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13228407#comment-13228407
]
Thomas Weise commented on HCATALOG-311:
---------------------------------------
There will be potentially many current/expired transactions in list, need to
handle expiration accordingly:
* Integrate expiration inline/lazily as part of begin/abort/snapshot
* Decided not to use a timer based thread option - benefits don’t justify added
complexity at this time
* beginTransaction to perform actual expiration with revision data storage
update (interval ~30s) - need to read modify and write open revisions at that
point anyways
* Skip expired transactions from active list in createSnapshot (cleanup only
happens as side effect of subsequent beginTransaction calls)
Limitation: We initially will only handle revision data and don’t delete
corresponding data from HBase (no “rollback”)
> Revision Manager Transaction Expiration
> ---------------------------------------
>
> Key: HCATALOG-311
> URL: https://issues.apache.org/jira/browse/HCATALOG-311
> Project: HCatalog
> Issue Type: Sub-task
> Components: storage handlers
> Reporter: Thomas Weise
> Assignee: Thomas Weise
>
> Changes to existing inline expiration behavior to scale and avoid side
> effects on read.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
