You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@omid.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2019/06/01 03:04:00 UTC

[jira] [Commented] (OMID-131) Enhance row level conlict detection to reduce client memory footprint.

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

Lars Hofhansl commented on OMID-131:
------------------------------------

Thinking about this again... What exactly is stored in the shadow column?

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