[
https://issues.jboss.org/browse/ISPN-7328?page=com.atlassian.jira.plugin....
]
Ryan Emerson commented on ISPN-7328:
------------------------------------
[~vblagojevic] I definitely think the ideal approach is to implement something on the
server side as you state. However, in the mean time we could potentially reduce the number
of server server requests by utilising wildcards to get the status of all cache types
across all containers and then filtering this on the client side e.g. call:
`/host=master/server=server-one/subsystem=datagrid-infinispan/cache-container=*/distributed-cache=*:read-attribute(name=cache-availability)`
and then process the results. This approach is complicated by the fact that we would have
to ensure that we send requests to a host/server combo that is valid for a specific cache.
Administration console - cache statuses in cache container page
behave randomly
-------------------------------------------------------------------------------
Key: ISPN-7328
URL:
https://issues.jboss.org/browse/ISPN-7328
Project: Infinispan
Issue Type: Bug
Components: Console
Affects Versions: 9.0.0.Beta1
Reporter: Jiří Holuša
Assignee: Vladimir Blagojevic
Priority: Minor
Attachments: screenshot1.png
Steps to reproduce: create more caches (in my case at least ~20), go to cache container
and try to refresh the page several times. It should sometimes appear that some of the
cache has yellow warning status, see attached screenshot.
This occurs very randomly and only with more caches (and probably more servers). IMHO
there is some kind of timeout issue that the console fails to retrieve statuses from all
caches in time.
I think the best solution would be to, when waiting for retrieving of the cache status,
have instead of "warning" icon some kind of spinner which would basically signal
"I haven't got the status yet". This would also solve a bit of
user-unfriendliness, which is when you go to cache container, initially all the statuses
are "warning" and then they change to "OK". This moment can time quite
some time when there are more caches and can confuse users quite a bit.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)