[
https://issues.apache.org/jira/browse/NIFI-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14906175#comment-14906175
]
ASF GitHub Bot commented on NIFI-989:
-------------------------------------
GitHub user joemeszaros opened a pull request:
https://github.com/apache/nifi/pull/94
NIFI-989: Support size() operation in distributed map cache
The distributed map cache server is a great tool for caching along with the
cache client (DistributedMapCacheClientService), but after you configure and
enable it, it is a black box. You are unable to get any information from the
cache e.g how much entries live in the cache.
The purpose of this PR to create an extended cache interface and associated
implementations to support the size() operation, which returns the number of
entries in the distributed cache.
It could be a first step in a direction of a more transparent cache, where
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, ...).
Similar to:
- memcached :
https://docs.oracle.com/cd/E17952_01/refman-5.0-en/ha-memcached-stats-general.html
- couchbase: http://blog.couchbase.com/monitoring-couchbase-cluster
- redis:
http://haydenjames.io/using-redis-stat-for-redis-statistics-tracking/
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 like to
debug cache related problems, or just get basic interaction with the cache.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ImpressTV/nifi NIFI-989
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/94.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #94
----
commit 5a8578a70db1b9c61d26bbd06132ee035929378f
Author: Joe <[email protected]>
Date: 2015-09-24T10:26:42Z
NIFI-989: Support size() operation in distributed map cache
----
> 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észáros
> Priority: Minor
> Labels: cache, command-line, distributed, improvement
>
> The distributed map cache server is a great tool for caching along with the
> cache client (DistributedMapCacheClientService), but after you configure and
> enable it, it is a black box. You are unable to get any information from the
> cache e.g how much entries live in the cache.
> The purpose of this issue to extend the cache interface and associated
> implementations to support the size() operation, which returns the number of
> entries in the distributed cache.
> It could be a first step in a direction of a more transparent cache, where
> 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, ...).
> Similar to:
> - memcached :
> https://docs.oracle.com/cd/E17952_01/refman-5.0-en/ha-memcached-stats-general.html
> - couchbase: http://blog.couchbase.com/monitoring-couchbase-cluster
> - redis: http://haydenjames.io/using-redis-stat-for-redis-statistics-tracking/
> 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 like to
> debug cache related problems, or just get basic interaction with the cache.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
