July 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7973) Investigate Service Brokers

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7973?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec edited comment on ISPN-7973 at 7/12/17 4:06 AM: -------------------------------------------------------------------- Based on [discussion between Marko Luksa and Emmanuel Bernard|https://bluejeans.com/s/uij6Y]: * Marko implemented En Masse. * The Broker controls instances it created. E.g. we might imagine having a JDG Broker which will add a cache to all living instances. * The {{ServicePlan}} is a resource incorporated into {{ServiceClass}}. It is not separate. * The Broker can instantiate the service synchronously or asynchronously. * The client can specify the name of a {{Secret}} with credentials. Currently users need to preconfigure their apps (to use the secret provided by the Catalog). There are plans to make it the other way around. * An {{Endpoints}} object contains a list of IP addresses and ports to desired Pods (or other type of services) * The Boker Pod can provide its own UI (it's just a running Pod). * Ideas: * We may use the Broker to instrument the deployed JDG instances * We may use the Broker to instantiate JDG instances outside of the cloud. During the Bind step we could provide credentials to connect to it. In addition to that we'd need to manually facilitate {{Endpoints}} objects pointing to the cluster. * During the bind operation we should provide {{hotrod-client.properties}}. * Things to clarify and other issues: * No UI for creating/deleting/editing ServicePlans. It is also worth to mention that OpenShift Origin (with {{oc cluster up}}) comes with one default plan (use {{oc edit ServiceClass infinispan-ephemeral}} to view it). * Shall we create separate separate service or one service with multiple plans? was (Author: sebastian.laskawiec): Based on [discussion between Marko Luksa and Emmanuel Bernard|https://bluejeans.com/s/uij6Y]: * Marko implemented En Masse. * The Broker controls instances it created. E.g. we might imagine having a JDG Broker which will add a cache to all living instances. * The {{ServicePlan}} is a resource incorporated into {{ServiceClass}}. It is not separate. * The Broker can instantiate the service synchronously or asynchronously. * The client can specify the name of a {{Secret}} with credentials. Currently users need to preconfigure their apps (to use the secret provided by the Catalog). There are plans to make it the other way around. * An {{Endpoints}} object contains a list of IP addresses and ports to desired Pods (or other type of services) * The Boker Pod can provide its own UI (it's just a running Pod). * Ideas: * We may use the Broker to instrument the deployed JDG instances * We may use the Broker to instantiate JDG instances outside of the cloud. During the Bind step we could provide credentials to connect to it. In addition to that we'd need to manually facilitate {{Endpoints}} objects pointing to the cluster. * During the bind operation we should provide {{hotrod-client.properties}}. * Potentially missing features: * No UI for creating/deleting/editing ServicePlans. It is also worth to mention that OpenShift Origin (with {{oc cluster up}}) comes with one default plan (use {{oc edit ServiceClass infinispan-ephemeral}} to view it). > Investigate Service Brokers > --------------------------- > > Key: ISPN-7973 > URL: https://issues.jboss.org/browse/ISPN-7973 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7973) Investigate Service Brokers

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7973?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec edited comment on ISPN-7973 at 7/12/17 4:01 AM: -------------------------------------------------------------------- Based on [discussion between Marko Luksa and Emmanuel Bernard|https://bluejeans.com/s/uij6Y]: * Marko implemented En Masse. * The Broker controls instances it created. E.g. we might imagine having a JDG Broker which will add a cache to all living instances. * The {{ServicePlan}} is a resource incorporated into {{ServiceClass}}. It is not separate. * The Broker can instantiate the service synchronously or asynchronously. * The client can specify the name of a {{Secret}} with credentials. Currently users need to preconfigure their apps (to use the secret provided by the Catalog). There are plans to make it the other way around. * An {{Endpoints}} object contains a list of IP addresses and ports to desired Pods (or other type of services) * The Boker Pod can provide its own UI (it's just a running Pod). * Ideas: * We may use the Broker to instrument the deployed JDG instances * We may use the Broker to instantiate JDG instances outside of the cloud. During the Bind step we could provide credentials to connect to it. In addition to that we'd need to manually facilitate {{Endpoints}} objects pointing to the cluster. * During the bind operation we should provide {{hotrod-client.properties}}. * Potentially missing features: * No UI for creating/deleting/editing ServicePlans. It is also worth to mention that OpenShift Origin (with {{oc cluster up}}) comes with one default plan (use {{oc edit ServiceClass infinispan-ephemeral}} to view it). was (Author: sebastian.laskawiec): Based on [discussion between Marko Luksa and Emmanuel Bernard|https://bluejeans.com/s/uij6Y]: * Marko implemented En Masse Potentially missing features: * No UI for creating/deleting/editing ServicePlans. It is also worth to mention that OpenShift Origin (with {{oc cluster up}}) comes with one default plan (use {{oc edit ServiceClass infinispan-ephemeral}} to view it). > Investigate Service Brokers > --------------------------- > > Key: ISPN-7973 > URL: https://issues.jboss.org/browse/ISPN-7973 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8000) Update build property version.org.infinispan.server-build.old to latest from the 8.2.x series

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8000?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8000: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Update build property version.org.infinispan.server-build.old to latest from the 8.2.x series > --------------------------------------------------------------------------------------------- > > Key: ISPN-8000 > URL: https://issues.jboss.org/browse/ISPN-8000 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 9.1.0.CR1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.1.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7973) Investigate Service Brokers

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7973?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-7973: ------------------------------------------- Based on [discussion between Marko Luksa and Emmanuel Bernard|https://bluejeans.com/s/uij6Y]: * Marko implemented En Masse Potentially missing features: * No UI for creating/deleting/editing ServicePlans. It is also worth to mention that OpenShift Origin (with {{oc cluster up}}) comes with one default plan (use {{oc edit ServiceClass infinispan-ephemeral}} to view it). > Investigate Service Brokers > --------------------------- > > Key: ISPN-7973 > URL: https://issues.jboss.org/browse/ISPN-7973 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4099) Local Listeners can raise entry events on rehash

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-4099?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-4099: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2541, https://issues.jboss.org/browse/ISPN-4099 (was: https://github.com/infinispan/infinispan/pull/2541) > Local Listeners can raise entry events on rehash > ------------------------------------------------ > > Key: ISPN-4099 > URL: https://issues.jboss.org/browse/ISPN-4099 > Project: Infinispan > Issue Type: Bug > Components: Listeners > Affects Versions: 7.0.0.Alpha1 > Reporter: William Burns > Assignee: William Burns > Fix For: 9.1.0.Final > > > -Cluster Listeners currently raise all create, modify and remove events. When a rehash event occurs this would cause a create event to be generated even though it wasn't just added to the cache. We need to not raise an event in this case.- > Writing up tests for this, cluster listeners are unaffected as they use the primaryOnly value for the listener. Further testing shows that this only affects local listeners when they become a backup owner from not being an owner. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4099) Local Listeners can raise entry events on rehash

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-4099?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-4099: -------------------------------- Fix Version/s: 9.1.0.Final > Local Listeners can raise entry events on rehash > ------------------------------------------------ > > Key: ISPN-4099 > URL: https://issues.jboss.org/browse/ISPN-4099 > Project: Infinispan > Issue Type: Bug > Components: Listeners > Affects Versions: 7.0.0.Alpha1 > Reporter: William Burns > Assignee: William Burns > Fix For: 9.1.0.Final > > > -Cluster Listeners currently raise all create, modify and remove events. When a rehash event occurs this would cause a create event to be generated even though it wasn't just added to the cache. We need to not raise an event in this case.- > Writing up tests for this, cluster listeners are unaffected as they use the primaryOnly value for the listener. Further testing shows that this only affects local listeners when they become a backup owner from not being an owner. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4032) Listeners on originator node in DIST are notified even when not an owner

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-4032?page=com.atlassian.jira.plugin.... ] William Burns resolved ISPN-4032. --------------------------------- Resolution: Duplicate Issue This is fixed by https://issues.jboss.org/browse/ISPN-7029 > Listeners on originator node in DIST are notified even when not an owner > ------------------------------------------------------------------------ > > Key: ISPN-4032 > URL: https://issues.jboss.org/browse/ISPN-4032 > Project: Infinispan > Issue Type: Bug > Components: Core, Listeners > Affects Versions: 6.0.1.Final > Reporter: William Burns > Assignee: William Burns > Labels: 630 > > Currently we notify listeners installed on the originator node when they perform a write command. This is done even when the originator node doesn't own the key. These notifications should only be fired by primary owner/backup owners normally and only primary if configured to do so. > The DistListenerTest currently even asserts this behavior around line ~85. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6157) Drop size() method from AdvancedCacheLoader SPI

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6157?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-6157: ------------------------------------- Actually this method could be useful when invoking size method on the cache and passivation is disabled. This assumes that we don't have to worry about `Flag.SKIP_CACHE_STORE` though. > Drop size() method from AdvancedCacheLoader SPI > ----------------------------------------------- > > Key: ISPN-6157 > URL: https://issues.jboss.org/browse/ISPN-6157 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Tristan Tarrant > Assignee: William Burns > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7865) Distributed Stream thread usage for key aware operations can be improved

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7865?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7865: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/5283 > Distributed Stream thread usage for key aware operations can be improved > ------------------------------------------------------------------------ > > Key: ISPN-7865 > URL: https://issues.jboss.org/browse/ISPN-7865 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Distributed Execution and Map/Reduce > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.0.Final > > > Currently iterator will block a thread on the remote server when it is trying to send back a response. It would be better if we used full async API to instead request blocks of values as the iterator consumes them. We should make sure we always maintain a distributed batch size worth. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8057) AdminOperation task engine does not adhere to API

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8057?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8057: ---------------------------------- Status: Open (was: New) > AdminOperation task engine does not adhere to API > ------------------------------------------------- > > Key: ISPN-8057 > URL: https://issues.jboss.org/browse/ISPN-8057 > Project: Infinispan > Issue Type: Bug > Components: Server, Tasks > Affects Versions: 9.1.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.1.0.Final > > > The AdminOperation task engine returns a Set<Class> instead of Set<Task> for getTasks() -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 2017