[JBoss JIRA] (ISPN-5368) Out of order events produced when using the MassIndexer with async backend
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5368?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5368:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1208162|https://bugzilla.redhat.com/show_bug.cgi?id=1208162] from VERIFIED to CLOSED
> Out of order events produced when using the MassIndexer with async backend
> --------------------------------------------------------------------------
>
> Key: ISPN-5368
> URL: https://issues.jboss.org/browse/ISPN-5368
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 7.2.0.Beta2, 7.1.1.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Fix For: 7.2.0.CR1, 7.2.0.Final
>
>
> When using async indexing backend on DIST caches with shared index (InfinispanIndexManager), the MassIndexer fails to re-index all the entries, if it is run from a node that is not
> the indexing master.
> Normally the operation sequence of the MassIndexer in the above configuration, for a two node cluster is:
> * Purge the index
> * Send index job to node A and to node B
> * Flush
> Given the backend is async, all index commands are sent to the master RPC-wise asynchronously, and so a reorder can occur and produce like:
> * Send index job to node A
> * Purge
> * Send index job to node B
> * Flush
> Causing previously re-indexed entries to be wiped
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (ISPN-5252) Override toString() of org.infinispan.registry.ScopedKey
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5252?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5252:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1203565|https://bugzilla.redhat.com/show_bug.cgi?id=1203565] from VERIFIED to CLOSED
> Override toString() of org.infinispan.registry.ScopedKey
> --------------------------------------------------------
>
> Key: ISPN-5252
> URL: https://issues.jboss.org/browse/ISPN-5252
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 7.2.0.Alpha1, 7.1.1.Final
> Reporter: Osamu Nagano
> Assignee: Osamu Nagano
> Fix For: 7.2.0.Beta2, 7.2.0.Final
>
>
> A lock request timed out and the target key was dumped, but it was default {{toString()}} output of {{ScopedKey}}. This is unfriendly to developer. The wrapped original key should be dumped.
> {noformat}
> Caused by: org.infinispan.util.concurrent.TimeoutException: Unable to acquire lock after [10 seconds] on key [org.infinispan.registry.ScopedKey@5b6f425] for requestor [GlobalTransaction:<AAA>:1568:remote]! Lock held by [GlobalTransaction:<BBB>:1271:local]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months