[JBoss JIRA] (ISPN-9177) Add RBAC to admin console pages
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-9177?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9177:
-------------------------------
Fix Version/s: 9.4.3.Final
(was: 9.4.2.Final)
> 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
> Priority: Major
> Fix For: 9.4.3.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.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9173) Availability mode should be updated atomically with the actual members
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-9173?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9173:
-------------------------------
Fix Version/s: 9.4.3.Final
(was: 9.4.2.Final)
> 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
> Priority: Major
> Labels: testsuite_stability
> Fix For: 9.4.3.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.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9161) Description of StateTransferManager attributes does not match the behaviour or show wrong content
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-9161?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9161:
-------------------------------
Fix Version/s: 9.4.3.Final
(was: 9.4.2.Final)
> 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
> Priority: Major
> Fix For: 9.4.3.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.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9124) Uncaught exception in CounterConfigurationManager.startCounterCache
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-9124?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9124:
-------------------------------
Fix Version/s: 9.4.3.Final
(was: 9.4.2.Final)
> Uncaught exception in CounterConfigurationManager.startCounterCache
> -------------------------------------------------------------------
>
> Key: ISPN-9124
> URL: https://issues.jboss.org/browse/ISPN-9124
> Project: Infinispan
> Issue Type: Task
> Components: Test Suite - Core
> Affects Versions: 9.2.2.Final
> Reporter: Dan Berindei
> Priority: Major
> Fix For: 9.4.3.Final
>
>
> {{CounterConfigurationManager.startCounterCache}} starts the cache asynchronously, but a short test may stop the cache manager before the worker thread got to do anything. The worker thread doesn't catch the exception, so it's just logged on the console:
> {noformat}
> Exception in thread "async-thread--p132-t1" org.infinispan.IllegalLifecycleStateException: Cache container has been stopped and cannot be reused. Recreate the cache container.
> at org.infinispan.manager.DefaultCacheManager.assertIsNotTerminated(DefaultCacheManager.java:951)
> at org.infinispan.manager.DefaultCacheManager.internalGetCache(DefaultCacheManager.java:465)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:461)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:447)
> at org.infinispan.counter.impl.manager.CounterConfigurationManager.lambda$startCounterCache$5(CounterConfigurationManager.java:230)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9366) Cache.size optimizations
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-9366?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9366:
-------------------------------
Fix Version/s: 9.4.3.Final
(was: 9.4.2.Final)
> Cache.size optimizations
> ------------------------
>
> Key: ISPN-9366
> URL: https://issues.jboss.org/browse/ISPN-9366
> Project: Infinispan
> Issue Type: Enhancement
> Reporter: William Burns
> Assignee: William Burns
> Priority: Major
> Fix For: 9.4.3.Final
>
>
> Now that we have a segmented data container and segmented store we can add optimizations for the Cache.size operation in various configurations.
> If a store is configured, passivation must be disabled for any of these optimizations related to stores to work
> # Shared store can just invoke Store.size
> # No store & no expired entries can invoke DataContainer.sizeIncludingExpired(IntSet)
> # Non shared store can invoke Store.size(IntSet)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months