You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Thomas D'Silva (JIRA)" <ji...@apache.org> on 2015/09/26 02:20:04 UTC

[jira] [Updated] (PHOENIX-2284) Remove call to returnAllSequences when connection count drop to zero

     [ https://issues.apache.org/jira/browse/PHOENIX-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas D'Silva updated PHOENIX-2284:
------------------------------------
    Summary: Remove call to returnAllSequences when connection count drop to zero  (was: Need ConnectionQueryServicesImpl.returnAllSequences to be configurable)

> Remove call to returnAllSequences when connection count drop to zero
> --------------------------------------------------------------------
>
>                 Key: PHOENIX-2284
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2284
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.5.0
>            Reporter: Brian Esserlieu
>
> Problem: Experimentally, we've discovered that >80% of sequences are never used.
> Cause: We work in an environment where we have multiple app servers, each with its own Phoenix client.  We have upsert operations that may span across multiple app servers (Phoenix clients), and upsert a smaller number of rows than the number of retrieved sequences based on the default cache size.  After each transaction, each client's connection is closed which triggers the sequences to prematurely get recycled.  
> Solution: We need the sequence recycling (ConnectionQueryServicesImpl.returnAllSequences) behavior to be configurable so we can turn it off, since it doesn't make sense in our environment.  



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