[infinispan-issues] [JBoss JIRA] (ISPN-6700) Restart required dialog show only after editing distributed cache

[Ryan Emerson (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242390#comment-13242390 ] 

Ryan Emerson commented on ISPN-6700:
------------------------------------

[~jholusa] The reason that the restart dialog does not appear for eviction->size is because the resource-description returned by the server indicates that changing this field does not require a restart. This is also why this field only states undo to the right and does not state "restart required."

The restart dialog was not previously shown for caches other than distributed ones, was because a reference to the outside-controller (which handles the restart dialog) was not passed to the configuration-section directive. 

> Restart required dialog show only after editing distributed cache
> -----------------------------------------------------------------
>
>                 Key: ISPN-6700
>                 URL: https://issues.jboss.org/browse/ISPN-6700
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Console
>    Affects Versions: 8.2.2.Final
>            Reporter: Jiří Holuša
>            Assignee: Ryan Emerson
>
> Page: Cache configuration page (select cache container -> select cache -> click Configuration)
> When editing any property of replicated, local and invalidation cache, for example expiration lifespan. When I change somehow the value, right next to the input box, there appears: " (Undo) Restart needed". Then I click "Apply changes", a confirmation dialog pops up with text: "Update configuration template <cache>?", I click "Update" and it's done. I have to manually search for the option of restarting the cluster.
> However, if I do it with distributed cache, after clicking "Update" in confirmation dialog, another dialog pops up with text: "Attributes changed require a restart of the affected servers. If you need to make additional configuration changes right now, consider restarting servers after the last change." with options "Restart now" and "Restart later".
> IMHO this should be consistent and the latter option is correct. If restart is needed (as the tooltip says), console should offer it right away.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)