March 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4022) M/R: Run the combiner concurrently with the mapper

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-4022?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-4022: ------------------------------------------- [~dan.berindei] and [~mircea.markus] I thought about this a bit further and I concluded there are additional benefits to this approach. I would call this enhancement "staggered combine". Just as Dan suggests we should invoke combine on certain thresholds (say 1K entries in a combiner) during map phase and move intermediate KOut/VOut values around cluster as these thresholds are reached. The benefit is that not only we will relieve memory pressure, we will also never run out of RAM storing map output in a Collector. In addition staggered migration of KOut/VOut to intermediate cache should alleviate some of the insertion stress we have observed in performance tests. If we are able to combine this feature with ISPN-3999 Sanne suggested this should be awesome! WDYT? > M/R: Run the combiner concurrently with the mapper > -------------------------------------------------- > > Key: ISPN-4022 > URL: https://issues.jboss.org/browse/ISPN-4022 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Distributed Execution and Map/Reduce > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Assignee: Vladimir Blagojevic > Fix For: 7.0.0.Final > > > Because we only run the combiner after we finished the mapping phase, we need to keep all the results of the mapping phase in memory at once. We should split the output of the mapper into chunks and allow the combiner to process chunks while the mapper is still running, relieving some of the memory pressure. Maybe even block the mapper if there are too many chunks in-flight. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4068) Add support for IncludeCurrentState to listeners

by William Burns (JIRA)

