tephra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Xiaoman Huang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TEPHRA-247) Avoid encoding the transaction multiple times
Date Sat, 13 Jan 2018 03:27:00 GMT

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

Patrick Xiaoman Huang commented on TEPHRA-247:

Hi Andres,
when we start a tx, yes we will send the request to all region,
HTable.coprocesorService use several Futures to do the invocations concurrently, so I think
this will not affect the performance, but your concern is this will increase the probilities
of failure?
--region split
yes, this is the problem, can we use RegionObserver.postCompleteSplit() do some Cache.split()
means push caches to splited region?
-- timeout
tx has attribute of timeout, we use this to clean the tx out of cache?
-- checkpoint
I will look more on this.

I will do some more thinking on these.
Thanks for the reply

> Avoid encoding the transaction multiple times
> ---------------------------------------------
>                 Key: TEPHRA-247
>                 URL: https://issues.apache.org/jira/browse/TEPHRA-247
>             Project: Tephra
>          Issue Type: Improvement
>          Components: core, manager
>    Affects Versions: 0.12.0-incubating
>            Reporter: Andreas Neumann
>            Assignee: Andreas Neumann
>         Attachments: design.jpg
> Currently, the same transaction object is encoded again and again for every Get performed
in HBase. It would be better to cache the encoded transaction for the duration of the transaction
and reuse it, 

This message was sent by Atlassian JIRA

View raw message