[JBoss JIRA] (ISPN-8893) Stack trace of a primary request of Infinispan is lost, damaging supportability severely
by Yeray Borges (JIRA)
[ https://issues.jboss.org/browse/ISPN-8893?page=com.atlassian.jira.plugin.... ]
Yeray Borges updated ISPN-8893:
-------------------------------
Git Pull Request: https://github.com/infinispan/infinispan/pull/5815
> Stack trace of a primary request of Infinispan is lost, damaging supportability severely
> ----------------------------------------------------------------------------------------
>
> Key: ISPN-8893
> URL: https://issues.jboss.org/browse/ISPN-8893
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Reporter: Yeray Borges
> Assignee: Yeray Borges
> Labels: top-50-list
>
> A request is handled by XNIO's "default task-NNN" thread. If the request executes a clustering cache operation, like session replication, it waits for the backup operation on another server. And if the other server failed on the backup operation, the primary server unwraps the exception to print only the remote exception. The original context of thread "default task-NNN" is lost and a user can't even identify what the primary operation was.
> This affects supportability too much. It seems only JDG 7.1 is free from this issue (it has {{AsyncInterceptorChain}}). All other releases like EAP 7.1, RHSSO which is based on EAP 7.0 has this issue.
> See the "Forum Reference" link of a mail thread for the detail.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (ISPN-8912) SoftIndexFileStore does not fail gracefully if max node size exceeds 32777
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-8912?page=com.atlassian.jira.plugin.... ]
Radim Vansa updated ISPN-8912:
------------------------------
Summary: SoftIndexFileStore does not fail gracefully if max node size exceeds 32777 (was: The SoftIndexFileStore runs into a deadlock at startup if more than ~20000 values have been stored and max node size is > 32777 bytes)
> SoftIndexFileStore does not fail gracefully if max node size exceeds 32777
> --------------------------------------------------------------------------
>
> Key: ISPN-8912
> URL: https://issues.jboss.org/browse/ISPN-8912
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 9.1.6.Final
> Reporter: Andreas Pabst
> Assignee: Radim Vansa
>
> The following unit test just puts lots of entries into the cache and restarts the cache repeatedly.
> It succeeds if maxNodeSize is set to anything up to 32777, but runs into a deadlock from 32778 upwards. If going even higher it doesn't run into a deadlock anymore, but throws an IllegalArgumentException instead.
> As a workaround one can delete the index. But the problem resurfaces after the next restart.
> {code:java}
> import java.util.concurrent.TimeUnit;
> import java.util.stream.IntStream;
> import org.infinispan.Cache;
> import org.infinispan.configuration.cache.Configuration;
> import org.infinispan.configuration.cache.ConfigurationBuilder;
> import org.infinispan.manager.DefaultCacheManager;
> import org.infinispan.manager.EmbeddedCacheManager;
> import org.infinispan.persistence.sifs.configuration.SoftIndexFileStoreConfigurationBuilder;
> import org.junit.After;
> import org.junit.Before;
> import org.junit.Rule;
> import org.junit.Test;
> import org.junit.rules.Timeout;
> public class SifsLargeNodeTest {
> private EmbeddedCacheManager cacheManager;
> @Rule
> public Timeout timeout = new Timeout(15, TimeUnit.SECONDS);
> private static Configuration createConfig(String location, int maxNodeSizeInBytes) {
> return new ConfigurationBuilder()
> .persistence().addStore(SoftIndexFileStoreConfigurationBuilder.class)
> .dataLocation(location + "/data").indexLocation(location + "/index")
> .maxNodeSize(maxNodeSizeInBytes)
> .preload(false).purgeOnStartup(false)
> .build();
> }
> @Before
> public void setUp() {
> cacheManager = new DefaultCacheManager();
> }
> @After
> public void tearDown() {
> cacheManager.stop();
> }
> @Test
> public void testLoad() {
> int maxNodeSizeInBytes = 32780; // Note: Anything up to 32777 works fine
> String cacheName = "sifslargenodetestcache";
> Configuration cfg = createConfig(cacheName, maxNodeSizeInBytes);
> int numberOfRuns = 10;
> int valuesToPutPerRun = 10000;
> for (int run = 0; run < numberOfRuns; run++) {
> System.out.println("RUN " + run);
> cacheManager.defineConfiguration(cacheName, cfg);
> Cache<Integer, String> testCacheBeforeReduction = cacheManager.getCache(cacheName);
> IntStream.range(run * valuesToPutPerRun, (run + 1) * valuesToPutPerRun)
> .forEach(i -> testCacheBeforeReduction.put(i, Integer.toString(i)));
> cacheManager.stop();
> cacheManager = new DefaultCacheManager();
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (ISPN-8912) The SoftIndexFileStore runs into a deadlock at startup if more than ~20000 values have been stored and max node size is > 32777 bytes
by Andreas Pabst (JIRA)
[ https://issues.jboss.org/browse/ISPN-8912?page=com.atlassian.jira.plugin.... ]
Andreas Pabst commented on ISPN-8912:
-------------------------------------
Thank you for clarifying. Do you want me to edit the title so it reflects that the actual issue is the missing range check for the maxNodeSize configuration value?
> The SoftIndexFileStore runs into a deadlock at startup if more than ~20000 values have been stored and max node size is > 32777 bytes
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-8912
> URL: https://issues.jboss.org/browse/ISPN-8912
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 9.1.6.Final
> Reporter: Andreas Pabst
> Assignee: Radim Vansa
>
> The following unit test just puts lots of entries into the cache and restarts the cache repeatedly.
> It succeeds if maxNodeSize is set to anything up to 32777, but runs into a deadlock from 32778 upwards. If going even higher it doesn't run into a deadlock anymore, but throws an IllegalArgumentException instead.
> As a workaround one can delete the index. But the problem resurfaces after the next restart.
> {code:java}
> import java.util.concurrent.TimeUnit;
> import java.util.stream.IntStream;
> import org.infinispan.Cache;
> import org.infinispan.configuration.cache.Configuration;
> import org.infinispan.configuration.cache.ConfigurationBuilder;
> import org.infinispan.manager.DefaultCacheManager;
> import org.infinispan.manager.EmbeddedCacheManager;
> import org.infinispan.persistence.sifs.configuration.SoftIndexFileStoreConfigurationBuilder;
> import org.junit.After;
> import org.junit.Before;
> import org.junit.Rule;
> import org.junit.Test;
> import org.junit.rules.Timeout;
> public class SifsLargeNodeTest {
> private EmbeddedCacheManager cacheManager;
> @Rule
> public Timeout timeout = new Timeout(15, TimeUnit.SECONDS);
> private static Configuration createConfig(String location, int maxNodeSizeInBytes) {
> return new ConfigurationBuilder()
> .persistence().addStore(SoftIndexFileStoreConfigurationBuilder.class)
> .dataLocation(location + "/data").indexLocation(location + "/index")
> .maxNodeSize(maxNodeSizeInBytes)
> .preload(false).purgeOnStartup(false)
> .build();
> }
> @Before
> public void setUp() {
> cacheManager = new DefaultCacheManager();
> }
> @After
> public void tearDown() {
> cacheManager.stop();
> }
> @Test
> public void testLoad() {
> int maxNodeSizeInBytes = 32780; // Note: Anything up to 32777 works fine
> String cacheName = "sifslargenodetestcache";
> Configuration cfg = createConfig(cacheName, maxNodeSizeInBytes);
> int numberOfRuns = 10;
> int valuesToPutPerRun = 10000;
> for (int run = 0; run < numberOfRuns; run++) {
> System.out.println("RUN " + run);
> cacheManager.defineConfiguration(cacheName, cfg);
> Cache<Integer, String> testCacheBeforeReduction = cacheManager.getCache(cacheName);
> IntStream.range(run * valuesToPutPerRun, (run + 1) * valuesToPutPerRun)
> .forEach(i -> testCacheBeforeReduction.put(i, Integer.toString(i)));
> cacheManager.stop();
> cacheManager = new DefaultCacheManager();
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (ISPN-8908) Remote cache fails to get entries when state transfer is turned off
by Vojtech Juranek (JIRA)
[ https://issues.jboss.org/browse/ISPN-8908?page=com.atlassian.jira.plugin.... ]
Vojtech Juranek updated ISPN-8908:
----------------------------------
Description:
When state transfer is turned off, remote cache fails to obtain cache entries from HR server (in client-server mode) which connects to the cluster. Only about half of the entries can be seen by HR client on newly connected server, both in replicated cache and distributed cache.
It's not specific to CS mode, same problem is also in embedded mode.
was:
When state transfer is turned off, remote cache fails to obtain cache entries from HR server (in client-server mode) which connects to the cluster. Only about half of the entries can be seen by HR client on newly connected server, both in replicated cache and distributed cache.
Investigate it in embedded mode is TBD.
> Remote cache fails to get entries when state transfer is turned off
> -------------------------------------------------------------------
>
> Key: ISPN-8908
> URL: https://issues.jboss.org/browse/ISPN-8908
> Project: Infinispan
> Issue Type: Bug
> Components: State Transfer
> Affects Versions: 9.2.0.Final
> Reporter: Vojtech Juranek
>
> When state transfer is turned off, remote cache fails to obtain cache entries from HR server (in client-server mode) which connects to the cluster. Only about half of the entries can be seen by HR client on newly connected server, both in replicated cache and distributed cache.
> It's not specific to CS mode, same problem is also in embedded mode.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months