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

Ohad Shacham commented on OMID-131:
-----------------------------------

It is a tradeoff between using HBase storage and returning Tephra's lists in 
each begin. Switching to row level will reduce the storage, however, might 
increase the scan/get times. 

> Enhance row level conlict detection to reduce client memory footprint.
> ----------------------------------------------------------------------
>
>                 Key: OMID-131
>                 URL: https://issues.apache.org/jira/browse/OMID-131
>             Project: Apache Omid
>          Issue Type: Improvement
>    Affects Versions: 1.0.1
>            Reporter: Yonatan Gottesman
>            Assignee: Yonatan Gottesman
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently even if omid is working in row level conflict detection, all the 
> cells are kept by the client until after commit for writing shadow cells or 
> removing them after abort.
> Instead the client should store only the rows or only the family.
> If we choose to store only the row, the client memory footprint will be 
> smaller, but if a region server wants to query a shadow cell for a cell it 
> might have to query a different region.
> On the other hand client can store the famelies of a writeset. This will have 
> a bigger footprint if we have lots of families but if a region queries a 
> shadow cell it will be on the same region.
>  
>  



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

Reply via email to