[JBoss JIRA] (ISPN-4692) Optimize externalizer for FileListCacheValue
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4692?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4692:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1166028|https://bugzilla.redhat.com/show_bug.cgi?id=1166028] from MODIFIED to ON_QA
> Optimize externalizer for FileListCacheValue
> --------------------------------------------
>
> Key: ISPN-4692
> URL: https://issues.jboss.org/browse/ISPN-4692
> Project: Infinispan
> Issue Type: Enhancement
> Components: Lucene Directory
> Reporter: Sanne Grinovero
> Assignee: Gustavo Fernandes
> Fix For: 7.0.0.CR1
>
>
> There are two possible improvements to be applied to the Externalizer strategy applied by FileListCacheValue.
> - Each String is being encoded (and decoded) in UTF8 format, which is expensive. We should explore alternative encodings to String - at least for the wire format.
> - This is an ideal case for Delta operations: on each modification just one entry of the map is added / removed, but the whole HashMap is being transferred at each write.
> I'm not sure how we can combine the Delta interface with custom Externalizers, so that will need to be explored.
> We might want to avoid storing it as a value and resort to custom RPC commands to transfer the needed bits only, but we don't want to reimplement state transfer and CacheStore storage.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-4975) Cross site state transfer - status of push gets stuck at "SENDING" after being cancelled
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4975?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4975:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1163337|https://bugzilla.redhat.com/show_bug.cgi?id=1163337] from MODIFIED to ON_QA
> Cross site state transfer - status of push gets stuck at "SENDING" after being cancelled
> ----------------------------------------------------------------------------------------
>
> Key: ISPN-4975
> URL: https://issues.jboss.org/browse/ISPN-4975
> Project: Infinispan
> Issue Type: Bug
> Components: State Transfer
> Affects Versions: 7.0.0.Final
> Reporter: Matej Čimbora
> Assignee: Pedro Ruivo
> Fix For: 7.1.0.Alpha1
>
>
> After invoking: site --cancelpush backupSite on the producer site, status of the push operation seems to get stuck at "SENDING" value (tested by site --pushstatus), even if state transfer is not currently in progress.
> Invoking site --cancelreceive mainSite on the consumer site works correctly. New invocation of site --push backupsite leads to "X-Site state transfer to '%s' already started!" being displayed. The issue seems to be caused by XSiteStateTransferManagerImpl.siteCollector not being cleared.
> Used configuration:
> distributed caches, site A: 2 nodes, site B: 3 nodes, B is a backup for A.
> Scenario
> - Start A,B
> - Take B offline using takeSiteOffline
> - Load data into A
> - Push state into B
> - CancelPushState B
> -- PushStateStatus remains stuck at SENDING & new push is not possible
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-4975) Cross site state transfer - status of push gets stuck at "SENDING" after being cancelled
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4975?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4975:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1163337|https://bugzilla.redhat.com/show_bug.cgi?id=1163337] from POST to MODIFIED
> Cross site state transfer - status of push gets stuck at "SENDING" after being cancelled
> ----------------------------------------------------------------------------------------
>
> Key: ISPN-4975
> URL: https://issues.jboss.org/browse/ISPN-4975
> Project: Infinispan
> Issue Type: Bug
> Components: State Transfer
> Affects Versions: 7.0.0.Final
> Reporter: Matej Čimbora
> Assignee: Pedro Ruivo
> Fix For: 7.1.0.Alpha1
>
>
> After invoking: site --cancelpush backupSite on the producer site, status of the push operation seems to get stuck at "SENDING" value (tested by site --pushstatus), even if state transfer is not currently in progress.
> Invoking site --cancelreceive mainSite on the consumer site works correctly. New invocation of site --push backupsite leads to "X-Site state transfer to '%s' already started!" being displayed. The issue seems to be caused by XSiteStateTransferManagerImpl.siteCollector not being cleared.
> Used configuration:
> distributed caches, site A: 2 nodes, site B: 3 nodes, B is a backup for A.
> Scenario
> - Start A,B
> - Take B offline using takeSiteOffline
> - Load data into A
> - Push state into B
> - CancelPushState B
> -- PushStateStatus remains stuck at SENDING & new push is not possible
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-4433) Can not run INFINISPAN testsuite with JDK8
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4433?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4433:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1084904|https://bugzilla.redhat.com/show_bug.cgi?id=1084904] from POST to MODIFIED
> Can not run INFINISPAN testsuite with JDK8
> -------------------------------------------
>
> Key: ISPN-4433
> URL: https://issues.jboss.org/browse/ISPN-4433
> Project: Infinispan
> Issue Type: Bug
> Components: Build process
> Affects Versions: 7.0.0.Alpha4
> Reporter: Vitalii Chepeliuk
> Assignee: Mircea Markus
> Fix For: 7.0.0.Alpha5
>
>
> {noformat}
> [ERROR] Failed to execute goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check (default) on project infinispan-cachestore-jdbc: Execution default of goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check failed. IllegalArgumentException -> [Help 1]
> [ERROR] Failed to execute goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check (default) on project infinispan-lucene-v3: Execution default of goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check failed. IllegalArgumentException -> [Help 1]
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack (unpack) on project infinispan-lucene-directory: Artifact has not been packaged yet. When used on reactor artifact, unpack should be executed after packaging: see MDEP-98. -> [Help 2]
> [ERROR] Failed to execute goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check (default) on project infinispan-query: Execution default of goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check failed. IllegalArgumentException -> [Help 1]
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project infinispan-tools: Compilation failure: Compilation failure:
> [ERROR] /mnt/hudson_workspace/workspace/edg-60-ispn-testsuite-rhel/89fa96e5/infinispan/tools/src/main/java/org/infinispan/tools/doclet/jmx/JmxDoclet.java:[67,32] cannot find symbol
> [ERROR] symbol: method getInstance()
> [ERROR] location: class com.sun.tools.doclets.formats.html.ConfigurationImpl
> [ERROR] /mnt/hudson_workspace/workspace/edg-60-ispn-testsuite-rhel/89fa96e5/infinispan/tools/src/main/java/org/infinispan/tools/doclet/jmx/JmxDoclet.java:[80,32] cannot find symbol
> [ERROR] symbol: method getInstance()
> [ERROR] location: class com.sun.tools.doclets.formats.html.ConfigurationImpl
> [ERROR] -> [Help 3]
> {noformat}
> Look on last Jenkins run with JDK8
> * RHEL5
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e...
> * RHEL6
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e...
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-4979) CacheStatusResponse map uses too much memory
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4979?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4979:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1163573|https://bugzilla.redhat.com/show_bug.cgi?id=1163573] from POST to MODIFIED
> CacheStatusResponse map uses too much memory
> --------------------------------------------
>
> Key: ISPN-4979
> URL: https://issues.jboss.org/browse/ISPN-4979
> Project: Infinispan
> Issue Type: Bug
> Components: Core, State Transfer
> Affects Versions: 7.0.0.Final
> Reporter: Dan Berindei
> Assignee: William Burns
> Priority: Critical
> Fix For: 7.1.0.Alpha1, 7.1.0.Final
>
>
> When the cluster is large and there are a log of caches, the {{CacheStatusResponse}} map on the new coordinator can get quite large. One of the problems that seems to be that the addresses in {{DefaultConsistentHash}} are duplicated on serialization, so the deserialized version occupies more memory.
> We need to investigate why the objects are not "shared" by the River marshaller, and maybe work around the problem by de-duplicating the addresses in the externalizer.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-5019) After coordinator change, cache topologies should be installed in parallel
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5019?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5019:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1163573|https://bugzilla.redhat.com/show_bug.cgi?id=1163573] from POST to MODIFIED
> After coordinator change, cache topologies should be installed in parallel
> --------------------------------------------------------------------------
>
> Key: ISPN-5019
> URL: https://issues.jboss.org/browse/ISPN-5019
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 7.0.2.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Critical
> Fix For: 7.1.0.Beta1
>
>
> When the coordinator crashes, the new coordinator has to recover the cache topologies from all the nodes in the cluster and install updated topologies for all the caches. This is done on a single thread, and it can take a long time when there are a lot of caches.
> We should be accelerate this by doing the topology installation on separate threads. However, we have to be careful with the async transport pool, because {{executeOnClusterAsync}} actually needs to spawn a new thread in the same pool.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months