[JBoss JIRA] (ISPN-11784) Combine netty and non blocking thread pools
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-11784?page=com.atlassian.jira.plugi... ]
Work on ISPN-11784 started by Will Burns.
-----------------------------------------
> Combine netty and non blocking thread pools
> -------------------------------------------
>
> Key: ISPN-11784
> URL: https://issues.redhat.com/browse/ISPN-11784
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> We cannot simply drop in our non blocking thread pool as an executor for netty io event loop group. The reason is because Netty takes over control of that thread and only runs tasks submitted to its various event loops. To consolidate these we need to replace our non blocking thread pool with the netty thread pool so it can awake the thread to process tasks.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-11784) Combine netty and non blocking thread pools
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-11784?page=com.atlassian.jira.plugi... ]
Will Burns updated ISPN-11784:
------------------------------
Status: Open (was: New)
> Combine netty and non blocking thread pools
> -------------------------------------------
>
> Key: ISPN-11784
> URL: https://issues.redhat.com/browse/ISPN-11784
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Reporter: Will Burns
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> We cannot simply drop in our non blocking thread pool as an executor for netty io event loop group. The reason is because Netty takes over control of that thread and only runs tasks submitted to its various event loops. To consolidate these we need to replace our non blocking thread pool with the netty thread pool so it can awake the thread to process tasks.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-11763) Make cache authorization roles declaration implicit
by Pedro Ruivo (Jira)
[ https://issues.redhat.com/browse/ISPN-11763?page=com.atlassian.jira.plugi... ]
Pedro Ruivo updated ISPN-11763:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Make cache authorization roles declaration implicit
> ---------------------------------------------------
>
> Key: ISPN-11763
> URL: https://issues.redhat.com/browse/ISPN-11763
> Project: Infinispan
> Issue Type: Enhancement
> Components: Security
> Affects Versions: 11.0.0.Dev05
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 11.0.0.CR1
>
>
> Specifying cache authorization roles is a chore because a user must declare which global roles apply to each individual cache.
> By making the cache roles implicit, we can apply all roles declared in the global config to caches automatically:
> {code:xml}
> <cache-container>
> <security>
> <authorization>
> <identity-role-mapper/>
> <role name="AdminRole" permissions="ALL"/>
> <role name="ReaderRole" permissions="READ"/>
> <role name="WriterRole" permissions="WRITE"/>
> <role name="SupervisorRole" permissions="READ WRITE EXEC BULK_READ"/>
> </authorization>
> </security>
> <distributed-cache name="secure-implicit">
> <security><authorization/></security>
> </distributed-cache>
> <distributed-cache name="secure-explicit">
> <security><authorization roles="AdminRole ReaderRole WriterRole SupervisorRole"/></security>
> </distributed-cache>
> </cache-container>
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-11785) Docs: Server patching
by Pedro Ruivo (Jira)
[ https://issues.redhat.com/browse/ISPN-11785?page=com.atlassian.jira.plugi... ]
Pedro Ruivo updated ISPN-11785:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 11.0.0.CR1
10.1.9.Final
Resolution: Done
> Docs: Server patching
> ---------------------
>
> Key: ISPN-11785
> URL: https://issues.redhat.com/browse/ISPN-11785
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
> Fix For: 11.0.0.CR1, 10.1.9.Final
>
>
> CLI help text exists for the patching tool. Need to include help with the CLI command reference doc. Add procedural content for patching servers to CLI, Server Guide, Upgrade Guide.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-11800) Convert BackupReceiver to component
by Pedro Ruivo (Jira)
[ https://issues.redhat.com/browse/ISPN-11800?page=com.atlassian.jira.plugi... ]
Pedro Ruivo updated ISPN-11800:
-------------------------------
Fix Version/s: 11.0.0.CR1
> Convert BackupReceiver to component
> -----------------------------------
>
> Key: ISPN-11800
> URL: https://issues.redhat.com/browse/ISPN-11800
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core, Cross-Site Replication
> Affects Versions: 11.0.0.Dev05
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 11.0.0.CR1
>
>
> The {{BackupReceiver}} instance is created by {{BackupReceiverRepository}} and it needs access to the {{Cache}} instance for its dependencies.
> However, with the latest changes in Cross-Site Replication, it needs to be accessed by commands and the only way to do it is by doing:
> {code:java}
> BackupReceiver backupReceiver = registry.getGlobalComponentRegistry()
> .getComponent(BackupReceiverRepository.class)
> .getBackupReceiver(cache);
> {code}
> Bottom line: tt should be converted to a component.
> Another alternative would be to merge it with {{PerCacheInboundInvocationHandler}}... but it doesn't sound too good since it will increase the complexity and size of {{PerCacheInboundInvocationHandler}}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-11800) Convert BackupReceiver to component
by Pedro Ruivo (Jira)
[ https://issues.redhat.com/browse/ISPN-11800?page=com.atlassian.jira.plugi... ]
Pedro Ruivo updated ISPN-11800:
-------------------------------
Affects Version/s: 11.0.0.Dev05
> Convert BackupReceiver to component
> -----------------------------------
>
> Key: ISPN-11800
> URL: https://issues.redhat.com/browse/ISPN-11800
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core, Cross-Site Replication
> Affects Versions: 11.0.0.Dev05
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 11.0.0.CR1
>
>
> The {{BackupReceiver}} instance is created by {{BackupReceiverRepository}} and it needs access to the {{Cache}} instance for its dependencies.
> However, with the latest changes in Cross-Site Replication, it needs to be accessed by commands and the only way to do it is by doing:
> {code:java}
> BackupReceiver backupReceiver = registry.getGlobalComponentRegistry()
> .getComponent(BackupReceiverRepository.class)
> .getBackupReceiver(cache);
> {code}
> Bottom line: tt should be converted to a component.
> Another alternative would be to merge it with {{PerCacheInboundInvocationHandler}}... but it doesn't sound too good since it will increase the complexity and size of {{PerCacheInboundInvocationHandler}}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months