May 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9205) LocalInvalidationSynchronization#afterCompletion calls PutFromLoadValidator#endInvalidatingKey with arguments in incorrect order

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-9205?page=com.atlassian.jira.plugin.... ] Radim Vansa commented on ISPN-9205: ----------------------------------- It does not since it got introduced in HHH-12457 which is not in master yet. > LocalInvalidationSynchronization#afterCompletion calls PutFromLoadValidator#endInvalidatingKey with arguments in incorrect order > -------------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-9205 > URL: https://issues.jboss.org/browse/ISPN-9205 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 9.2.3.Final > Reporter: Gail Badner > Fix For: 9.2.4.Final > > > {{LocalInvalidationSynchronization#afterCompletion}} calls: > {{validator.endInvalidatingKey(key, lockOwner, ...) }} > Instead, it should call: > {{validator.endInvalidatingKey(lockOwner, key, ... }} > I'll create a PR shortly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9183) Replace <eviction> with <memory> in 2LC configs

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9183?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9183: ---------------------------------- Fix Version/s: 9.2.4.Final > Replace <eviction> with <memory> in 2LC configs > ----------------------------------------------- > > Key: ISPN-9183 > URL: https://issues.jboss.org/browse/ISPN-9183 > Project: Infinispan > Issue Type: Task > Components: Hibernate Cache > Affects Versions: 9.3.0.Beta1 > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.3.0.CR1, 9.2.4.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9183) Replace <eviction> with <memory> in 2LC configs

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-9183?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-9183: ------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/5994, https://github.com/infinispan/infinispan/pull/6009 (was: https://github.com/infinispan/infinispan/pull/5994) > Replace <eviction> with <memory> in 2LC configs > ----------------------------------------------- > > Key: ISPN-9183 > URL: https://issues.jboss.org/browse/ISPN-9183 > Project: Infinispan > Issue Type: Task > Components: Hibernate Cache > Affects Versions: 9.3.0.Beta1 > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.3.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9174) Qualify region names in v53.InfinispanRegionFactory

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-9174?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-9174: ------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/5990, https://github.com/infinispan/infinispan/pull/6008 (was: https://github.com/infinispan/infinispan/pull/5990) > Qualify region names in v53.InfinispanRegionFactory > --------------------------------------------------- > > Key: ISPN-9174 > URL: https://issues.jboss.org/browse/ISPN-9174 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 9.2.3.Final, 9.3.0.Beta1 > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.3.0.CR1, 9.2.4.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8799) Limit the default number of shards in the AffinityIndexManager

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8799?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8799: ------------------------------------ Status: Open (was: New) > Limit the default number of shards in the AffinityIndexManager > -------------------------------------------------------------- > > Key: ISPN-8799 > URL: https://issues.jboss.org/browse/ISPN-8799 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.3.0.Final > > > By default this index manager will create as many Lucene indexes as Infinispan segments (256) which will penalize query performance. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9206) Handle long qualified region names more effectively

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-9206?page=com.atlassian.jira.plugin.... ] Radim Vansa commented on ISPN-9206: ----------------------------------- [~sannegrinovero] Are you sure that the list will be equal on all nodes? I can imagine 1) app having two different versions clustered together - at least temporarily during roll out 2) with prefixes one server may have more deployments than the other For debugging purposes I'd keep the last segment of the region name (simple name of the class) - even in production. Why do you need the management operations to expose **full** names? I would consider cache names an implementation detail. IMO the last segment should make it distinguishable enough. We'd need to handle different configuration options a bit differently - right now for specific overrides we use o.h.cache.infinispan.*deployment*#*com.acme.Entity*.cfg - is the deployment really needed there? Isn't the persistence.xml (or spring properties or whatever file you provide) always scoped to the deployment anyway? > Handle long qualified region names more effectively > --------------------------------------------------- > > Key: ISPN-9206 > URL: https://issues.jboss.org/browse/ISPN-9206 > Project: Infinispan > Issue Type: Enhancement > Components: Hibernate Cache > Affects Versions: 9.2.2.Final, 9.3.0.Beta1 > Reporter: Radim Vansa > Assignee: Radim Vansa > > Hibernate region names are FQCNs, and when the prefix is added this can exceed the 255 byte ByteString limit. Also, it's inefficient to ship such long cache names with each command. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9206) Handle long qualified region names more effectively

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-9206?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-9206: --------------------------------------- +1 I suggested a similar idea to Paul during a chat some months back. Hashing would not guarantee lack of collisions, but we can test for any collision with other type names as they are all known upfront, and make adjustments; the important aspect is that the algorithm be deterministic, so to produce the same "name" on all nodes. Since the list of types is well known you could also just sort them, store them in an array, then use the array index as the identifier. We would still want to print full names on management operations though, and when logging we'll probably want to know both the id and the full name. > Handle long qualified region names more effectively > --------------------------------------------------- > > Key: ISPN-9206 > URL: https://issues.jboss.org/browse/ISPN-9206 > Project: Infinispan > Issue Type: Enhancement > Components: Hibernate Cache > Affects Versions: 9.2.2.Final, 9.3.0.Beta1 > Reporter: Radim Vansa > Assignee: Radim Vansa > > Hibernate region names are FQCNs, and when the prefix is added this can exceed the 255 byte ByteString limit. Also, it's inefficient to ship such long cache names with each command. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9206) Handle long qualified region names more effectively

