[JBoss JIRA] (ISPN-9699) Cluster member owning no data
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9699?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9699:
----------------------------------
Fix Version/s: 9.4.4.Final
(was: 9.4.3.Final)
> Cluster member owning no data
> -----------------------------
>
> Key: ISPN-9699
> URL: https://issues.jboss.org/browse/ISPN-9699
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 9.4.1.Final
> Reporter: Thomas Segismont
> Assignee: Katia Aresti
> Priority: Major
> Fix For: 10.0.0.Alpha2, 9.4.4.Final
>
>
> Currently, you can set {{capacity-factor}} to zero on a cache if you don't want a node to own any segment.
> If you want a node to own no data at all, you could set this property on all declared caches. But this wouldn't work for internal caches anyway (locks, counters).
> It would be nice to have a global switch.
> This would be useful when your app needs to be a cluster member for discovery/membership but is deployed mostly for processing. Indeed, when such nodes are added/removed from the cluster:
> * there would be no data loss
> * the cluster would be back in healthy state faster as no data would be moved around.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (ISPN-9677) Non-transactional queries don't update the query cache
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9677?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9677:
----------------------------------
Fix Version/s: 9.4.4.Final
(was: 9.4.3.Final)
> Non-transactional queries don't update the query cache
> ------------------------------------------------------
>
> Key: ISPN-9677
> URL: https://issues.jboss.org/browse/ISPN-9677
> Project: Infinispan
> Issue Type: Bug
> Components: Hibernate Cache
> Affects Versions: 9.4.1.Final
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Priority: Major
> Fix For: 10.0.0.Alpha1, 9.4.4.Final
>
>
> This is affecting the Hibernate second-level cache simple tutorials where queries are executed outside transactions.
> The problem is that the new integration for the query results (result of ISPN-9075) does not verify if there's an on-going transaction before registering a transaction completed synchronization where the query cache is updated.
> As a result, when a non-transactional query happens, the transaction synchronization callback does not happen and the query cache is not updated.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (ISPN-9764) Server should utilise the Persistence element
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9764?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9764:
----------------------------------
Fix Version/s: 9.4.4.Final
(was: 9.4.3.Final)
> Server should utilise the Persistence element
> ---------------------------------------------
>
> Key: ISPN-9764
> URL: https://issues.jboss.org/browse/ISPN-9764
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 9.4.2.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Alpha2, 9.4.4.Final
>
>
> Currently the <persistence> element is not required to configure stores in the server. We need to add this, so that we can configure PersistenceManager characteristics such as store-availability etc. Furthermore, with the current config it's possible for two store configs to cancel out each other's passivation behaviour if one has passivation=true and passivation=false.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (ISPN-9778) XidImpl implementations can optimize some byte[] allocations
by William Burns (Jira)
[ https://issues.jboss.org/browse/ISPN-9778?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-9778:
--------------------------------
Description:
The EmbeddedXid and XidImpl classes show up on profiler for allocating byte[] in a local environment.
1. We should be able to remove the branch byte[] completely as well as its accompanying AtomicInteger and just return an empty byte[] that is cached (ie. Util.EMPTY_BYTE_ARRAY).
2. We can use the byte[] that is provided from the create method directly in XidImpl, which would reduce our allocation to just the 1 byte\[24\] for embedded or byte\[32\] for remote.
-3. We can return the byte[] directly for getGlobalTransactionId without copying.-
was:
The EmbeddedXid and XidImpl classes show up on profiler for allocating byte[] in a local environment.
1. We should be able to remove the branch byte[] completely as well as its accompanying AtomicInteger and just return an empty byte[] that is cached (ie. Util.EMPTY_BYTE_ARRAY).
2. We can use the byte[] that is provided from the create method directly in XidImpl, which would reduce our allocation to just the 1 byte[24] for embedded or byte[32] for remote.
3. We can return the byte[] directly for getGlobalTransactionId without copying.
> XidImpl implementations can optimize some byte[] allocations
> ------------------------------------------------------------
>
> Key: ISPN-9778
> URL: https://issues.jboss.org/browse/ISPN-9778
> Project: Infinispan
> Issue Type: Bug
> Components: Transactions
> Reporter: William Burns
> Priority: Major
> Fix For: 10.0.0.Alpha2
>
>
> The EmbeddedXid and XidImpl classes show up on profiler for allocating byte[] in a local environment.
> 1. We should be able to remove the branch byte[] completely as well as its accompanying AtomicInteger and just return an empty byte[] that is cached (ie. Util.EMPTY_BYTE_ARRAY).
> 2. We can use the byte[] that is provided from the create method directly in XidImpl, which would reduce our allocation to just the 1 byte\[24\] for embedded or byte\[32\] for remote.
> -3. We can return the byte[] directly for getGlobalTransactionId without copying.-
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (ISPN-9778) XidImpl implementations can optimize some byte[] allocations
by William Burns (Jira)
William Burns created ISPN-9778:
-----------------------------------
Summary: XidImpl implementations can optimize some byte[] allocations
Key: ISPN-9778
URL: https://issues.jboss.org/browse/ISPN-9778
Project: Infinispan
Issue Type: Bug
Components: Transactions
Reporter: William Burns
Fix For: 10.0.0.Alpha2
The EmbeddedXid and XidImpl classes show up on profiler for allocating byte[] in a local environment.
1. We should be able to remove the branch byte[] completely as well as its accompanying AtomicInteger and just return an empty byte[] that is cached (ie. Util.EMPTY_BYTE_ARRAY).
2. We can use the byte[] that is provided from the create method directly in XidImpl, which would reduce our allocation to just the 1 byte[24] for embedded or byte[32] for remote.
3. We can return the byte[] directly for getGlobalTransactionId without copying.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (ISPN-9777) Default AdvancedCacheLoader#publishEntries can hang with more than 2048 entries
by William Burns (Jira)
William Burns created ISPN-9777:
-----------------------------------
Summary: Default AdvancedCacheLoader#publishEntries can hang with more than 2048 entries
Key: ISPN-9777
URL: https://issues.jboss.org/browse/ISPN-9777
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 9.3.0.Final
Reporter: William Burns
Assignee: William Burns
Fix For: 10.0.0.Alpha2
The default method for AdvancedCacheLoader#publishEntries relies on the invocation of the process method. This uses the PersistenceManagerCloseableSupplier to handle this. Unfortunately it uses a WithinThreadExecutor, which actually can cause the process method to deadlock with a single thread as it can fill up the queue of 2048 elements.
We should instead use a single threaded executor which would allow the loading of elements and retrieval in parallel on 2 different threads.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months