William Burns created ISPN-4068: ----------------------------------- Summary: Add support for IncludeCurrentState to listeners Key: ISPN-4068 URL: https://issues.jboss.org/browse/ISPN-4068 Project: Infinispan Issue Type: Feature Request Components: Listeners Reporter: William Burns Assignee: Dan Berindei Fix For: 7.0.0.Final Cluster listeners were added with ISPN-3355. This didn't cover the includeInitialState support. This should be able to work with both local and cluster listeners. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3771) HotRod SSL is not working properly with IBM JDKs -- SSLHandshakeException

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-3771?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-3771: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2411 > HotRod SSL is not working properly with IBM JDKs -- SSLHandshakeException > ------------------------------------------------------------------------- > > Key: ISPN-3771 > URL: https://issues.jboss.org/browse/ISPN-3771 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 6.0.0.Final > Environment: Both RHEL x64 and x32 architecture using IBM JDK 6 or IBM JDK 7. > Test is passing for Open-jdk and Oracle-jdk. > Reporter: Tomas Sykora > Assignee: Mircea Markus > Attachments: hotRodSSLibmJDKsProblem > > > For reproducing, run mvn clean verify -Psuite.examples -DfailIfNoTests=false -Dtest=ExampleConfigsTest#testSSLHotRodConfig in Infinispan-server testsuite, using IBM JDK 7. > See attached file for stack trace. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4010) Allow configuring the LevelDB cache store through JON

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-4010?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-4010: -------------------------------- Fix Version/s: 7.0.0.Final 7.0.0.Alpha2 > Allow configuring the LevelDB cache store through JON > ----------------------------------------------------- > > Key: ISPN-4010 > URL: https://issues.jboss.org/browse/ISPN-4010 > Project: Infinispan > Issue Type: Feature Request > Reporter: Mircea Markus > Assignee: William Burns > Labels: 621, 630 > Fix For: 7.0.0.Final, 7.0.0.Alpha2 > > > Although a JON console can create a cache, the JON can not set a levelDB store configuration. Our customer wants to set a levelDB store setting using the JON when creating the cache. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4010) Allow configuring the LevelDB cache store through JON

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4010?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4010: ----------------------------------------------- William Burns <wburns(a)redhat.com> changed the Status of [bug 1060301|https://bugzilla.redhat.com/show_bug.cgi?id=1060301] from NEW to POST > Allow configuring the LevelDB cache store through JON > ----------------------------------------------------- > > Key: ISPN-4010 > URL: https://issues.jboss.org/browse/ISPN-4010 > Project: Infinispan > Issue Type: Feature Request > Reporter: Mircea Markus > Assignee: William Burns > Labels: 621, 630 > > Although a JON console can create a cache, the JON can not set a levelDB store configuration. Our customer wants to set a levelDB store setting using the JON when creating the cache. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4010) Allow configuring the LevelDB cache store through JON

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4010?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4010: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1060301 > Allow configuring the LevelDB cache store through JON > ----------------------------------------------------- > > Key: ISPN-4010 > URL: https://issues.jboss.org/browse/ISPN-4010 > Project: Infinispan > Issue Type: Feature Request > Reporter: Mircea Markus > Assignee: William Burns > Labels: 621, 630 > > Although a JON console can create a cache, the JON can not set a levelDB store configuration. Our customer wants to set a levelDB store setting using the JON when creating the cache. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4010) Allow configuring the LevelDB cache store through JON

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4010?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4010: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1060301, https://bugzilla.redhat.com/show_bug.cgi?id=1060299 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1060301) > Allow configuring the LevelDB cache store through JON > ----------------------------------------------------- > > Key: ISPN-4010 > URL: https://issues.jboss.org/browse/ISPN-4010 > Project: Infinispan > Issue Type: Feature Request > Reporter: Mircea Markus > Assignee: William Burns > Labels: 621, 630 > > Although a JON console can create a cache, the JON can not set a levelDB store configuration. Our customer wants to set a levelDB store setting using the JON when creating the cache. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4010) Allow configuring the LevelDB cache store through JON

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-4010?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-4010: -------------------------------- Labels: 621 630 (was: 630) > Allow configuring the LevelDB cache store through JON > ----------------------------------------------------- > > Key: ISPN-4010 > URL: https://issues.jboss.org/browse/ISPN-4010 > Project: Infinispan > Issue Type: Feature Request > Reporter: Mircea Markus > Assignee: William Burns > Labels: 621, 630 > > Although a JON console can create a cache, the JON can not set a levelDB store configuration. Our customer wants to set a levelDB store setting using the JON when creating the cache. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3947) HotRod client keep trying recover connections to a failed cluster

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3947?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3947: -------------------------------- Labels: 621 hotrod hotrod-java-client (was: hotrod hotrod-java-client) > HotRod client keep trying recover connections to a failed cluster > ----------------------------------------------------------------- > > Key: ISPN-3947 > URL: https://issues.jboss.org/browse/ISPN-3947 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Affects Versions: 6.0.1.Final, 7.0.0.Alpha1 > Reporter: Wolf-Dieter Fink > Assignee: Galder Zamarreño > Priority: Critical > Labels: 621, hotrod, hotrod-java-client > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > If an infinispan-server cluster is not longer reachable for some reason, i.e. network disconnect, the hot-rod client try to re-establish the lost connections. > The client library will retry this by a fixed calculation based on the max numbers of connections from the pool or 10 multiplied with the number of available servers. > This can lead in a very long time until the application can continue and react as it will wait for the read- or connect-timeout for each try. > To improve this behaviour there should be a configurable limit of retries per server and/or a timeout in total. > This will give the application the chance to handle a remote-cache failure and reply to the user instead of hanging for minutes (with the default settings) -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3845) CACHE_MODE_LOCAL flag only works in primary owner for non-tx caches

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3845?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3845: -------------------------------- Labels: 621 testsuite_stability (was: testsuite_stability) > CACHE_MODE_LOCAL flag only works in primary owner for non-tx caches > ------------------------------------------------------------------- > > Key: ISPN-3845 > URL: https://issues.jboss.org/browse/ISPN-3845 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Labels: 621, testsuite_stability > Fix For: 7.0.0.Alpha1 > > > the flag is not forcing the EntryWrappingInterceptor to wrap the entry. the result is the entry will not be stored in the cache. > It's causing the random failures in: > {noformat} > HotRodReplicationTest.testReplicatedPutWithTopologyChanges > HotRod11ReplicationTest.testReplicatedPutWithTopologyChanges > HotRod12ReplicationTest.testReplicatedPutWithTopologyChanges > {noformat} -- 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

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2014