phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samarth Jain (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-2622) Writes to transactional table get slower after regions splits to multiple region servers
Date Fri, 22 Jan 2016 23:15:39 GMT

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

Samarth Jain commented on PHOENIX-2622:
---------------------------------------

Patch looks good, [~jamestaylor]. 

One minor comment - not sure you really need a separate delegate class DelegateTransactionAware.
You can just have the PhoenixReadFence implement TransactionAware interface and store the
TransactionAware returned by VisibilityFence.create(key) in a member variable named delegate/readFence.
PhoenixReadFence then can implement TransactionAware interface along with adding the equals()
and hashcode() methods. 

> Writes to transactional table get slower after regions splits to multiple region servers
> ----------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-2622
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2622
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Mujtaba Chohan
>             Fix For: 4.7.0
>
>         Attachments: PHOENIX-2622.patch, upsert_rate.png
>
>
> Upsert rate get slower for transactional table as more and more regions gets split to
different region servers. More details to be added. !upsert_rate.png! This chart shows the
upsert rate of 100K batches over time for transactional vs standard table for a total of 4M
rows split in 6 regions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message