[JBoss JIRA] (ISPN-6691) Simplify Distributed Stream local intermediate operations
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-6691?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-6691:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/4366
> Simplify Distributed Stream local intermediate operations
> ---------------------------------------------------------
>
> Key: ISPN-6691
> URL: https://issues.jboss.org/browse/ISPN-6691
> Project: Infinispan
> Issue Type: Enhancement
> Components: Distributed Execution and Map/Reduce
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 9.0.0.Final
>
>
> Currently whenever a local intermediate operation (sort, limit, distinct, skip) is invoked on a distributed stream it tries to separate the invoctions based on if it should run remotely or locally. This code is quite hard to read and maintain. It also prevents the ability from adding new functionality without complicating the code substantially.
> We can rewrite this to have a new IntermediateDistributedCache that acts a bridge between the distributed (remote) stream and the local stream required for these operations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ISPN-6692) Handle exceptions in RemoteIterator close
by Gustavo Fernandes (JIRA)
Gustavo Fernandes created ISPN-6692:
---------------------------------------
Summary: Handle exceptions in RemoteIterator close
Key: ISPN-6692
URL: https://issues.jboss.org/browse/ISPN-6692
Project: Infinispan
Issue Type: Bug
Components: Remote Protocols
Reporter: Gustavo Fernandes
When closing a remote iterator during a server shutdown it should not throw exceptions like {{RemoteIllegalLifecycleStateException}} but rather log them
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ISPN-5874) Distributed Stream sort with non sorted terminal operation can fail
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-5874?page=com.atlassian.jira.plugin.... ]
William Burns commented on ISPN-5874:
-------------------------------------
An example is the following
{code}
CacheSet<Map.Entry<Integer, String>> entrySet = cache.entrySet();
assertEquals(10, createStream(entrySet).sorted((e1, e2) -> Integer.compare(e1.getKey(), e2.getKey())).mapToInt(Map.Entry::getKey).count());
{code}
> Distributed Stream sort with non sorted terminal operation can fail
> -------------------------------------------------------------------
>
> Key: ISPN-5874
> URL: https://issues.jboss.org/browse/ISPN-5874
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 8.1.0.Alpha1
> Reporter: William Burns
> Assignee: William Burns
>
> Using a sort intermediate operation when another intermediate operation is applied before sort and then invoking a terminal operation that doesn't pay attention to sorting doesn't apply the other intermediate operations properly, causing issues such as CCE and others.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ISPN-6691) Simplify Distributed Stream local intermediate operations
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-6691?page=com.atlassian.jira.plugin.... ]
William Burns commented on ISPN-6691:
-------------------------------------
This should also be able to remedy ISPN-5874
> Simplify Distributed Stream local intermediate operations
> ---------------------------------------------------------
>
> Key: ISPN-6691
> URL: https://issues.jboss.org/browse/ISPN-6691
> Project: Infinispan
> Issue Type: Enhancement
> Components: Distributed Execution and Map/Reduce
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 9.0.0.Final
>
>
> Currently whenever a local intermediate operation (sort, limit, distinct, skip) is invoked on a distributed stream it tries to separate the invoctions based on if it should run remotely or locally. This code is quite hard to read and maintain. It also prevents the ability from adding new functionality without complicating the code substantially.
> We can rewrite this to have a new IntermediateDistributedCache that acts a bridge between the distributed (remote) stream and the local stream required for these operations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ISPN-6691) Simplify Distributed Stream local intermediate operations
by William Burns (JIRA)
William Burns created ISPN-6691:
-----------------------------------
Summary: Simplify Distributed Stream local intermediate operations
Key: ISPN-6691
URL: https://issues.jboss.org/browse/ISPN-6691
Project: Infinispan
Issue Type: Enhancement
Components: Distributed Execution and Map/Reduce
Reporter: William Burns
Assignee: William Burns
Fix For: 9.0.0.Final
Currently whenever a local intermediate operation (sort, limit, distinct, skip) is invoked on a distributed stream it tries to separate the invoctions based on if it should run remotely or locally. This code is quite hard to read and maintain. It also prevents the ability from adding new functionality without complicating the code substantially.
We can rewrite this to have a new IntermediateDistributedCache that acts a bridge between the distributed (remote) stream and the local stream required for these operations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ISPN-6689) Scala @switch doesn't work for OperationStatus Enumeration
by Dan Berindei (JIRA)
Dan Berindei created ISPN-6689:
----------------------------------
Summary: Scala @switch doesn't work for OperationStatus Enumeration
Key: ISPN-6689
URL: https://issues.jboss.org/browse/ISPN-6689
Project: Infinispan
Issue Type: Bug
Components: Build process
Affects Versions: 9.0.0.Alpha2
Reporter: Dan Berindei
Priority: Minor
Fix For: 9.0.0.Alpha3
{noformat}
[WARNING] /tmp/privatebuild/infinispan/server/hotrod/src/main/scala/org/infinispan/server/hotrod/OperationStatus.scala:36: warning: could not emit switch for @switch annotated match
[INFO] (st: @switch) match {
[INFO] ^
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ISPN-6530) Cannot enable security configuration for a cache in cache configuration page if there was no security configuration at container startup
by Martin Vrabel (JIRA)
[ https://issues.jboss.org/browse/ISPN-6530?page=com.atlassian.jira.plugin.... ]
Martin Vrabel closed ISPN-6530.
-------------------------------
Resolution: Duplicate
> Cannot enable security configuration for a cache in cache configuration page if there was no security configuration at container startup
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-6530
> URL: https://issues.jboss.org/browse/ISPN-6530
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 8.2.1.Final
> Reporter: Martin Vrabel
> Assignee: Vladimir Blagojevic
>
> in cache configuration page in security tab. if we have cache container with configured secirity
> {code}
> <security>
> <authorization>
> <identity-role-mapper/>
> <role name="reader" permissions="READ"/>
> <role name="admin" permissions="ALL"/>
> <role name="executor" permissions="READ WRITE EXEC LISTEN"/>
> </authorization>
> </security>
> {code}
> and a cache that doesn't have a security configuration e.g.
> {code}
> <security>
> <authorization roles="admin" />
> </security>
> {code}
> at the start of the container and I enable security in the cache configuration page I get this error.
> {code}
> Error
> domain-failure-description
> WFLYCTL0175: Resource [ ("profile" => "clustered"), ("subsystem" => "datagrid-infinispan"), ("cache-container" => "testContainer"), ("configurations" => "CONFIGURATIONS"), ("local-cache-configuration" => "localCacheForConfigurationTesting"), ("security" => "SECURITY") ] does not exist; a resource at address [ ("profile" => "clustered"), ("subsystem" => "datagrid-infinispan"), ("cache-container" => "testContainer"), ("configurations" => "CONFIGURATIONS"), ("local-cache-configuration" => "localCacheForConfigurationTesting"), ("security" => "SECURITY"), ("authorization" => "AUTHORIZATION") ] cannot be created until all ancestor resources have been added
> {code}
> The console looks for the JMX value but because there is no configuration it throws an error
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ISPN-6685) Hot Rod server fails to start due to NPE in PersistenceManagerImpl.preload()
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-6685?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-6685:
------------------------------------
Component/s: Remote Querying
> Hot Rod server fails to start due to NPE in PersistenceManagerImpl.preload()
> ----------------------------------------------------------------------------
>
> Key: ISPN-6685
> URL: https://issues.jboss.org/browse/ISPN-6685
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Querying, Server
> Affects Versions: 9.0.0.Alpha2
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Critical
> Fix For: 9.0.0.Alpha3, 8.2.3.Final
>
> Attachments: server.log
>
>
> This occurs intermittently during the Spark connector testsuite, that starts 3 servers in parallel. The HotRod server fails to start with error:
> {noformat}
> 2016-05-19 19:31:21,976 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "datagrid-infinispan-endpoint"),
> ("hotrod-connector" => "hotrod-connector")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.datagrid-infinispan-endpoint.hotrod.hotrod-connector" => "org.jboss.msc.service.StartException in service jboss.datagrid-infinispan-endpoint.hotrod.hotrod-connector: DGENDPT10004: Failed to start HotRodServer
> Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.persistence.manager.PersistenceManagerImpl.preload() on object of type PersistenceManagerImpl
> Caused by: org.infinispan.persistence.spi.PersistenceException: Execution exception!
> Caused by: java.util.concurrent.ExecutionException: org.infinispan.persistence.spi.PersistenceException: Unable to preload!
> Caused by: org.infinispan.persistence.spi.PersistenceException: Unable to preload!
> Caused by: java.lang.NullPointerException"}}
> 2016-05-19 19:31:22,037 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service jboss.datagrid-infinispan-endpoint.hotrod.hotrod-connector: org.jboss.msc.service.StartException in service jboss.datagrid-infinispan-endpoint.hotrod.hotrod-connector: DGENDPT10004: Failed to start HotRodServer
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ISPN-6685) Hot Rod server fails to start due to NPE in PersistenceManagerImpl.preload()
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-6685?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-6685:
------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/4365
> Hot Rod server fails to start due to NPE in PersistenceManagerImpl.preload()
> ----------------------------------------------------------------------------
>
> Key: ISPN-6685
> URL: https://issues.jboss.org/browse/ISPN-6685
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 9.0.0.Alpha2
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Critical
> Fix For: 9.0.0.Alpha3, 8.2.3.Final
>
> Attachments: server.log
>
>
> This occurs intermittently during the Spark connector testsuite, that starts 3 servers in parallel. The HotRod server fails to start with error:
> {noformat}
> 2016-05-19 19:31:21,976 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "datagrid-infinispan-endpoint"),
> ("hotrod-connector" => "hotrod-connector")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.datagrid-infinispan-endpoint.hotrod.hotrod-connector" => "org.jboss.msc.service.StartException in service jboss.datagrid-infinispan-endpoint.hotrod.hotrod-connector: DGENDPT10004: Failed to start HotRodServer
> Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.persistence.manager.PersistenceManagerImpl.preload() on object of type PersistenceManagerImpl
> Caused by: org.infinispan.persistence.spi.PersistenceException: Execution exception!
> Caused by: java.util.concurrent.ExecutionException: org.infinispan.persistence.spi.PersistenceException: Unable to preload!
> Caused by: org.infinispan.persistence.spi.PersistenceException: Unable to preload!
> Caused by: java.lang.NullPointerException"}}
> 2016-05-19 19:31:22,037 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service jboss.datagrid-infinispan-endpoint.hotrod.hotrod-connector: org.jboss.msc.service.StartException in service jboss.datagrid-infinispan-endpoint.hotrod.hotrod-connector: DGENDPT10004: Failed to start HotRodServer
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months