[JBoss JIRA] (ISPN-11258) Proto Compatibility check should not fail on unknown OS
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-11258?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-11258:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Proto Compatibility check should not fail on unknown OS
> -------------------------------------------------------
>
> Key: ISPN-11258
> URL: https://issues.redhat.com/browse/ISPN-11258
> Project: Infinispan
> Issue Type: Enhancement
> Components: Build
> Affects Versions: 10.1.1.Final, 11.0.0.Alpha1
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.1.2.Final, 11.0.0.Alpha1
>
>
> Currently the proto schema compatibility check will fail if Infinispan is built on an OS that we do not have a protolock binary for. Instead, we should skip the check and warn the user. This will not affect our protobuf schema compatibility, as the check will still be performed on our CI builds.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
[JBoss JIRA] (ISPN-11272) RecoveryManagerImpl should use Caffeine map
by Will Burns (Jira)
Will Burns created ISPN-11272:
---------------------------------
Summary: RecoveryManagerImpl should use Caffeine map
Key: ISPN-11272
URL: https://issues.redhat.com/browse/ISPN-11272
Project: Infinispan
Issue Type: Sub-task
Components: Core
Reporter: Will Burns
The RecoveryManagerImpl currently allows a user to configure the cache for holding in doubt transactions. The key and value both are not marshallable and thus the cache cannot be clustered or have persistence in any way. We should remove this configuration option and just create a Caffeine map that has lifespan set on the key.
Also the key can just be Xid as long as the RecoveryManager is scoped to a named cache.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
[JBoss JIRA] (ISPN-11272) RecoveryManagerImpl should use Caffeine map
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-11272?page=com.atlassian.jira.plugi... ]
Will Burns updated ISPN-11272:
------------------------------
Parent: (was: ISPN-10309)
Issue Type: Task (was: Sub-task)
> RecoveryManagerImpl should use Caffeine map
> -------------------------------------------
>
> Key: ISPN-11272
> URL: https://issues.redhat.com/browse/ISPN-11272
> Project: Infinispan
> Issue Type: Task
> Components: Core
> Reporter: Will Burns
> Priority: Major
>
> The RecoveryManagerImpl currently allows a user to configure the cache for holding in doubt transactions. The key and value both are not marshallable and thus the cache cannot be clustered or have persistence in any way. We should remove this configuration option and just create a Caffeine map that has lifespan set on the key.
> Also the key can just be Xid as long as the RecoveryManager is scoped to a named cache.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
[JBoss JIRA] (ISPN-11272) RecoveryManagerImpl should use Caffeine map
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-11272?page=com.atlassian.jira.plugi... ]
Will Burns commented on ISPN-11272:
-----------------------------------
This was found when we found a call to Cache#put which can block under certain configurations.
> RecoveryManagerImpl should use Caffeine map
> -------------------------------------------
>
> Key: ISPN-11272
> URL: https://issues.redhat.com/browse/ISPN-11272
> Project: Infinispan
> Issue Type: Task
> Components: Core
> Reporter: Will Burns
> Priority: Major
>
> The RecoveryManagerImpl currently allows a user to configure the cache for holding in doubt transactions. The key and value both are not marshallable and thus the cache cannot be clustered or have persistence in any way. We should remove this configuration option and just create a Caffeine map that has lifespan set on the key.
> Also the key can just be Xid as long as the RecoveryManager is scoped to a named cache.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months