[JBoss JIRA] (ISPN-7239) Protect writes to cache store from topology change
by Pedro Ruivo (JIRA)
Pedro Ruivo created ISPN-7239:
---------------------------------
Summary: Protect writes to cache store from topology change
Key: ISPN-7239
URL: https://issues.jboss.org/browse/ISPN-7239
Project: Infinispan
Issue Type: Bug
Components: Core
Reporter: Pedro Ruivo
Assignee: Pedro Ruivo
In current implementation, the cache-store is updated without protection from topology change. The ownership is checked before, but the topology can change between the check and the actual write.
It can be problematic for shared cache store where only the primary owner must perform the write.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months
[JBoss JIRA] (ISPN-7238) Reduce number of CompletableFuture allocations during async invocation
by Dan Berindei (JIRA)
Dan Berindei created ISPN-7238:
----------------------------------
Summary: Reduce number of CompletableFuture allocations during async invocation
Key: ISPN-7238
URL: https://issues.jboss.org/browse/ISPN-7238
Project: Infinispan
Issue Type: Task
Components: Core
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 9.0.0.Beta1
The current asynchronous invocations allocate a new {{CompletableFuture}} instance (plus a {{UniHandle}}, and a {{ComposedAsyncInvocationStage}}) for every interceptor that calls {{compose()}} or the other {{InvocationState}} methods that add a callback.
We can reduce this by having a list of handlers in each invocation stage, and only creating a new {{CompletableFuture}} when we need to change the {{command}}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months
[JBoss JIRA] (ISPN-2955) Async marshalling executor retry when queue fills
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-2955?page=com.atlassian.jira.plugin.... ]
Dan Berindei resolved ISPN-2955.
--------------------------------
Fix Version/s: 8.0.0.Final
Resolution: Out of Date
Async marshalling was removed with ISPN-2939.
> Async marshalling executor retry when queue fills
> -------------------------------------------------
>
> Key: ISPN-2955
> URL: https://issues.jboss.org/browse/ISPN-2955
> Project: Infinispan
> Issue Type: Enhancement
> Components: Marshalling
> Affects Versions: 5.2.5.Final
> Reporter: Manik Surtani
> Fix For: 8.0.0.Final
>
>
> When using an async transport and async marshalling, an executor is used to process the marshalling task in a separate thread and the caller's thread is allowed to return immediately.
> When the executor's queue fills and the queue cannot accept any more tasks, it throws a {{RejectedExecutionException}}, causing a very bad user/developer experience. A more correct approach to this is to catch the {{RejectedExecutionException}}, block and retry the task submission.
> The end result is that, in the degenerate case (when the executor queue is full) instead of throwing exceptions, those invocations will perform slightly slower.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months
[JBoss JIRA] (ISPN-6776) Administration console - push state transfer and cancel state transfer buttons don't work properly
by Roman Macor (JIRA)
[ https://issues.jboss.org/browse/ISPN-6776?page=com.atlassian.jira.plugin.... ]
Roman Macor commented on ISPN-6776:
-----------------------------------
[~vblagojevic] ah, I've mistaken this with [JIRA|https://issues.jboss.org/browse/ISPN-7236]. This one is from June, that's why the configuration was no longer working :) anyway I've updated the configuration files. I can't retest this until ISPN-7236 is resolved.
> Administration console - push state transfer and cancel state transfer buttons don't work properly
> --------------------------------------------------------------------------------------------------
>
> Key: ISPN-6776
> URL: https://issues.jboss.org/browse/ISPN-6776
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
> Attachments: domain.xml, host.xml
>
>
> Click on cache container -> Actions -> Manage backup sites -> Push state (on BRN site which is configured)
> result: nothing happens, server log:
> [Server:server-one] 15:15:03,752 ERROR [org.jgroups.protocols.relay.RELAY2] (ServerService Thread Pool -- 36) master:server-one: no route to BRN: dropping message
> expected result: Success! The operation has been successfully executed.
> Please note that if we take the site offline and then online again in the "Manage backup sites" dialog, push state button works correctly.
> Cancel state button is behaving the same, except taking site offline and then online again doesn't help.
> I'm attaching server configuration
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months
[JBoss JIRA] (ISPN-6776) Administration console - push state transfer and cancel state transfer buttons don't work properly
by Roman Macor (JIRA)
[ https://issues.jboss.org/browse/ISPN-6776?page=com.atlassian.jira.plugin.... ]
Roman Macor edited comment on ISPN-6776 at 11/25/16 9:42 AM:
-------------------------------------------------------------
[~vblagojevic] ah, I've mistaken this with [ISPN-7236|https://issues.jboss.org/browse/ISPN-7236]. This one is from June, that's why the configuration was no longer working :) anyway I've updated the configuration files. I can't retest this until ISPN-7236 is resolved.
was (Author: rmacor):
[~vblagojevic] ah, I've mistaken this with [JIRA|https://issues.jboss.org/browse/ISPN-7236]. This one is from June, that's why the configuration was no longer working :) anyway I've updated the configuration files. I can't retest this until ISPN-7236 is resolved.
> Administration console - push state transfer and cancel state transfer buttons don't work properly
> --------------------------------------------------------------------------------------------------
>
> Key: ISPN-6776
> URL: https://issues.jboss.org/browse/ISPN-6776
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
> Attachments: domain.xml, host.xml
>
>
> Click on cache container -> Actions -> Manage backup sites -> Push state (on BRN site which is configured)
> result: nothing happens, server log:
> [Server:server-one] 15:15:03,752 ERROR [org.jgroups.protocols.relay.RELAY2] (ServerService Thread Pool -- 36) master:server-one: no route to BRN: dropping message
> expected result: Success! The operation has been successfully executed.
> Please note that if we take the site offline and then online again in the "Manage backup sites" dialog, push state button works correctly.
> Cancel state button is behaving the same, except taking site offline and then online again doesn't help.
> I'm attaching server configuration
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months
[JBoss JIRA] (ISPN-6742) Console shows cache available and disabled at the same time
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-6742?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic commented on ISPN-6742:
-------------------------------------------
Good point [~rmacor] I'll make that adjustment to PR and we can integrate it! Thanks
> Console shows cache available and disabled at the same time
> -----------------------------------------------------------
>
> Key: ISPN-6742
> URL: https://issues.jboss.org/browse/ISPN-6742
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 8.2.2.Final
> Reporter: Jiří Holuša
> Assignee: Vladimir Blagojevic
> Fix For: 9.0.0.Alpha3
>
> Attachments: attachment.png
>
>
> Page: go to cache detail and click "Actions" -> "Disable".
> After confirmation, the cache status is still "Available", but new red box appears with text "Disabled", see the attachment. This doesn't seem to me very intuitive, if the cache is disabled, it should be IMO unavailable and this should be also reflected in the caches list.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months
[JBoss JIRA] (ISPN-6776) Administration console - push state transfer and cancel state transfer buttons don't work properly
by Roman Macor (JIRA)
[ https://issues.jboss.org/browse/ISPN-6776?page=com.atlassian.jira.plugin.... ]
Roman Macor updated ISPN-6776:
------------------------------
Attachment: domain.xml
host.xml
> Administration console - push state transfer and cancel state transfer buttons don't work properly
> --------------------------------------------------------------------------------------------------
>
> Key: ISPN-6776
> URL: https://issues.jboss.org/browse/ISPN-6776
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
> Attachments: domain.xml, host.xml
>
>
> Click on cache container -> Actions -> Manage backup sites -> Push state (on BRN site which is configured)
> result: nothing happens, server log:
> [Server:server-one] 15:15:03,752 ERROR [org.jgroups.protocols.relay.RELAY2] (ServerService Thread Pool -- 36) master:server-one: no route to BRN: dropping message
> expected result: Success! The operation has been successfully executed.
> Please note that if we take the site offline and then online again in the "Manage backup sites" dialog, push state button works correctly.
> Cancel state button is behaving the same, except taking site offline and then online again doesn't help.
> I'm attaching server configuration
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months
[JBoss JIRA] (ISPN-6776) Administration console - push state transfer and cancel state transfer buttons don't work properly
by Roman Macor (JIRA)
[ https://issues.jboss.org/browse/ISPN-6776?page=com.atlassian.jira.plugin.... ]
Roman Macor updated ISPN-6776:
------------------------------
Attachment: (was: host.xml)
> Administration console - push state transfer and cancel state transfer buttons don't work properly
> --------------------------------------------------------------------------------------------------
>
> Key: ISPN-6776
> URL: https://issues.jboss.org/browse/ISPN-6776
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
>
> Click on cache container -> Actions -> Manage backup sites -> Push state (on BRN site which is configured)
> result: nothing happens, server log:
> [Server:server-one] 15:15:03,752 ERROR [org.jgroups.protocols.relay.RELAY2] (ServerService Thread Pool -- 36) master:server-one: no route to BRN: dropping message
> expected result: Success! The operation has been successfully executed.
> Please note that if we take the site offline and then online again in the "Manage backup sites" dialog, push state button works correctly.
> Cancel state button is behaving the same, except taking site offline and then online again doesn't help.
> I'm attaching server configuration
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months