by Radim Vansa (JIRA)

Radim Vansa created ISPN-9206: --------------------------------- Summary: Handle long qualified region names more effectively Key: ISPN-9206 URL: https://issues.jboss.org/browse/ISPN-9206 Project: Infinispan Issue Type: Enhancement Components: Hibernate Cache Affects Versions: 9.3.0.Beta1, 9.2.2.Final Reporter: Radim Vansa Assignee: Radim Vansa Hibernate region names are FQCNs, and when the prefix is added this can exceed the 255 byte ByteString limit. Also, it's inefficient to ship such long cache names with each command. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9205) LocalInvalidationSynchronization#afterCompletion calls PutFromLoadValidator#endInvalidatingKey with arguments in incorrect order

by Gail Badner (JIRA)

[ https://issues.jboss.org/browse/ISPN-9205?page=com.atlassian.jira.plugin.... ] Gail Badner commented on ISPN-9205: ----------------------------------- This does not appear to affect master branch. > LocalInvalidationSynchronization#afterCompletion calls PutFromLoadValidator#endInvalidatingKey with arguments in incorrect order > -------------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-9205 > URL: https://issues.jboss.org/browse/ISPN-9205 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 9.2.3.Final > Reporter: Gail Badner > Fix For: 9.2.4.Final > > > {{LocalInvalidationSynchronization#afterCompletion}} calls: > {{validator.endInvalidatingKey(key, lockOwner, ...) }} > Instead, it should call: > {{validator.endInvalidatingKey(lockOwner, key, ... }} > I'll create a PR shortly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9205) LocalInvalidationSynchronization#afterCompletion calls PutFromLoadValidator#endInvalidatingKey with arguments in incorrect order

by Gail Badner (JIRA)

Gail Badner created ISPN-9205: --------------------------------- Summary: LocalInvalidationSynchronization#afterCompletion calls PutFromLoadValidator#endInvalidatingKey with arguments in incorrect order Key: ISPN-9205 URL: https://issues.jboss.org/browse/ISPN-9205 Project: Infinispan Issue Type: Bug Components: Hibernate Cache Affects Versions: 9.2.3.Final Reporter: Gail Badner Fix For: 9.2.4.Final {{LocalInvalidationSynchronization#afterCompletion}} calls: {{validator.endInvalidatingKey(key, lockOwner, ...) }} Instead, it should call: {{validator.endInvalidatingKey(lockOwner, key, ... }} I'll create a PR shortly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2018