July 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5179) Add distributed execution and map/reduce job statistics

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-5179?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-5179: -------------------------------------- Fix Version/s: 9.0.0.Alpha4 (was: 9.0.0.Alpha3) > Add distributed execution and map/reduce job statistics > -------------------------------------------------------- > > Key: ISPN-5179 > URL: https://issues.jboss.org/browse/ISPN-5179 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.Alpha4 > > > We should add DMR/JMX statistics for the running distributed execution jobs as well as map/reduce jobs. The statistics will also include overview/total system statistics of previously executed jobs; we might store statistics of individual executed jobs in some internal cache. However, the primary objective is to calculate and maintain dist.exec and map/reduce job statistics for Infinispan admin console. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5218) Add batching to the AdvancedCacheWriter interface

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-5218?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-5218: -------------------------------------- Fix Version/s: 9.0.0.Alpha4 (was: 9.0.0.Alpha3) > Add batching to the AdvancedCacheWriter interface > ------------------------------------------------- > > Key: ISPN-5218 > URL: https://issues.jboss.org/browse/ISPN-5218 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Tristan Tarrant > Assignee: Ryan Emerson > Fix For: 9.0.0.Alpha4 > > > The AdvancedCacheWriter should be extended with a write operation which takes multiple entries so that stores which can do batching can optimize this. This would benefit both passivation and the async writer. > Immediate users would be the JDBC stores. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5427) Change getAll to return ordered map

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-5427?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-5427: -------------------------------------- Fix Version/s: 9.0.0.Alpha4 (was: 9.0.0.Alpha3) > Change getAll to return ordered map > ----------------------------------- > > Key: ISPN-5427 > URL: https://issues.jboss.org/browse/ISPN-5427 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Remote Protocols > Reporter: William Burns > Assignee: William Burns > Fix For: 9.0.0.Alpha4 > > > Currently our getAll returns a map of entries that exist in the cache in any order. We could enhance this to return a map where the entries are in the same iteration order of the Set (important when the user uses a LinkedHashSet). We could even do something like List<V> getAll(List<K>) to show better ordering as an option too. > This has 2 immediate advantages. > 1. Remote getAll no longer requires to serialize all the keys in the response since it knows which values map to which keys based on what it sent. > 2. Query results need ordered List as well. See query/src/main/java/org/infinispan/query/impl/EntityLoader.java -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5426) Create a remote query tutorial

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-5426?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-5426: -------------------------------------- Fix Version/s: 9.0.0.Alpha4 (was: 9.0.0.Alpha3) > Create a remote query tutorial > ------------------------------ > > Key: ISPN-5426 > URL: https://issues.jboss.org/browse/ISPN-5426 > Project: Infinispan > Issue Type: Feature Request > Components: Documentation-Query, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha4 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5424) SemaphoreCompletionService improvements

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-5424?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-5424: -------------------------------------- Fix Version/s: 9.0.0.Alpha4 (was: 9.0.0.Alpha3) > SemaphoreCompletionService improvements > --------------------------------------- > > Key: ISPN-5424 > URL: https://issues.jboss.org/browse/ISPN-5424 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 7.2.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Alpha4 > > > Turns out the {{CompletionService}} features aren't that necessary, and it makes the use of {{Runnable}} more cumbersome. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5415) Expose protobuf entries to scripting

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-5415?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-5415: -------------------------------------- Fix Version/s: 9.0.0.Alpha4 (was: 9.0.0.Alpha3) > Expose protobuf entries to scripting > ------------------------------------ > > Key: ISPN-5415 > URL: https://issues.jboss.org/browse/ISPN-5415 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Querying > Affects Versions: 8.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha4 > > > We need an alternative API for Protostream marshalling that is easy to consume from scripting languages. The messages need to be unmarshalled into a map-like object that can be accessed easily from scripting languages. No marshaller implementation code should be provided by users, also no annotations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5241) Cache topology updates should use the NO_FC flag

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-5241?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-5241: -------------------------------------- Fix Version/s: 9.0.0.Alpha4 (was: 9.0.0.Alpha3) > Cache topology updates should use the NO_FC flag > ------------------------------------------------ > > Key: ISPN-5241 > URL: https://issues.jboss.org/browse/ISPN-5241 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 7.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 9.0.0.Alpha4 > > > Topology updates are sent while holding the ClusterCacheStatus lock, so they should never block. However, when MFC is present, the topology update can block waiting for enough credits. As most CacheTopologyControlCommands need to acquire the ClusterCacheStatus lock, this can easily lead to a full remote-executor pool (and OOB pool) and the appearance of a deadlock. > What's more, if one node is not responsive, it can block all the other nodes from receiving further topology updates. Topology updates should be as prompt as possible, so we should use the NO_FC flag to ensure that each node receives topology updates as soon as possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5467) Design new interceptor interfaces for sequential invocation

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-5467?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-5467: -------------------------------------- Fix Version/s: 9.0.0.Alpha4 (was: 9.0.0.Alpha3) > Design new interceptor interfaces for sequential invocation > ----------------------------------------------------------- > > Key: ISPN-5467 > URL: https://issues.jboss.org/browse/ISPN-5467 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Alpha4, 9.0.0.Final > > > We need the interceptors to execute in sequence instead of using a stack in order to allow interrupting the execution of a command on one thread and continuing the execution on another thread. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5454) XSite: RetryMechanismTest random failures

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-5454?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-5454: -------------------------------------- Fix Version/s: 9.0.0.Alpha4 (was: 9.0.0.Alpha3) > XSite: RetryMechanismTest random failures > ----------------------------------------- > > Key: ISPN-5454 > URL: https://issues.jboss.org/browse/ISPN-5454 > Project: Infinispan > Issue Type: Bug > Components: Cross-Site Replication > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > Priority: Blocker > Labels: testsuite_stability > Fix For: 9.0.0.Alpha4 > > > {{ClusteredCacheBackupReceiver.awaitRemoteTask()}} doesn't respect the state push command's timeout, at least when it's smaller than the sync replication timeout in the target cache. When that happens, the state provider will resend the state, and there will be 2 state push commands executing at the same time. > RetryMechanismTest changes the state push timeout to 2 seconds, but the sync replication timeout stays at 15 seconds. This causes failures in {{testRetryLocally}} and {{testFailRetryLocally}}, if it takes more than 2 seconds to suspect the killed node. > {noformat} > 10:02:13,007 TRACE (asyncTransportThread-8,NodeN:) [RetryOnFailureXSiteCommand] Sending XSiteStatePushCommand{cacheName=___defaultcache, timeout=2000 (1 keys)} to [NYC (sync, timeout=2000)] > 10:02:16,008 TRACE (asyncTransportThread-8,NodeN:) [RetryOnFailureXSiteCommand] Sending XSiteStatePushCommand{cacheName=___defaultcache, timeout=2000 (1 keys)} to [NYC (sync, timeout=2000)] > 10:02:16,040 TRACE (asyncTransportThread-4,NodeP:) [RpcManagerImpl] replication exception: > org.infinispan.remoting.transport.jgroups.SuspectException: Node NodeQ-56809 was suspected > 10:02:16,040 TRACE (asyncTransportThread-0,NodeP:) [RpcManagerImpl] replication exception: > org.infinispan.remoting.transport.jgroups.SuspectException: Node NodeQ-56809 was suspected > 10:02:19,147 ERROR (testng-RetryMechanismTest:) [UnitTestTestNGListener] Test testFailRetryLocally(org.infinispan.xsite.statetransfer.failures.RetryMechanismTest) failed. > java.lang.AssertionError: expected:<2> but was:<3> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:245) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:252) > at org.infinispan.xsite.statetransfer.failures.RetryMechanismTest.testFailRetryLocally(RetryMechanismTest.java:227) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5453) X-site state transfer: retry locally if local state push throws a SuspectException

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-5453?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-5453: -------------------------------------- Fix Version/s: 9.0.0.Alpha4 (was: 9.0.0.Alpha3) > X-site state transfer: retry locally if local state push throws a SuspectException > ---------------------------------------------------------------------------------- > > Key: ISPN-5453 > URL: https://issues.jboss.org/browse/ISPN-5453 > Project: Infinispan > Issue Type: Bug > Components: Core, Cross-Site Replication > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > Priority: Minor > Fix For: 9.0.0.Alpha4 > > > When the local state push command throws a {{SuspectException}}, we currently retry remotely unless the target node was already removed from the cache topology. This will fail with another {{SuspectException}}, so it would be better to retry locally the first time. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 July 2016