You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Swapnil Bawaskar (JIRA)" <ji...@apache.org> on 2016/10/01 22:22:21 UTC

[jira] [Updated] (GEODE-1724) For updating client cq stats, we should not go to disk

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

Swapnil Bawaskar updated GEODE-1724:
------------------------------------
    Fix Version/s: 1.0.0-incubating

> For updating client cq stats, we should not go to disk
> ------------------------------------------------------
>
>                 Key: GEODE-1724
>                 URL: https://issues.apache.org/jira/browse/GEODE-1724
>             Project: Geode
>          Issue Type: Bug
>          Components: client queues
>            Reporter: Hitesh Khamesra
>            Assignee: Hitesh Khamesra
>             Fix For: 1.0.0-incubating
>
>
> durable client -queue with overflow, In this case overflow client queue uses LIFO policy. Because of that we put new entry on disk first. But, after putting that entry into queue that thread needs to update Cq stats, which causes that thread to fetch that value again from disk. that hurts performance. we should be updating any(all) client stats before putting that value into disk.



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