[JBoss JIRA] (ISPN-8454) Off Heap can crash when using JMH test
by William Burns (JIRA)
William Burns created ISPN-8454:
-----------------------------------
Summary: Off Heap can crash when using JMH test
Key: ISPN-8454
URL: https://issues.jboss.org/browse/ISPN-8454
Project: Infinispan
Issue Type: Bug
Components: Off Heap
Reporter: William Burns
Assignee: William Burns
Fix For: 9.2.0.Beta1
I have a jmh branch from our benchmarks that always can crash off heap when not using tracing. For whatever reason I can't seem to reliably produce it with tracing. This JIRA is to handle this issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (ISPN-8453) Commit should fail if cache is in degraded mode
by Dan Berindei (JIRA)
Dan Berindei created ISPN-8453:
----------------------------------
Summary: Commit should fail if cache is in degraded mode
Key: ISPN-8453
URL: https://issues.jboss.org/browse/ISPN-8453
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 9.2.0.Alpha2, 9.1.2.Final, 8.2.8.Final, 8.1.9.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 9.2.0.Beta1
When the originator receives a {{CacheNotFoundResponse}} and the cache is in degraded mode, the transaction is marked as partially completed, but the commit completes successfully.
I believe that is not correct, because the originator could crash after the commit but before the merge, and in that case the transaction will not be applied on all the owners. The transaction manager will ignore any commit exception in {{NON_XA}}/{{useSynchronization}} mode, but at least in {{FULL_XA}}/{{NON_DURABLE_XA}} mode we can signal to the user that the transaction may be lost.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (ISPN-8453) Commit should fail if cache is in degraded mode
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-8453?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-8453:
-------------------------------
Status: Open (was: New)
> Commit should fail if cache is in degraded mode
> -----------------------------------------------
>
> Key: ISPN-8453
> URL: https://issues.jboss.org/browse/ISPN-8453
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 8.1.9.Final, 8.2.8.Final, 9.1.2.Final, 9.2.0.Alpha2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 9.2.0.Beta1
>
>
> When the originator receives a {{CacheNotFoundResponse}} and the cache is in degraded mode, the transaction is marked as partially completed, but the commit completes successfully.
> I believe that is not correct, because the originator could crash after the commit but before the merge, and in that case the transaction will not be applied on all the owners. The transaction manager will ignore any commit exception in {{NON_XA}}/{{useSynchronization}} mode, but at least in {{FULL_XA}}/{{NON_DURABLE_XA}} mode we can signal to the user that the transaction may be lost.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (ISPN-8409) Change off heap eviction to store everything in same allocated memory block
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-8409?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-8409:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Change off heap eviction to store everything in same allocated memory block
> ---------------------------------------------------------------------------
>
> Key: ISPN-8409
> URL: https://issues.jboss.org/browse/ISPN-8409
> Project: Infinispan
> Issue Type: Sub-task
> Components: Off Heap
> Affects Versions: 9.2.0.Alpha1
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 9.2.0.Beta1
>
>
> When eviction is enabled with off heap, we currently allocate an additional 28 byte lru node for every entry. We can instead include the lru information in the entry allocation, by changing slightly when memory is freed. This will allow for more entries to be inserted when eviction is enabled, and possibly additional performance.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (ISPN-8452) KUBE_PING doesn't work with JDG 7.2 OpenShift image
by Sebastian Łaskawiec (JIRA)
Sebastian Łaskawiec created ISPN-8452:
-----------------------------------------
Summary: KUBE_PING doesn't work with JDG 7.2 OpenShift image
Key: ISPN-8452
URL: https://issues.jboss.org/browse/ISPN-8452
Project: Infinispan
Issue Type: Bug
Components: Cloud Integrations
Reporter: Sebastian Łaskawiec
Assignee: Ryan Emerson
It seems that KUBE_PING doesn't work with the latest version of JDG 7.2 OpenShift image. The reason for this is that JDG 7.2 is shipped with upstream KUBE_PING which conflicts with the one provided in the openshift layer.
The easiest solution is to revert layer ordering {{layers.conf}} file:
{code}
echo "layers=base,openshift" > /opt/datagrid/modules/layers.conf
{code}
This solution has additional advantage - we can fallback to previous KUBE_PING version (the one provided by the CE Team) by just changing this small line.
However if the upstream KUBE_PING works fine and we are happy with it, we should remove the old version from the server. I think that's a solution we should take for JDG 8 or maybe sooner - 7.3.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months