[JBoss JIRA] (ISPN-4196) Local transaction not removed from transaction table with keySet, entrySet, values operations
by Martin Gencur (JIRA)
[ https://issues.jboss.org/browse/ISPN-4196?page=com.atlassian.jira.plugin.... ]
Martin Gencur updated ISPN-4196:
--------------------------------
Description: The cleanup phase of FilesystemQueryDslIterationTest of this test is based on Cache.clear() and is very slow , taking about 30 seconds, or at least that's how much we gain if the cache cleanup is removed. Without the cleanup, this test takes about 2.5 seconds, so we need to investigate why Cache.clear() creates a problem here or in general. (was: The cleanup phase of this test is based on Cache.clear() and is very slow , taking about 30 seconds, or at least that's how much we gain if the cache cleanup is removed. Without the cleanup, this test takes about 2.5 seconds, so we need to investigate why Cache.clear() creates a problem here or in general.)
> Local transaction not removed from transaction table with keySet, entrySet, values operations
> ---------------------------------------------------------------------------------------------
>
> Key: ISPN-4196
> URL: https://issues.jboss.org/browse/ISPN-4196
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 7.0.0.Alpha1
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 7.0.0.Final
>
>
> The cleanup phase of FilesystemQueryDslIterationTest of this test is based on Cache.clear() and is very slow , taking about 30 seconds, or at least that's how much we gain if the cache cleanup is removed. Without the cleanup, this test takes about 2.5 seconds, so we need to investigate why Cache.clear() creates a problem here or in general.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 12 months
[JBoss JIRA] (ISPN-4196) Local transaction not removed from transaction table with keySet, entrySet, values operations
by Martin Gencur (JIRA)
[ https://issues.jboss.org/browse/ISPN-4196?page=com.atlassian.jira.plugin.... ]
Martin Gencur updated ISPN-4196:
--------------------------------
Summary: Local transaction not removed from transaction table with keySet, entrySet, values operations (was: QueryDslIterationTest cleanup takes 30 secods to complete)
> Local transaction not removed from transaction table with keySet, entrySet, values operations
> ---------------------------------------------------------------------------------------------
>
> Key: ISPN-4196
> URL: https://issues.jboss.org/browse/ISPN-4196
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 7.0.0.Alpha1
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 7.0.0.Final
>
>
> The cleanup phase of this test is based on Cache.clear() and is very slow , taking about 30 seconds, or at least that's how much we gain if the cache cleanup is removed. Without the cleanup, this test takes about 2.5 seconds, so we need to investigate why Cache.clear() creates a problem here or in general.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 12 months
[JBoss JIRA] (ISPN-4196) QueryDslIterationTest cleanup takes 30 secods to complete
by Martin Gencur (JIRA)
[ https://issues.jboss.org/browse/ISPN-4196?page=com.atlassian.jira.plugin.... ]
Martin Gencur commented on ISPN-4196:
-------------------------------------
So I think the root cause is the following: The clear() operation internally uses _cluster_registry_cache and calls keySet on it. keySet operation creates an invocation context and creates a new local transaction which is added to localTransactions variable for the respective cache. However, the keySet operation is not enlisted in the transaction and so when the transaction commits, the local transaction is not removed from the list. This happens through transaction manager that removes all transactions which have been enlisted in the transaction. Trying to find solution...
> QueryDslIterationTest cleanup takes 30 secods to complete
> ---------------------------------------------------------
>
> Key: ISPN-4196
> URL: https://issues.jboss.org/browse/ISPN-4196
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 7.0.0.Alpha1
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 7.0.0.Final
>
>
> The cleanup phase of this test is based on Cache.clear() and is very slow , taking about 30 seconds, or at least that's how much we gain if the cache cleanup is removed. Without the cleanup, this test takes about 2.5 seconds, so we need to investigate why Cache.clear() creates a problem here or in general.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 12 months
[JBoss JIRA] (ISPN-3533) Design HotRod protocol version 2.0
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-3533?page=com.atlassian.jira.plugin.... ]
Radim Vansa commented on ISPN-3533:
-----------------------------------
Currently, HotRod client sets the protocol version and expects the server to understand it. Wouldn't it be better to include some negotiation: client connect with "I support 2.0, 2.1 and 2.2", server responds "I support 2.0 and 2.1", and then client knows he should use 2.1 instead of 2.2?
Also, have you considered rather versioned "extensions" (such as querying, transactions, streaming, listeners...) to basic protocol than simple versions extending the previous one? Or is this overengineering?
> Design HotRod protocol version 2.0
> ----------------------------------
>
> Key: ISPN-3533
> URL: https://issues.jboss.org/browse/ISPN-3533
> Project: Infinispan
> Issue Type: Enhancement
> Components: Remote Protocols
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
>
> Umbrella JIRA for Hot Rod improvements for version 2.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 12 months
[JBoss JIRA] (ISPN-4196) QueryDslIterationTest cleanup takes 30 secods to complete
by Martin Gencur (JIRA)
[ https://issues.jboss.org/browse/ISPN-4196?page=com.atlassian.jira.plugin.... ]
Martin Gencur commented on ISPN-4196:
-------------------------------------
After some debugging, the problems seems to be in the QueryInterceptor which handles clearing the index.
The 30-second waiting period is caused by ComponentRegistry calling stop() operation on TransactionTable. This stop() method waits for localTransactions variable to be empty (not containing any LocalTransactions). This is fine for default cache on which the clear() was initially invoked. However, during the clear() operation, another "_cluster_registry_cache_" is used by QueryInterceptor (it creates and registers a new local transaction for the _cluster_registry_cache_) and at the time of calling stop() method on its TransactionTable, the transaction is still there. This transaction should have been removed from the localTransactions variable but was not. I'll investigate further what can be done about this.
> QueryDslIterationTest cleanup takes 30 secods to complete
> ---------------------------------------------------------
>
> Key: ISPN-4196
> URL: https://issues.jboss.org/browse/ISPN-4196
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 7.0.0.Alpha1
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 7.0.0.Final
>
>
> The cleanup phase of this test is based on Cache.clear() and is very slow , taking about 30 seconds, or at least that's how much we gain if the cache cleanup is removed. Without the cleanup, this test takes about 2.5 seconds, so we need to investigate why Cache.clear() creates a problem here or in general.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 12 months
[JBoss JIRA] (ISPN-4192) Adding a clustered in a local cache fails with NullPointerException
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-4192?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-4192:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 7.0.0.Alpha4
(was: 7.0.0.Alpha3)
Resolution: Done
> Adding a clustered in a local cache fails with NullPointerException
> -------------------------------------------------------------------
>
> Key: ISPN-4192
> URL: https://issues.jboss.org/browse/ISPN-4192
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 7.0.0.Alpha2
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: 7.0.0.Alpha4
>
>
> members is null
> {code}
> Caused by: java.lang.NullPointerException
> at org.infinispan.notifications.cachelistener.CacheNotifierImpl.addedListener(CacheNotifierImpl.java:594)
> at org.infinispan.notifications.impl.AbstractListenerImpl.validateAndAddListenerInvocation(AbstractListenerImpl.java:154)
> at org.infinispan.notifications.cachelistener.CacheNotifierImpl.addListener(CacheNotifierImpl.java:578)
> at org.infinispan.cache.impl.CacheImpl.addListener(CacheImpl.java:560)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 12 months
[JBoss JIRA] (ISPN-4192) Adding a clustered in a local cache fails with NullPointerException
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-4192?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-4192:
-----------------------------------
Fix Version/s: 7.0.0.Alpha3
(was: 7.0.0.Alpha4)
> Adding a clustered in a local cache fails with NullPointerException
> -------------------------------------------------------------------
>
> Key: ISPN-4192
> URL: https://issues.jboss.org/browse/ISPN-4192
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 7.0.0.Alpha2
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: 7.0.0.Alpha3
>
>
> members is null
> {code}
> Caused by: java.lang.NullPointerException
> at org.infinispan.notifications.cachelistener.CacheNotifierImpl.addedListener(CacheNotifierImpl.java:594)
> at org.infinispan.notifications.impl.AbstractListenerImpl.validateAndAddListenerInvocation(AbstractListenerImpl.java:154)
> at org.infinispan.notifications.cachelistener.CacheNotifierImpl.addListener(CacheNotifierImpl.java:578)
> at org.infinispan.cache.impl.CacheImpl.addListener(CacheImpl.java:560)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 12 months