March 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5709) Support for running Infinispan as an Application in YARN

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5709?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5709: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > Support for running Infinispan as an Application in YARN > -------------------------------------------------------- > > Key: ISPN-5709 > URL: https://issues.jboss.org/browse/ISPN-5709 > Project: Infinispan > Issue Type: Feature Request > Components: Hadoop Integration > Reporter: Gustavo Fernandes > Fix For: 8.2.0.Final > > > Hadoop 2.x allows custom "applications" to be managed by the resource scheduler framework. As an example, Apache Spark, Apache Tez, HBase and others can be bootstrapped and managed on top of Yarn. > Running on top of Yarn offers the following capabilities: > * Creating on demand (or long running) clusters with a simple command line, possibly targeting different versions and/or number of nodes > * Increase/Decrease the number of nodes as required > * Fine grained control of memory/CPU/disk/network utilized > * Submit arbitrary jobs targeting the application -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5976) Server ops which don't manipulate the model should be runtime only

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5976?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5976: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > Server ops which don't manipulate the model should be runtime only > ------------------------------------------------------------------ > > Key: ISPN-5976 > URL: https://issues.jboss.org/browse/ISPN-5976 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Affects Versions: 8.1.0.Beta1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5979) Server cache operations that don't affect the model should be executable in profile and per-server

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5979?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5979: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > Server cache operations that don't affect the model should be executable in profile and per-server > -------------------------------------------------------------------------------------------------- > > Key: ISPN-5979 > URL: https://issues.jboss.org/browse/ISPN-5979 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.1.0.Beta1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.2.0.Final > > > Server cache commands can be executed in both profiles and per-server, so they should be set "runtme only" when they don't affect the model. > Additionally server commands should use a more robust method of obtaining the container/cache from the operation's path address -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5929) InfinispanQueryIT.testQueryOnFirstNode random failures

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5929?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5929: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > InfinispanQueryIT.testQueryOnFirstNode random failures > ------------------------------------------------------ > > Key: ISPN-5929 > URL: https://issues.jboss.org/browse/ISPN-5929 > Project: Infinispan > Issue Type: Bug > Components: Integration , Test Suite - Query > Affects Versions: 8.1.0.Alpha2 > Reporter: Dan Berindei > Assignee: Adrian Nistor > Priority: Blocker > Fix For: 8.2.0.Final > > > {{InfinispanQueryIT.testQueryOnFirstNode()}} and {{InfinispanQueryIT.testQueryOnSecondNode()}} fail randomly in CI with this assertion: > {noformat} > java.lang.AssertionError: expected:<3> but was:<2> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at org.infinispan.test.integration.as.query.InfinispanQueryIT.testQueryOnFirstNode(InfinispanQueryIT.java:99) > {noformat} > Example: http://ci.infinispan.org/viewLog.html?buildId=31810&tab=buildResultsDiv&b... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5975) Flush cache operation for server

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5975?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5975: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > Flush cache operation for server > -------------------------------- > > Key: ISPN-5975 > URL: https://issues.jboss.org/browse/ISPN-5975 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.2.0.Final > > > Implement a flush-cache operation registered for every cache type which, if passivation is enabled, evicts all entries to the store, otherwise if a write-behind cache store is enabled, it waits for completion, otherwise it does nothing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5892) XML configuration should include number of segments for replicated caches

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5892?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5892: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > XML configuration should include number of segments for replicated caches > ------------------------------------------------------------------------- > > Key: ISPN-5892 > URL: https://issues.jboss.org/browse/ISPN-5892 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 8.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.2.0.Final > > > The primary owner of a key is determined based on the segment, so for remote caches it's good to increase the number of segments when there are many nodes in the cluster. Groups configuration may be useful as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5894) Move near cache demo from source to a separate repo

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5894?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5894: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > Move near cache demo from source to a separate repo > --------------------------------------------------- > > Key: ISPN-5894 > URL: https://issues.jboss.org/browse/ISPN-5894 > Project: Infinispan > Issue Type: Task > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.2.0.Final > > > Move near cache demo from source to a separate repo. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5862) Add version number to deprecated comments

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5862?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5862: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > Add version number to deprecated comments > ----------------------------------------- > > Key: ISPN-5862 > URL: https://issues.jboss.org/browse/ISPN-5862 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Affects Versions: 8.1.0.Alpha1 > Reporter: Dan Berindei > Fix For: 8.2.0.Final > > > It should be possible to remove deprecated classes and methods after one major version cycle, but it's not always obvious when the API was deprecated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5853) Add Hawkular subsytem to server distribution

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5853?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5853: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > Add Hawkular subsytem to server distribution > -------------------------------------------- > > Key: ISPN-5853 > URL: https://issues.jboss.org/browse/ISPN-5853 > Project: Infinispan > Issue Type: Task > Components: JMX, reporting and management, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.2.0.Final > > > https://github.com/hawkular/hawkular-agent/blob/master/hawkular-wildfly-a... > <storage-adapter type="HAWKULAR" username="jdoe" password="password" url="http://${jboss.bind.address:127.0.0.1}:${jboss.http.port:8080}" /> > Use bindings. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5849) AutoCloseable return from adding listeners can be clunky to use

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5849?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5849: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > AutoCloseable return from adding listeners can be clunky to use > --------------------------------------------------------------- > > Key: ISPN-5849 > URL: https://issues.jboss.org/browse/ISPN-5849 > Project: Infinispan > Issue Type: Sub-task > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.2.0.Final > > > On one side, to use it as a try-with-resource, you need to declare it right in the {{try()}}; > {code} > try(AutoCloseable handler = writeOnlyMap.listeners().onWrite(written -> > System.out.printf("Written (via onWrite): %s%n", written.get()))) { > Map<String, String> entries = new HashMap<>(); > entries.put("key1", "value1"); > entries.put("key2", "value2"); > writeOnlyMap.evalMany(entries, (v, writeView) -> writeView.set(v)) > .get(); // Wait for completable future > } > {code} > So it's usability is mostly designed for unit tests since listeners tend to be set and removed at a later stage. IOW, listeners are not generally a short-lived object. > The other aspect that is clunky to use is the fact that AutoCloseable's close() throws Exception, which again makes it ackward to use for example if lambdas. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2016