[JBoss JIRA] (ISPN-12328) Deadlock when querying
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-12328?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-12328:
-------------------------------------
Description:
I noticed the deadlock (stack trace attached) when querying a single node with 50 threads (10ms interval between the queries, no writes while querying).
It appears I need to configure a thread pool size to workaround this? [~dan.berindei] [~rpwburns]
was:
I noticed the deadlock (stack trace attached) when querying a single node with 50 threads (10ms interval between the queries, no writes while querying).
It appears I need to configure any thread pool size to workaround this? [~dan.berindei] [~rpwburns]
> Deadlock when querying
> ----------------------
>
> Key: ISPN-12328
> URL: https://issues.redhat.com/browse/ISPN-12328
> Project: Infinispan
> Issue Type: Enhancement
> Affects Versions: 11.0.3.Final
> Reporter: Gustavo Fernandes
> Priority: Major
> Attachments: dump.zip
>
>
> I noticed the deadlock (stack trace attached) when querying a single node with 50 threads (10ms interval between the queries, no writes while querying).
> It appears I need to configure a thread pool size to workaround this? [~dan.berindei] [~rpwburns]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months
[JBoss JIRA] (ISPN-12328) Deadlock when querying
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-12328?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-12328:
-------------------------------------
Description:
I noticed the deadlock (stack trace attached) when querying a single node with 50 threads (10ms interval between the queries, no writes while querying).
It appears I need to configure any thread pool size to workaround this? [~dan.berindei] [~rpwburns]
was:
I noticed the deadlock (stack trace attached) when querying a single node with 50 threads (10ms interval between the queries).
It appears I need to configure any thread pool size to workaround this? [~dan.berindei] [~rpwburns]
> Deadlock when querying
> ----------------------
>
> Key: ISPN-12328
> URL: https://issues.redhat.com/browse/ISPN-12328
> Project: Infinispan
> Issue Type: Enhancement
> Affects Versions: 11.0.3.Final
> Reporter: Gustavo Fernandes
> Priority: Major
> Attachments: dump.zip
>
>
> I noticed the deadlock (stack trace attached) when querying a single node with 50 threads (10ms interval between the queries, no writes while querying).
> It appears I need to configure any thread pool size to workaround this? [~dan.berindei] [~rpwburns]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months
[JBoss JIRA] (ISPN-12328) Deadlock when querying
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-12328?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-12328:
-------------------------------------
Description:
I noticed the deadlock (stack trace attached) when querying a single node with 50 threads (10ms interval between the queries).
It appears I need to configure any thread pool size to workaround this? [~dan.berindei] [~rpwburns]
was:
I noticed the deadlock (stack trace attached) when querying a single node with 50 queries (10ms interval between the queries).
It appears I need to configure any thread pool size to workaround this? [~dan.berindei] [~rpwburns]
> Deadlock when querying
> ----------------------
>
> Key: ISPN-12328
> URL: https://issues.redhat.com/browse/ISPN-12328
> Project: Infinispan
> Issue Type: Enhancement
> Affects Versions: 11.0.3.Final
> Reporter: Gustavo Fernandes
> Priority: Major
> Attachments: dump.zip
>
>
> I noticed the deadlock (stack trace attached) when querying a single node with 50 threads (10ms interval between the queries).
> It appears I need to configure any thread pool size to workaround this? [~dan.berindei] [~rpwburns]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months
[JBoss JIRA] (ISPN-12328) Deadlock when querying
by Gustavo Fernandes (Jira)
Gustavo Fernandes created ISPN-12328:
----------------------------------------
Summary: Deadlock when querying
Key: ISPN-12328
URL: https://issues.redhat.com/browse/ISPN-12328
Project: Infinispan
Issue Type: Enhancement
Affects Versions: 11.0.3.Final
Reporter: Gustavo Fernandes
I noticed the deadlock (stack trace attached) when querying a single node with 50 queries (10ms interval between the queries).
It appears I need to configure any thread pool size to workaround this? [~dan.berindei] [~rpwburns]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months
[JBoss JIRA] (ISPN-12318) Query.maxResult() ignored during entity loading
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-12318?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-12318:
-------------------------------------
Description:
When a query has a maxResult it should not try to load/collect/read/hidrate all hits but rather restrict it to the requested page size. This causes unnecessary allocations of Strings and byte[]. In particular, the {{KeyTransformationHandler#stringToKey}} method produces a large amount of garbage.
was:
When a query has a maxResult it should not try to load/collect/read/hidrate all hits but rather restrict it to the requested page size. This causes unnecessary allocations of Strings and byte[]. In particular, the {{KeyTransformationHandler#stringToKey}} method produces a large amount of garbage.
Other issue is the default maxResult is not defined consistently: it is 10 for queries over REST and undefined for embedded and queries over Hot Rod.
> Query.maxResult() ignored during entity loading
> -----------------------------------------------
>
> Key: ISPN-12318
> URL: https://issues.redhat.com/browse/ISPN-12318
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 12.0.0.Dev03
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Critical
>
> When a query has a maxResult it should not try to load/collect/read/hidrate all hits but rather restrict it to the requested page size. This causes unnecessary allocations of Strings and byte[]. In particular, the {{KeyTransformationHandler#stringToKey}} method produces a large amount of garbage.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months
[JBoss JIRA] (ISPN-12327) Limit query results by default
by Gustavo Fernandes (Jira)
Gustavo Fernandes created ISPN-12327:
----------------------------------------
Summary: Limit query results by default
Key: ISPN-12327
URL: https://issues.redhat.com/browse/ISPN-12327
Project: Infinispan
Issue Type: Enhancement
Components: Embedded Querying
Affects Versions: 12.0.0.Dev03
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
Queries over REST have maxResults to 10 by default. We should extend this behaviour to queries over Hot Rod and embedded for consistency and performance reasons.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months
[JBoss JIRA] (ISPN-12309) Creating cache with invalid configuration leaves inconsistent state
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-12309?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-12309:
-------------------------------------
Description:
When a cache is created using the EmbeddedCacheManagerAdmin with an invalid configuration, it will throw an error but will persist the cache nonetheless.
Further operations involving cache manager can throw exceptions, for example, Health.getHealth()
was:
When a cache is created using the EmbeddedCacheManagerAdmin with an invalid configuration, it will throw an error but will persist the cache nonetheless.
Further operations involving cache manager will throw exceptions.
> Creating cache with invalid configuration leaves inconsistent state
> -------------------------------------------------------------------
>
> Key: ISPN-12309
> URL: https://issues.redhat.com/browse/ISPN-12309
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Reporter: Katia Aresti
> Assignee: Gustavo Fernandes
> Priority: Major
>
> When a cache is created using the EmbeddedCacheManagerAdmin with an invalid configuration, it will throw an error but will persist the cache nonetheless.
> Further operations involving cache manager can throw exceptions, for example, Health.getHealth()
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months
[JBoss JIRA] (ISPN-12309) Creating cache with invalid configuration leaves inconsistent state
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-12309?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-12309:
-------------------------------------
Description:
When a cache is created using the EmbeddedCacheManagerAdmin with an invalid configuration, it will throw an error but will persist the cache nonetheless.
Further operations involving cache manager will throw exceptions.
was:
When a cache is created using the EmbeddedCacheManagerAdmin with an invalid configuration, it will throw an error but will persist the cache nonetheless.
Further operations involving cache manager will throw exceptions since.
> Creating cache with invalid configuration leaves inconsistent state
> -------------------------------------------------------------------
>
> Key: ISPN-12309
> URL: https://issues.redhat.com/browse/ISPN-12309
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Reporter: Katia Aresti
> Assignee: Gustavo Fernandes
> Priority: Major
>
> When a cache is created using the EmbeddedCacheManagerAdmin with an invalid configuration, it will throw an error but will persist the cache nonetheless.
> Further operations involving cache manager will throw exceptions.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months