[JBoss JIRA] (ISPN-9106) Cli fails with link error
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-9106?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-9106:
-------------------------------
Sprint: Sprint 9.3.0.Beta1
> Cli fails with link error
> -------------------------
>
> Key: ISPN-9106
> URL: https://issues.jboss.org/browse/ISPN-9106
> Project: Infinispan
> Issue Type: Bug
> Components: CLI, Server
> Affects Versions: 9.3.0.Alpha1
> Reporter: Sebastian Łaskawiec
> Assignee: Ryan Emerson
> Fix For: 9.3.0.Beta1
>
>
> The readiness check returns an error on current master build:
> {code}
> opt/jboss/infinispan-server/bin/ispn-cli.sh -c --controller=172.16.26.143:9990 '/subsystem=datagrid-infinispan/cache-container=clustered/health=HEALTH:read-attribute(name=cluster-health)'
> Failed to link org/jboss/as/patching/cli/PatchCommand (Module "org.jboss.as.patching" version 4.0.0.Final from local module loader @555590 (finder: local module finder @6d1e7682 (roots: /opt/jboss/infinispan-server/modules,/opt/jboss/infinispan-server/modules/system/layers/base))): org/aesh/command/Command
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (ISPN-9106) Cli fails with link error
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-9106?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-9106:
-------------------------------
Summary: Cli fails with link error (was: Readiness probe fails)
> Cli fails with link error
> -------------------------
>
> Key: ISPN-9106
> URL: https://issues.jboss.org/browse/ISPN-9106
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.3.0.Alpha1
> Reporter: Sebastian Łaskawiec
> Assignee: Ryan Emerson
> Fix For: 9.3.0.Beta1
>
>
> The readiness check returns an error on current master build:
> {code}
> opt/jboss/infinispan-server/bin/ispn-cli.sh -c --controller=172.16.26.143:9990 '/subsystem=datagrid-infinispan/cache-container=clustered/health=HEALTH:read-attribute(name=cluster-health)'
> Failed to link org/jboss/as/patching/cli/PatchCommand (Module "org.jboss.as.patching" version 4.0.0.Final from local module loader @555590 (finder: local module finder @6d1e7682 (roots: /opt/jboss/infinispan-server/modules,/opt/jboss/infinispan-server/modules/system/layers/base))): org/aesh/command/Command
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (ISPN-9106) Cli fails with link error
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-9106?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-9106:
-------------------------------
Component/s: CLI
Server
> Cli fails with link error
> -------------------------
>
> Key: ISPN-9106
> URL: https://issues.jboss.org/browse/ISPN-9106
> Project: Infinispan
> Issue Type: Bug
> Components: CLI, Server
> Affects Versions: 9.3.0.Alpha1
> Reporter: Sebastian Łaskawiec
> Assignee: Ryan Emerson
> Fix For: 9.3.0.Beta1
>
>
> The readiness check returns an error on current master build:
> {code}
> opt/jboss/infinispan-server/bin/ispn-cli.sh -c --controller=172.16.26.143:9990 '/subsystem=datagrid-infinispan/cache-container=clustered/health=HEALTH:read-attribute(name=cluster-health)'
> Failed to link org/jboss/as/patching/cli/PatchCommand (Module "org.jboss.as.patching" version 4.0.0.Final from local module loader @555590 (finder: local module finder @6d1e7682 (roots: /opt/jboss/infinispan-server/modules,/opt/jboss/infinispan-server/modules/system/layers/base))): org/aesh/command/Command
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (ISPN-9106) Cli fails with link error
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-9106?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-9106:
-------------------------------
Fix Version/s: 9.3.0.Beta1
> Cli fails with link error
> -------------------------
>
> Key: ISPN-9106
> URL: https://issues.jboss.org/browse/ISPN-9106
> Project: Infinispan
> Issue Type: Bug
> Components: CLI, Server
> Affects Versions: 9.3.0.Alpha1
> Reporter: Sebastian Łaskawiec
> Assignee: Ryan Emerson
> Fix For: 9.3.0.Beta1
>
>
> The readiness check returns an error on current master build:
> {code}
> opt/jboss/infinispan-server/bin/ispn-cli.sh -c --controller=172.16.26.143:9990 '/subsystem=datagrid-infinispan/cache-container=clustered/health=HEALTH:read-attribute(name=cluster-health)'
> Failed to link org/jboss/as/patching/cli/PatchCommand (Module "org.jboss.as.patching" version 4.0.0.Final from local module loader @555590 (finder: local module finder @6d1e7682 (roots: /opt/jboss/infinispan-server/modules,/opt/jboss/infinispan-server/modules/system/layers/base))): org/aesh/command/Command
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (ISPN-8862) Iteration and stream operations with passivation disabled shouldn't use in memory
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-8862?page=com.atlassian.jira.plugin.... ]
Dan Berindei commented on ISPN-8862:
------------------------------------
We could go the other way around and skip the store iteration if there's no eviction. (Not sure if checking that the eviction strategy is none is enough to confirm that there's no automatic or manual eviction, though).
If there is any kind of eviction then we always have to iterate through the store's keys, so maybe we can pass the data container to the store and allow it to decide whether to try and load the value+metadata from the data container if available (e.g. {{SingleFileStore}}) or skip the data container access because reading the value separately is too expensive (e.g. {{JdbcStringBasedStore}}).
> Iteration and stream operations with passivation disabled shouldn't use in memory
> ---------------------------------------------------------------------------------
>
> Key: ISPN-8862
> URL: https://issues.jboss.org/browse/ISPN-8862
> Project: Infinispan
> Issue Type: Enhancement
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 9.3.0.Final
>
>
> When passivation is disabled all entries are assumed to be in the cache loader/store. We currently try to merge these together in a sloppy way [1]. This first reads in memory and then from the store and keeps all keys from in memory to exclude them from the store. Unfortunately the store still has to pull the entries even for the already read keys, but just ignores them. This leads to a lot of inefficiency and memory bloat. Instead we should just return the store entries as is when passivation is disabled.
> [1] https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (ISPN-9009) Add test interrupting conflict resolution
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-9009?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9009:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Add test interrupting conflict resolution
> -----------------------------------------
>
> Key: ISPN-9009
> URL: https://issues.jboss.org/browse/ISPN-9009
> Project: Infinispan
> Issue Type: Task
> Components: Test Suite - Core
> Affects Versions: 9.2.1.Final
> Reporter: Dan Berindei
> Assignee: Ryan Emerson
> Fix For: 9.3.0.Beta1
>
>
> We need a test that starts conflict resolution and then crashes a node or starts another merge, to verify that conflict resolution is properly interrupted or restarted as necessary.
> {{HotRodMergeTest}} was unintentionally testing this by starting the 2nd test before the 1st test's merge finished in all the server caches, but we need something more deterministic in core.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (ISPN-9107) IsolationLevel.READ_COMMITTED does not work as expected
by Tihomir Daskalov (JIRA)
Tihomir Daskalov created ISPN-9107:
--------------------------------------
Summary: IsolationLevel.READ_COMMITTED does not work as expected
Key: ISPN-9107
URL: https://issues.jboss.org/browse/ISPN-9107
Project: Infinispan
Issue Type: Bug
Affects Versions: 9.2.1.Final, 9.0.1.Final
Reporter: Tihomir Daskalov
Attachments: InfinispanTest.java
We use Infinispan in JBoss EAP 7.0.9 as separate module. We use it in TRANSACTIONAL mode with READ_COMMITTED isolation level. After we upgraded Infinispan from 7.2.4 to 9.2.1, we notice that Infinispan does not obey the isolation level. It always behaves as REPEATABLE_READ.
I see a similar issue in ISPN-1340 that is rejected with the argument that REPEATABLE_READ is a stronger isolation level than READ_COMMITTED and thus the later is not really needed.
I see this as a feature loss. Our application has long-running transactions that only read from the cache and short-running transactions that read and write. This bug causes the long-running transactions to not see the changes from the short-running transactions. So, they do not profit from the cache and are slower.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months