[Red Hat JIRA] (ISPN-12151) Add error count metric
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12151?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12151:
-----------------------------------
Fix Version/s: 12.0.0.CR1
(was: 12.0.0.Dev07)
> Add error count metric
> ----------------------
>
> Key: ISPN-12151
> URL: https://issues.redhat.com/browse/ISPN-12151
> Project: Infinispan
> Issue Type: Feature Request
> Components: Analytics
> Affects Versions: 11.0.1.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 12.0.0.Final, 12.0.0.CR1
>
>
> {{CacheMgmtInterceptor}} has metrics for the different kind of key operations, but errors are not tracked. We should add a metric to count errors, and perhaps a histogram for the duration of failed invocations as well.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 1 month
[Red Hat JIRA] (ISPN-9738) Support for entry iteration in the REST server
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-9738?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-9738:
----------------------------------
Fix Version/s: 12.0.0.CR1
(was: 12.0.0.Dev07)
> Support for entry iteration in the REST server
> ----------------------------------------------
>
> Key: ISPN-9738
> URL: https://issues.redhat.com/browse/ISPN-9738
> Project: Infinispan
> Issue Type: Enhancement
> Components: REST
> Affects Versions: 9.4.1.Final
> Reporter: Gustavo Fernandes
> Assignee: Katia Aresti
> Priority: Optional
> Fix For: 12.0.0.CR1
>
>
> Currently the REST server has an operation to get all keys that has limitations since all the keys are retrieved to a single node before serving to the client.
> Ideally, it should have an efficient way of retrieving entries making use of iterators. The API should provide a cursor/scroll/handle so that the client can pull the data without causing memory issues.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 1 month
[Red Hat JIRA] (ISPN-12261) Protocol server transport management
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12261?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12261:
-----------------------------------
Fix Version/s: 12.0.0.CR1
(was: 12.0.0.Dev07)
> Protocol server transport management
> -------------------------------------
>
> Key: ISPN-12261
> URL: https://issues.redhat.com/browse/ISPN-12261
> Project: Infinispan
> Issue Type: Feature Request
> Components: CLI, JMX, reporting and management, Server
> Affects Versions: 12.0.0.Dev02
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 12.0.0.CR1
>
>
> the WF-server had the ability to stop/start a transport via the CLI (ISPN-11240).
> The new server should have a similar capability.
> h4. Protocol management via CLI
> {noformat}
> $ cli.sh connector status
> $ cli.sh connector stop hotrod
> $ cli.sh connector start hotrod
> {noformat}
> Aside from start/stop, we should also leverage netty's ipfilter handler which allows filtering based on subnet so that traffic can be blocked selectively.
> h4. IP Filtering
> {code:xml}
> <endpoints socket-binding="default" security-realm="default">
> <ip-filter>
> <reject from="172.16.0.0/16"/>
> <accept from="127.0.0.0/8"/>
> </ip-filter>
> <hotrod-connector/>
> <rest-connector/>
> </endpoints>
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 1 month