[JBoss JIRA] (ISPN-9343) Streams should skip loader when preload=true and eviction is not enabled
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-9343?page=com.atlassian.jira.plugin.... ]
William Burns commented on ISPN-9343:
-------------------------------------
Both of these deal with optimizations when preload=true and eviction is disabled.
> Streams should skip loader when preload=true and eviction is not enabled
> ------------------------------------------------------------------------
>
> Key: ISPN-9343
> URL: https://issues.jboss.org/browse/ISPN-9343
> Project: Infinispan
> Issue Type: Enhancement
> Affects Versions: 9.3.0.Final
> Reporter: William Burns
>
> Currently stream operations and other bulk operations always read from the loader to ensure they don't miss any entries. However when a cache is configured to have preload=true and eviction is not enabled we should be able to ignore the loader and use in memory only. This would improve the performance of streams substantially in these cases.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (ISPN-9345) TimeutException involving the org.infinispan.CONFIG cache
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/ISPN-9345?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on ISPN-9345:
--------------------------------
Both views and discovery responses are shipped in the body of a message, *not* in the header. However, since both GMS and the discovery/merge protocol are typically below FRAG2, if you want to precise, you'd have to add a second FRAG2 just below the discovery layer.
The reason for placing the FRAG2 protocol towards the top ensures that credit requests are never greater than X bytes, so {{frag_size}} is always less than the max credits, preventing that a huge credit requests is blocked forever.
> TimeutException involving the org.infinispan.CONFIG cache
> ---------------------------------------------------------
>
> Key: ISPN-9345
> URL: https://issues.jboss.org/browse/ISPN-9345
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.3.0.Final
> Reporter: Gustavo Fernandes
> Assignee: Dan Berindei
>
> {noformat}
> Caused by: org.infinispan.commons.CacheException: Initial state transfer timed out for cache org.infinispan.CONFIG on jedha-64980
> at org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete(StateTransferManagerImpl.java:233)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.infinispan.commons.util.SecurityActions.lambda$invokeAccessibly$0(SecurityActions.java:79)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (ISPN-9345) TimeutException involving the org.infinispan.CONFIG cache
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-9345?page=com.atlassian.jira.plugin.... ]
Dan Berindei commented on ISPN-9345:
------------------------------------
[~belaban] what about view updates and discovery responses?
> TimeutException involving the org.infinispan.CONFIG cache
> ---------------------------------------------------------
>
> Key: ISPN-9345
> URL: https://issues.jboss.org/browse/ISPN-9345
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.3.0.Final
> Reporter: Gustavo Fernandes
> Assignee: Dan Berindei
>
> {noformat}
> Caused by: org.infinispan.commons.CacheException: Initial state transfer timed out for cache org.infinispan.CONFIG on jedha-64980
> at org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete(StateTransferManagerImpl.java:233)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.infinispan.commons.util.SecurityActions.lambda$invokeAccessibly$0(SecurityActions.java:79)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (ISPN-6873) Upgrade asciidoctor-maven-plugin to 1.5.4 (once it's released)
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/ISPN-6873?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec reassigned ISPN-6873:
-----------------------------------------
Assignee: Tristan Tarrant (was: Sebastian Łaskawiec)
> Upgrade asciidoctor-maven-plugin to 1.5.4 (once it's released)
> --------------------------------------------------------------
>
> Key: ISPN-6873
> URL: https://issues.jboss.org/browse/ISPN-6873
> Project: Infinispan
> Issue Type: Component Upgrade
> Components: Build
> Affects Versions: 9.0.0.Alpha3
> Environment: * Windows :)
> Reporter: Sebastian Łaskawiec
> Assignee: Tristan Tarrant
> Priority: Minor
>
> Currently our Windows build fails on [generating documentation|http://ci.infinispan.org/viewLog.html?tab=buildLog&logTab=t...]:
> {code}
> Failed to execute goal org.asciidoctor:asciidoctor-maven-plugin:1.5.3:process-asciidoc (pdf) on project infinispan-docs: Execution pdf of goal org.asciidoctor:asciidoctor-maven-plugin:1.5.3:process-asciidoc failed: (Errno::ENOENT) C:/BuildAgent/system/jetbrains.maven.runner/maven.repo.local-bt59/org/asciidoctor/asciidoctorj-pdf/1.5.0-alpha.11/asciidoctorj-pdf-1.5.0-alpha.11.jar!C:/gems/addressable-2.4.0/data/unicode.data
> [03:43:13]##teamcity[projectFinished tc:tags='tc:internal' projectId='org.infinispan:infinispan-docs:jar:9.0.0-SNAPSHOT']
> {code}
> This is a knows issue of asciidoctor-maven-plugin (see [here|https://github.com/asciidoctor/asciidoctorj/issues/416]).
> I temporarily disabled building distribution during Windows build (it should be re-enabled after this issue is fixed).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months