Mailing-List: contact commits-help@nifi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@nifi.apache.org
Date: Thu, 24 Sep 2015 10:34:04 +0000 (UTC)
From: =?utf-8?Q?Joe_M=C3=A9sz=C3=A1ros_=28JIRA=29?= <jira@apache.org>
To: commits@nifi.apache.org
Message-ID: <JIRA.12895809.1443021808000.61298.1443090844340@Atlassian.JIRA>
In-Reply-To: <JIRA.12895809.1443021808000@Atlassian.JIRA>
References: <JIRA.12895809.1443021808000@Atlassian.JIRA>
 <JIRA.12895809.1443021808600@arcas>
Subject: [jira] [Commented] (NIFI-989) Support size() operation in
 distributed map cache
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/NIFI-989?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D149061=
78#comment-14906178 ]=20

Joe M=C3=A9sz=C3=A1ros commented on NIFI-989:
-----------------------------------

>From client perspective, I created an ExtendedDistributedMapCacheClient int=
erface, which is the super interface of DistributedMapCacheClient. I choose=
 this name, instead of SizableDistributedMapCacheClient, because it gives u=
s more space. In the future we can add a new method, e.g. stat() to the new=
 interface, without change the interface name, and do not rename it Sizable=
DistributedMapCacheClientWithStats.

> Support size() operation in distributed map cache
> -------------------------------------------------
>
>                 Key: NIFI-989
>                 URL: https://issues.apache.org/jira/browse/NIFI-989
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: Joe M=C3=A9sz=C3=A1ros
>            Priority: Minor
>              Labels: cache, command-line, distributed, improvement
>
> The distributed map cache server is a great tool for caching along with t=
he cache client (DistributedMapCacheClientService), but after you configure=
 and enable it, it is a black box. You are unable to get any information fr=
om the cache e.g how much entries live in the cache.
> The purpose of this issue to extend the cache interface and associated im=
plementations to support the size() operation, which returns the number of=
=20
> entries in the distributed cache.=20
> It could be a first step in a direction of a more transparent cache, wher=
e the user can understand, what happens with the distributed cache. I mean =
after the size() operation, it could be really helpful to implement a stats=
() command, which s used to query the server about statistics it
> maintains and other internal data (e.g. evictions, hit rates, ...).=20
> Similar to:
>  - memcached : https://docs.oracle.com/cd/E17952_01/refman-5.0-en/ha-memc=
ached-stats-general.html
> - couchbase: http://blog.couchbase.com/monitoring-couchbase-cluster
> - redis: http://haydenjames.io/using-redis-stat-for-redis-statistics-trac=
king/
> I implemented a really simple command line tool, which can interact with =
the cache server from the command line, e.g. get a cache entry and it also =
able to get the size of the cache, which could be useful, when you would li=
ke to debug cache related problems, or just get basic interaction with the =
cache.


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