[JBoss JIRA] (ISPN-9209) Implement RemoteCache statistics
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-9209?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9209:
----------------------------------
Fix Version/s: 9.4.0.Final
(was: 9.4.0.CR3)
> Implement RemoteCache statistics
> --------------------------------
>
> Key: ISPN-9209
> URL: https://issues.jboss.org/browse/ISPN-9209
> Project: Infinispan
> Issue Type: Enhancement
> Components: Hot Rod
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 9.4.0.Final
>
>
> The Hot Rod client does not expose any local statistics (RemoteCacheManager.getStatistics() returns the server-side stats).
> We should have the following per-cache stats:
> - remote hits and hit avg time
> - remote misses and miss avg time
> - remote removes and remove avg time
> - near cache hits and avg time
> - near cache miss and avg time
> - near cache size
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (ISPN-9177) Add RBAC to admin console pages
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-9177?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9177:
----------------------------------
Fix Version/s: 9.4.0.Final
(was: 9.4.0.CR3)
> Add RBAC to admin console pages
> -------------------------------
>
> Key: ISPN-9177
> URL: https://issues.jboss.org/browse/ISPN-9177
> Project: Infinispan
> Issue Type: Feature Request
> Components: Console
> Affects Versions: 9.2.3.Final, 9.3.0.Beta1
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Fix For: 9.4.0.Final
>
>
> Up until now, we have assumed that admin user is able to invoke all operations, access and mutate all data from the admin console. With the advent of data manipulation capabilities in the console (ISPN-8759) and taking into account all existing management operations (some are destructive and irreversible), we should introduce RBAC to admin console page.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (ISPN-9173) Availability mode should be updated atomically with the actual members
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-9173?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9173:
----------------------------------
Fix Version/s: 9.4.0.Final
(was: 9.4.0.CR3)
> Availability mode should be updated atomically with the actual members
> ----------------------------------------------------------------------
>
> Key: ISPN-9173
> URL: https://issues.jboss.org/browse/ISPN-9173
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.3.0.Beta1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Labels: testsuite_stability
> Fix For: 9.4.0.Final
>
>
> This is a follow-up on ISPN-7682, which asks for the topology itself to be updated atomically.
> {{LocalTopologyManagerImpl}} has additional logic to update the availability mode first when the cache becomes degraded and to update it last when the cache becomes available, which means any delay between the updates cannot cause data inconsistencies.
> But that logic doesn't really belong in {{LocalTopologyManagerImpl}}, and it's easy to forget it's there (and in fact we had a bug there related to the new rebalance phases).
> In addition, tests that want to check the cache behaviour in degraded mode and wait only for the availability mode change will fail if there's a big delay between the availability mode change. I actually hit this while testing my ISPN-8731/ISPN-7682 changes, and I had added a random delay in {{StateConsumerImpl}} before {{distributionManager.setCacheTopology()}}.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (ISPN-9161) Description of StateTransferManager attributes does not match the behaviour or show wrong content
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-9161?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9161:
----------------------------------
Fix Version/s: 9.4.0.Final
(was: 9.4.0.CR3)
> Description of StateTransferManager attributes does not match the behaviour or show wrong content
> -------------------------------------------------------------------------------------------------
>
> Key: ISPN-9161
> URL: https://issues.jboss.org/browse/ISPN-9161
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Documentation-Core
> Reporter: Wolf-Dieter Fink
> Assignee: Dan Berindei
> Fix For: 9.4.0.Final
>
> Attachments: Screenshot from 2018-05-16 10-01-28.png
>
>
> Current description is:
> If true, the node has successfully joined the grid and is considered to hold state. If false, the join process is still in progress..
> But the behaviour is:
> It doesn't wait for the initial state transfer, it just waits for the coordinator to send it a topology before joinComplete is set to TRUE
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (ISPN-9367) State transfer should preserve the creation timestamp of entries
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-9367?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9367:
----------------------------------
Fix Version/s: 9.4.0.Final
(was: 9.4.0.CR3)
> State transfer should preserve the creation timestamp of entries
> ----------------------------------------------------------------
>
> Key: ISPN-9367
> URL: https://issues.jboss.org/browse/ISPN-9367
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.3.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 9.4.0.Final
>
>
> State transfer inserts values with the current time as the creation time. Since the entries store the expected lifespan and not the expected expiration time, entries on the receiving node could expire much later than intended.
> The argument probably doesn't apply to the timestamp of the last usage. Since state transfer process could be interpreted as a reader, it should be fine to extend the update the time of the last usage both on the sending node and on the receiving node.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months