December 2016 - infinispan-issues

[JBoss JIRA] (ISPN-7283) Make remote event supporting cluster listener more fine grained

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7283?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-7283: ------------------------------------- Master is now as well > Make remote event supporting cluster listener more fine grained > --------------------------------------------------------------- > > Key: ISPN-7283 > URL: https://issues.jboss.org/browse/ISPN-7283 > Project: Infinispan > Issue Type: Bug > Components: Listeners, Remote Protocols > Affects Versions: 9.0.0.Alpha4, 8.2.5.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.Beta2, 8.2.6.Final > > > Make server side cluster listener used for supporting remote events more fine grained. Right now if a client registers for created events, server side all nodes push all currently supported events over to the node where the remote listener is located: created, modified, removed and expired. Having all these events being passed around the cluster creates unnecessary load which can create problems in other nodes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7283) Make remote event supporting cluster listener more fine grained

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7283?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7283: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Make remote event supporting cluster listener more fine grained > --------------------------------------------------------------- > > Key: ISPN-7283 > URL: https://issues.jboss.org/browse/ISPN-7283 > Project: Infinispan > Issue Type: Bug > Components: Listeners, Remote Protocols > Affects Versions: 9.0.0.Alpha4, 8.2.5.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.Beta2, 8.2.6.Final > > > Make server side cluster listener used for supporting remote events more fine grained. Right now if a client registers for created events, server side all nodes push all currently supported events over to the node where the remote listener is located: created, modified, removed and expired. Having all these events being passed around the cluster creates unnecessary load which can create problems in other nodes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7320) Upgrade to RestEasy 3.1.0.Final

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7320?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7320: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4736 > Upgrade to RestEasy 3.1.0.Final > ------------------------------- > > Key: ISPN-7320 > URL: https://issues.jboss.org/browse/ISPN-7320 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Protocols, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Beta2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7320) Upgrade to RestEasy 3.1.0.Final

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7320?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7320: ---------------------------------- Status: Open (was: New) > Upgrade to RestEasy 3.1.0.Final > ------------------------------- > > Key: ISPN-7320 > URL: https://issues.jboss.org/browse/ISPN-7320 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Protocols, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Beta2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7321) Upgrade to AEsh 0.66.13

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7321?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7321: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4736 > Upgrade to AEsh 0.66.13 > ----------------------- > > Key: ISPN-7321 > URL: https://issues.jboss.org/browse/ISPN-7321 > Project: Infinispan > Issue Type: Component Upgrade > Components: CLI, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Beta2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7321) Upgrade to AEsh 0.66.13

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7321?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7321: ---------------------------------- Status: Open (was: New) > Upgrade to AEsh 0.66.13 > ----------------------- > > Key: ISPN-7321 > URL: https://issues.jboss.org/browse/ISPN-7321 > Project: Infinispan > Issue Type: Component Upgrade > Components: CLI, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Beta2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7321) Upgrade to AEsh 0.66.13

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-7321: ------------------------------------- Summary: Upgrade to AEsh 0.66.13 Key: ISPN-7321 URL: https://issues.jboss.org/browse/ISPN-7321 Project: Infinispan Issue Type: Component Upgrade Components: CLI, Server Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 9.0.0.Beta2 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7320) Upgrade to RestEasy 3.1.0.Final

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-7320: ------------------------------------- Summary: Upgrade to RestEasy 3.1.0.Final Key: ISPN-7320 URL: https://issues.jboss.org/browse/ISPN-7320 Project: Infinispan Issue Type: Component Upgrade Components: Remote Protocols, Server Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 9.0.0.Beta2 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7317) Errors on Cache Configuration Screen

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7317?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-7317: ------------------------------------- Eviction DMR is removed and is replaced by the new memory sub element. There is no longer a configurable eviction or thread strategy. The only things the new memory one does in regards to eviction is the max size and the eviction type whether it is MEMORY or COUNT. For example this cache has a memory element of off heap with a size of 1 GB using the default eviction type. {code}[standalone@localhost:9990 memory=OFF-HEAP] ls address-count=undefined eviction=undefined size=1000000000{code} > Errors on Cache Configuration Screen > ------------------------------------ > > Key: ISPN-7317 > URL: https://issues.jboss.org/browse/ISPN-7317 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.Beta1 > Reporter: Ryan Emerson > Assignee: Vladimir Blagojevic > Attachments: Screenshot from 2016-12-16 10-29-39.png > > > When going to a cache's configuration screen there are errors thrown in the console stating that the property type is undefined. > {code:javascript} > TypeError: Cannot read property 'type' of undefined > at Object.convertListToJson (http://localhost:3000/common/configuration/ConfigUtil.js:38:46) > at ConfigurationSectionCtrl.eval (http://localhost:3000/components/configuration-section/ConfigurationSecti...) > at Array.forEach (native) > at eval (http://localhost:3000/components/configuration-section/ConfigurationSecti...) > at Array.forEach (native) > at ConfigurationSectionCtrl.cleanMetadata (http://localhost:3000/components/configuration-section/ConfigurationSecti...) > at new ConfigurationSectionCtrl (http://localhost:3000/components/configuration-section/ConfigurationSecti...) > at Object.invoke (http://localhost:3000/vendor/jspm_packages/npm/angular@1.5.8/angular.js:4...) > at $controllerInit (http://localhost:3000/vendor/jspm_packages/npm/angular@1.5.8/angular.js:1...) > at nodeLinkFn (http://localhost:3000/vendor/jspm_packages/npm/angular@1.5.8/angular.js:9...) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (HRJS-30) Move testsuite server orchestration to a domain

by Galder Zamarreño (JIRA)

Galder Zamarreño created HRJS-30: ------------------------------------ Summary: Move testsuite server orchestration to a domain Key: HRJS-30 URL: https://issues.jboss.org/browse/HRJS-30 Project: Infinispan Javascript client Issue Type: Enhancement Affects Versions: 0.3.0 Reporter: Galder Zamarreño As more tests have been added to the Infinispan JS testsuite, the existing simple server orchestration script/environment are turning out to be a bit painful to deal with. On one hand, Haskell's {{stack}} can be sometimes difficult to install in some envs, e.g. Ubuntu. I've also seen issues with Turtle library used in Haskell and copying contents inside symbolic links in Red Hat Linux. On top of that, as security and cross-site tests were added, more configurations were added and more servers need to be added, making it track the configs a bit more confusing. Finally, the methods used to start/stop servers in self-contained tests, e.g. xsite and cluster failover, a little bit clunky. So, with this in mind, we thought of using more suitable orchestration techniques for Infinispan servers. We considered docker compose and kubernetes, but since the servers just simply need to run in a single machine and there's not a huge need to have clean environments, we decided to use a single Infinispan server domain to orchestrate all servers. The advantages of domain is that is easy to start all servers with the right configuration very quickly, and start/stop servers from tests is very easy and quick compared with current approach. On top of that, having domain based orchestration will make it easy to port over the servers, their configs and script over to testsuites of other langs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2016