March 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11463) Cache manager stats are mistakenly exported as MP metrics even when stats disabled

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11463?page=com.atlassian.jira.plugi... ] Nistor Adrian commented on ISPN-11463: -------------------------------------- This is merged in master but 10.1.x is still waiting > Cache manager stats are mistakenly exported as MP metrics even when stats disabled > ---------------------------------------------------------------------------------- > > Key: ISPN-11463 > URL: https://issues.redhat.com/browse/ISPN-11463 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 11.0.0.Dev04, 10.1.6.Final > > > The exported values are meaningless, constant, 0 or in some cases -1. It would be better not to register those metrics at all in this case. Actually, that was the initial, documented, intention but we have a small bug. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11512) The mass indexer should iterate over the cache only once

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11512?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11512: --------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Merged in master. The PR for 10.1.x is still pending > The mass indexer should iterate over the cache only once > -------------------------------------------------------- > > Key: ISPN-11512 > URL: https://issues.redhat.com/browse/ISPN-11512 > Project: Infinispan > Issue Type: Enhancement > Components: Indexing > Affects Versions: 10.1.5.Final, 11.0.0.Dev03 > Reporter: Dan Berindei > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 11.0.0.Final > > > {{DistributedExecutorMassIndexer}} starts an {{IndexWorker}} for each indexed type and submits them to all the nodes in parallel. Each {{IndexWorker}} runs a blocking iteration over the cache, and when the cache has a store, that iteration is very expensive. > Each iteration will load and deserialize all the entries in the store. Most stores don't implement {{AbstractSegmentedStoreConfiguration}}, so Infinispan wraps them in a {{ComposedSegmentedLoadWriteStore}}, which iterates over each segment in parallel on the persistence/blocking executor. Since the default number of segments is 256 and the persistence/blocking executor has 4*cpu_count/150 max threads, it doesn't take a lot of parallel iterations to fill the blocking executor's threads and prevent the cache from doing other, more urgent, work. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11555) Off-heap state transfer does not preserve the timestamp of entries

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-11555: --------------------------------------- Summary: Off-heap state transfer does not preserve the timestamp of entries Key: ISPN-11555 URL: https://issues.redhat.com/browse/ISPN-11555 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 9.4.18.Final, 10.1.5.Final, 11.0.0.Dev03 Reporter: Wolf-Dieter Fink Assignee: Dan Berindei Fix For: 11.0.0.Dev04 The ISPN-4075 fix made state transfer preserve the timestamp of mortal/transient entries with OBJECT and BINARY storage, but not with OFF_HEAP storage. {{OffHeapEntryFactoryImpl.create()}} doesn't even receive the entry's created/last access timestamps, instead it always writes {{timeService.wallClockTime()}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11534) Deprecate DefaultCacheManager constructors with default configuration

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11534?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11534: -------------------------------- Status: Open (was: New) > Deprecate DefaultCacheManager constructors with default configuration > --------------------------------------------------------------------- > > Key: ISPN-11534 > URL: https://issues.redhat.com/browse/ISPN-11534 > Project: Infinispan > Issue Type: Bug > Components: API, Core > Affects Versions: 11.0.0.Dev03 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Dev04 > > > {{DefaultCacheManager}} no longer has a default cache by default. In order to use the constructors with a default {{Configuration}} parameter, the user also has to define a default cache name in the {{GlobalConfiguration}}, but that is surprising. > We should remove these constructors, as the user can use the {{ConfigurationBuilderHolder}} constructor to define a default cache (and other caches as well) before starting the cache manager. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11534) Deprecate DefaultCacheManager constructors with default configuration

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11534?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11534: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8120 > Deprecate DefaultCacheManager constructors with default configuration > --------------------------------------------------------------------- > > Key: ISPN-11534 > URL: https://issues.redhat.com/browse/ISPN-11534 > Project: Infinispan > Issue Type: Bug > Components: API, Core > Affects Versions: 11.0.0.Dev03 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Dev04 > > > {{DefaultCacheManager}} no longer has a default cache by default. In order to use the constructors with a default {{Configuration}} parameter, the user also has to define a default cache name in the {{GlobalConfiguration}}, but that is surprising. > We should remove these constructors, as the user can use the {{ConfigurationBuilderHolder}} constructor to define a default cache (and other caches as well) before starting the cache manager. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11554) Off-heap state transfer does not preserve the timestamp of entries

