[JBoss JIRA] (ISPN-11297) Rejoining nodes with global state may have their caches corrupted if there is a config mismatch
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11297?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11297:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/7865
> Rejoining nodes with global state may have their caches corrupted if there is a config mismatch
> -----------------------------------------------------------------------------------------------
>
> Key: ISPN-11297
> URL: https://issues.redhat.com/browse/ISPN-11297
> Project: Infinispan
> Issue Type: Bug
> Components: Configuration, Core
> Affects Versions: 10.1.1.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Critical
> Fix For: 11.0.0.Beta1
>
>
> With a persistent global state enabled, when a node that was previously part of a cluster rejoins it currently processes caches from the cluster state before the ones from the local state. This means that, if the cache configuration is incompatible, it will be overwritten with the one coming from the cluster.
> When joining the node should perform compatibility checks between caches in the cluster state and the local state before proceeding with creating them. If a mismatch is found, it should fail fast.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-11314) Local non-blocking get breaks hit/miss statistics
by Dan Berindei (Jira)
Dan Berindei created ISPN-11314:
-----------------------------------
Summary: Local non-blocking get breaks hit/miss statistics
Key: ISPN-11314
URL: https://issues.redhat.com/browse/ISPN-11314
Project: Infinispan
Issue Type: Bug
Components: Hot Rod, Server
Affects Versions: 9.4.17.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 9.4.18.Final
The local-non-blocking get was breaking the hit/miss statistics
when client requests didn't go to the primary owner,
e.g. with a load balancer between the clients and the servers.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-7744) ServerEventLoggerTest.testLocalServerEventLogging fails intermittently
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-7744?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-7744:
----------------------------------
Fix Version/s: 11.0.0.Beta1
(was: 11.0.0.Alpha1)
> ServerEventLoggerTest.testLocalServerEventLogging fails intermittently
> ----------------------------------------------------------------------
>
> Key: ISPN-7744
> URL: https://issues.redhat.com/browse/ISPN-7744
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 9.0.0.Final
> Reporter: Tristan Tarrant
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.Beta1
>
>
> I got org.infinispan.server.eventlogger.ServerEventLoggerTest.testLocalServerEventLogging fail on Windows with following stacktrace:
> {code}
> java.lang.AssertionError: expected:<2> but was:<1>
> at org.testng.AssertJUnit.fail(AssertJUnit.java:59)
> at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:245)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:252)
> at org.infinispan.server.eventlogger.ServerEventLoggerTest$1.call(ServerEventLoggerTest.java:60)
> at org.infinispan.test.TestingUtil.withCacheManager(TestingUtil.java:1296)
> at org.infinispan.server.eventlogger.ServerEventLoggerTest.testLocalServerEventLogging(ServerEventLoggerTest.java:43)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-11205) DataSource support in the Server
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11205?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11205:
-----------------------------------
Fix Version/s: 11.0.0.Beta1
(was: 11.0.0.Alpha1)
> DataSource support in the Server
> --------------------------------
>
> Key: ISPN-11205
> URL: https://issues.redhat.com/browse/ISPN-11205
> Project: Infinispan
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 10.1.1.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 11.0.0.Beta1, 11.0.0.Final
>
>
> The server needs to have the ability to manage datasources/connection pools to databases so that they can be shared by multiple cache stores/loaders.
> We should use Agroal for this.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-11292) Add in (non)blocking thread pools
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11292?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11292:
-----------------------------------
Fix Version/s: 11.0.0.Beta1
(was: 11.0.0.Alpha1)
> Add in (non)blocking thread pools
> ---------------------------------
>
> Key: ISPN-11292
> URL: https://issues.redhat.com/browse/ISPN-11292
> Project: Infinispan
> Issue Type: Sub-task
> Components: Core
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
> Fix For: 11.0.0.Beta1
>
>
> We should remove the ASYNC_OPERATIONS_EXECUTOR and PERSISTENCE_EXECUTOR components and replace them with a NON_BLOCKING_EXECUTOR and BLOCKING_EXECUTOR or something similarly named.
> We should probably default the NON_BLOCKING_EXECUTOR to 2 * numCPU and blocking to 100? The queue size should be a bit bigger for blocking as compared to non blocking. The parser should allow these to be changed as other executors are currently.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-11248) Add test for ServerTask that utilizes protostream stored entries
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11248?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11248:
-----------------------------------
Fix Version/s: 11.0.0.Beta1
(was: 11.0.0.Alpha1)
> Add test for ServerTask that utilizes protostream stored entries
> ----------------------------------------------------------------
>
> Key: ISPN-11248
> URL: https://issues.redhat.com/browse/ISPN-11248
> Project: Infinispan
> Issue Type: Task
> Reporter: Will Burns
> Priority: Major
> Fix For: 11.0.0.Beta1
>
>
> We currently have a single ServerTask that just prints out "Hello <name>". We should add a new test that actually tests a very likely use case of storing entries in protostream and using a task that deserializes them properly (this could be done automatically by the encoding layer of the cache, if it is working).
> We may also want to look into sharing this with a custom loader, as we have users doing this today. And it is quite clunky, so we can see how the usability is in 11.0.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month