[JBoss JIRA] (ISPN-9390) DefaultConflictManager throws exception during merge conflicts resolution
by M S (JIRA)
[ https://issues.jboss.org/browse/ISPN-9390?page=com.atlassian.jira.plugin.... ]
M S commented on ISPN-9390:
---------------------------
I assigned our internal ticket for retest with trace logs, so hopefully you'll get it soon (if we successfully reproduce it)
> DefaultConflictManager throws exception during merge conflicts resolution
> -------------------------------------------------------------------------
>
> Key: ISPN-9390
> URL: https://issues.jboss.org/browse/ISPN-9390
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.3.0.Final
> Reporter: M S
> Attachments: 15nodes-merge-issue.zip
>
>
> In one of our environments where we have 15 nodes in cloud we got to the point where following issue occurs on one of the nodes - node22 (Cache zones encountered exception whilst trying to resolve conflicts on merge: java.util.concurrent.CompletionException: org.infinispan.commons.CacheException).
> We reproduced it while having 15 nodes in cloud, and then unplugging and plugging one node - node11 back.
> I'm attaching infinispan logs (WARN level set) from the failed controllers and our cluster config. [^15nodes-merge-issue.zip]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (ISPN-9392) Create store JMH benchmark
by William Burns (JIRA)
William Burns created ISPN-9392:
-----------------------------------
Summary: Create store JMH benchmark
Key: ISPN-9392
URL: https://issues.jboss.org/browse/ISPN-9392
Project: Infinispan
Issue Type: Task
Components: Loaders and Stores
Reporter: William Burns
We should add a JMH benchmark to isolate performance of the various stores.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (ISPN-8241) Refactor RocksDB clearThreshold
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-8241?page=com.atlassian.jira.plugin.... ]
William Burns commented on ISPN-8241:
-------------------------------------
It should be noted that this horrendously slow if there aren't that many entries in the database (in comparison to just invoking delete). We may however need to compact the files after deletes maybe?
> Refactor RocksDB clearThreshold
> -------------------------------
>
> Key: ISPN-8241
> URL: https://issues.jboss.org/browse/ISPN-8241
> Project: Infinispan
> Issue Type: Sub-task
> Components: Loaders and Stores
> Affects Versions: 9.1.0.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Fix For: 9.4.0.Final
>
>
> Currently the RocksDB store utilises a "clearThreshold" to try to delete entries individually before deleting and re-initiating the database. We should deprecate this threshold and always delete/reinit the database.
> Currently when deleting the database, we utilise Util.recursiveFileRemove which does not confirm that the file has actually been deleted. Instead, we should provide a nio based implementation instead, similar to the one stated [here|https://stackoverflow.com/questions/779519/delete-directories-recurs...]. This has the advantage that an IOException is thrown by java.nio.file.Files::delete
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (ISPN-9390) DefaultConflictManager throws exception during merge conflicts resolution
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-9390?page=com.atlassian.jira.plugin.... ]
Ryan Emerson commented on ISPN-9390:
------------------------------------
[~staho] Would it be possible for you to provide DEBUG or TRACE logs? With WARN logs it is very difficult to diagnose what's going on.
> DefaultConflictManager throws exception during merge conflicts resolution
> -------------------------------------------------------------------------
>
> Key: ISPN-9390
> URL: https://issues.jboss.org/browse/ISPN-9390
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.3.0.Final
> Reporter: M S
> Attachments: 15nodes-merge-issue.zip
>
>
> In one of our environments where we have 15 nodes in cloud we got to the point where following issue occurs on one of the nodes - node22 (Cache zones encountered exception whilst trying to resolve conflicts on merge: java.util.concurrent.CompletionException: org.infinispan.commons.CacheException).
> We reproduced it while having 15 nodes in cloud, and then unplugging and plugging one node - node11 back.
> I'm attaching infinispan logs (WARN level set) from the failed controllers and our cluster config. [^15nodes-merge-issue.zip]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (ISPN-8213) Functional commands are not replayed in tx on non-read owner
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-8213?page=com.atlassian.jira.plugin.... ]
Radim Vansa updated ISPN-8213:
------------------------------
Fix Version/s: 9.4.0.Final
> Functional commands are not replayed in tx on non-read owner
> ------------------------------------------------------------
>
> Key: ISPN-8213
> URL: https://issues.jboss.org/browse/ISPN-8213
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.1.0.Final
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Fix For: 9.4.0.Final
>
>
> When a functional command is executed on a node that is rebalancing and is not a read owner, we don't fetch the value (it does not end up in context's looked-up entries) but execute the command remotely in a read-only way.
> The entry should be later written on this node, too, but EWI tries to commit only looked-up entries.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (ISPN-9391) Infinispan-Server stop working (hang) after hot rod remote command clean
by Michael Sausmikat (JIRA)
Michael Sausmikat created ISPN-9391:
---------------------------------------
Summary: Infinispan-Server stop working (hang) after hot rod remote command clean
Key: ISPN-9391
URL: https://issues.jboss.org/browse/ISPN-9391
Project: Infinispan
Issue Type: Bug
Components: Hot Rod
Affects Versions: 9.3.1.Final
Environment: Infinispan Server Server 9.3.1.Final with 10 local caches
Wildfly Server 10.1.0.Final with our business logic (writer to caches with HotRod)
Many JavaFX-Client (reader to caches HotRod) with cache listeners
Reporter: Michael Sausmikat
After some time (2days) the Hot-Rod-Server hang.
The session beans (Wildfly) get SocketTimeOutExceptions when the won't to write to the cache
Normally one cache ist dead without hot rod eventing and with locks>0.
The ThreadDump shows many threads waiting for ClientEvent dispatching.
It is not possible to shutdown the infinispan server (Only kill helps).
After some research we found the following thread
https://developer.jboss.org/thread/269005
We have the same problem and change the queue size in the class
org.infinispan.server.hotrod.ClientListenerRegistry (line 304)
to 100000
I don't understand why the queue is blocking?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (ISPN-9390) DefaultConflictManager throws exception during merge conflicts resolution
by M S (JIRA)
[ https://issues.jboss.org/browse/ISPN-9390?page=com.atlassian.jira.plugin.... ]
M S commented on ISPN-9390:
---------------------------
The issue has been discussed with [~ryanemerson] in the discussion of [#https://issues.jboss.org/browse/ISPN-9014] and it was proposed to open the new one.
> DefaultConflictManager throws exception during merge conflicts resolution
> -------------------------------------------------------------------------
>
> Key: ISPN-9390
> URL: https://issues.jboss.org/browse/ISPN-9390
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.3.0.Final
> Reporter: M S
> Attachments: 15nodes-merge-issue.zip
>
>
> In one of our environments where we have 15 nodes in cloud we got to the point where following issue occurs on one of the nodes - node22 (Cache zones encountered exception whilst trying to resolve conflicts on merge: java.util.concurrent.CompletionException: org.infinispan.commons.CacheException).
> We reproduced it while having 15 nodes in cloud, and then unplugging and plugging one node - node11 back.
> I'm attaching infinispan logs (WARN level set) from the failed controllers and our cluster config. [^15nodes-merge-issue.zip]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months