by Dan Berindei (Jira)

Dan Berindei created ISPN-11554: ----------------------------------- Summary: Off-heap state transfer does not preserve the timestamp of entries Key: ISPN-11554 URL: https://issues.redhat.com/browse/ISPN-11554 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 11.0.0.Dev03, 10.1.5.Final, 9.4.18.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 11.0.0.Dev04 The ISPN-4075 fix made state transfer preserve the timestamp of mortal/transient entries with OBJECT and BINARY storage, but not with OFF_HEAP storage. {{OffHeapEntryFactoryImpl.create()}} doesn't even receive the entry's created/last access timestamps, instead it always writes {{timeService.wallClockTime()}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11554) Off-heap state transfer does not preserve the timestamp of entries

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11554?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11554: -------------------------------- Status: Open (was: New) > Off-heap state transfer does not preserve the timestamp of entries > ------------------------------------------------------------------ > > Key: ISPN-11554 > URL: https://issues.redhat.com/browse/ISPN-11554 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.4.18.Final, 10.1.5.Final, 11.0.0.Dev03 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Dev04 > > > The ISPN-4075 fix made state transfer preserve the timestamp of mortal/transient entries with OBJECT and BINARY storage, but not with OFF_HEAP storage. > {{OffHeapEntryFactoryImpl.create()}} doesn't even receive the entry's created/last access timestamps, instead it always writes {{timeService.wallClockTime()}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11156) Move the CustomFailurePolicy interface to a different package than org.infinispan.xsite

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11156?page=com.atlassian.jira.plugi... ] Will Burns resolved ISPN-11156. ------------------------------- Resolution: Done > Move the CustomFailurePolicy interface to a different package than org.infinispan.xsite > --------------------------------------------------------------------------------------- > > Key: ISPN-11156 > URL: https://issues.redhat.com/browse/ISPN-11156 > Project: Infinispan > Issue Type: Enhancement > Components: Cross-Site Replication > Affects Versions: 10.1.0.Final > Reporter: Donald Naro > Assignee: Pedro Ruivo > Priority: Major > Fix For: 11.0.0.Dev04 > > > https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... > move the CustomFailurePolicy interface to a different package than org.infinispan.xsite. the xsite package contains only internal classes so the custom policy interface is not in javadocs, even though it should be. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11482) Provide way for ClusterExecutor to use non blocking thread

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11482?page=com.atlassian.jira.plugi... ] Work on ISPN-11482 stopped by Will Burns. ----------------------------------------- > Provide way for ClusterExecutor to use non blocking thread > ---------------------------------------------------------- > > Key: ISPN-11482 > URL: https://issues.redhat.com/browse/ISPN-11482 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Dev04 > > > https://github.com/infinispan/infinispan/pull/7997#discussion_r394122227 changes cluster executor to run tasks on the blocking executor. Unfortunately since a user can run any arbitrary code we don't know if it will block or not. We should provide some way to run non blocking code more easily. Maybe add a new API method that is non blocking? -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10835) Docs: Cross-Site Repl with IRAC

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-10835?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-10835: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 11.0.0.Dev04 Resolution: Done > Docs: Cross-Site Repl with IRAC > ------------------------------- > > Key: ISPN-10835 > URL: https://issues.redhat.com/browse/ISPN-10835 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 11.0.0.Dev04 > > > Update cross-site replication docs for IRAC conflict resolution. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2020