[
https://issues.jboss.org/browse/ISPN-7328?page=com.atlassian.jira.plugin....
]
Vladimir Blagojevic commented on ISPN-7328:
-------------------------------------------
I looked at this issue, tried quick and naive options but did not get too far. I think
we'll need to introduce some random backoff timer to fire a DMR check status call for
each cache. Hopefully, that will not overwhelm the server as much as current approach
seems to be. However, the ultimate and long-term solution for this issue appears to be
adding a container level call for cache statuses that will, in one swoop, return statuses
for all container caches. We can then keep random time bounded timer that will fire and
update status for all/individual caches real time. Thoughts [~pzapataf] [~ryanemerson]?
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)