May 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9161) Description of StateTransferManager attributes does not match the behaviour or show wrong content

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/ISPN-9161?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink commented on ISPN-9161: ---------------------------------------- The rebalancingStatus show "COMPLETE", but the description shows other values. I suppose BALANCED mean COMPLETE. See attached screen shot > Description of StateTransferManager attributes does not match the behaviour or show wrong content > ------------------------------------------------------------------------------------------------- > > Key: ISPN-9161 > URL: https://issues.jboss.org/browse/ISPN-9161 > Project: Infinispan > Issue Type: Bug > Components: Core, Documentation-Core > Reporter: Wolf-Dieter Fink > Assignee: Dan Berindei > Fix For: 9.3.0.CR1 > > Attachments: Screenshot from 2018-05-16 10-01-28.png > > > Current description is: > If true, the node has successfully joined the grid and is considered to hold state. If false, the join process is still in progress.. > But the behaviour is: > It doesn't wait for the initial state transfer, it just waits for the coordinator to send it a topology before joinComplete is set to TRUE -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9161) Description of StateTransferManager.joinComplete does not match the behaviour

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/ISPN-9161?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink updated ISPN-9161: ----------------------------------- Attachment: Screenshot from 2018-05-16 10-01-28.png > Description of StateTransferManager.joinComplete does not match the behaviour > ----------------------------------------------------------------------------- > > Key: ISPN-9161 > URL: https://issues.jboss.org/browse/ISPN-9161 > Project: Infinispan > Issue Type: Bug > Components: Core, Documentation-Core > Reporter: Wolf-Dieter Fink > Assignee: Dan Berindei > Fix For: 9.3.0.CR1 > > Attachments: Screenshot from 2018-05-16 10-01-28.png > > > Current description is: > If true, the node has successfully joined the grid and is considered to hold state. If false, the join process is still in progress.. > But the behaviour is: > It doesn't wait for the initial state transfer, it just waits for the coordinator to send it a topology before joinComplete is set to TRUE -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9161) Description of StateTransferManager attributes does not match the behaviour or show wrong content

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/ISPN-9161?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink updated ISPN-9161: ----------------------------------- Summary: Description of StateTransferManager attributes does not match the behaviour or show wrong content (was: Description of StateTransferManager.joinComplete does not match the behaviour) > Description of StateTransferManager attributes does not match the behaviour or show wrong content > ------------------------------------------------------------------------------------------------- > > Key: ISPN-9161 > URL: https://issues.jboss.org/browse/ISPN-9161 > Project: Infinispan > Issue Type: Bug > Components: Core, Documentation-Core > Reporter: Wolf-Dieter Fink > Assignee: Dan Berindei > Fix For: 9.3.0.CR1 > > Attachments: Screenshot from 2018-05-16 10-01-28.png > > > Current description is: > If true, the node has successfully joined the grid and is considered to hold state. If false, the join process is still in progress.. > But the behaviour is: > It doesn't wait for the initial state transfer, it just waits for the coordinator to send it a topology before joinComplete is set to TRUE -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9151) All client listener parameters passed in programmatically

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-9151?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-9151: ----------------------------------- Forum Reference: http://lists.jboss.org/pipermail/infinispan-dev/2018-April/018088.html > All client listener parameters passed in programmatically > --------------------------------------------------------- > > Key: ISPN-9151 > URL: https://issues.jboss.org/browse/ISPN-9151 > Project: Infinispan > Issue Type: Enhancement > Components: Listeners, Remote Protocols > Reporter: Galder Zamarreño > Labels: redhat-summit-18 > > We're working with the OpenWhisk team to create a generic Feed that allows Infinispan remote events to be exposed in an OpenWhisk way. > So, you'd pass in Hot Rod endpoint information, name of cache and other details and you'd establish a feed of data from that cache for create/updated/removed data. > However, making this generic is tricky when you want to pass in filter/converter factory names since these are defined at the annotation level. > Ideally we should have a way to pass in filter/converter factory names programmatically. To avoid limiting ourselves, you could potentially pass in an instance of the annotation in an overloaded method or as optional parameter [[1|https://stackoverflow.com/questions/16299717/how-to-create-an-instance-of-an-annotation]]. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9151) All client listener parameters passed in programmatically

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-9151?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-9151: ----------------------------------- Description: We're working with the OpenWhisk team to create a generic Feed that allows Infinispan remote events to be exposed in an OpenWhisk way. So, you'd pass in Hot Rod endpoint information, name of cache and other details and you'd establish a feed of data from that cache for create/updated/removed data. However, making this generic is tricky when you want to pass in filter/converter factory names since these are defined at the annotation level. Ideally we should have a way to pass in filter/converter factory names programmatically. To avoid limiting ourselves, you could potentially pass in an instance of the annotation in an overloaded method or as optional parameter [[1|https://stackoverflow.com/questions/16299717/how-to-create-an-instance-of-an-annotation]]. was: We're working with the OpenWhisk team to create a generic Feed that allows Infinispan remote events to be exposed in an OpenWhisk way. So, you'd pass in Hot Rod endpoint information, name of cache and other details and you'd establish a feed of data from that cache for create/updated/removed data. However, making this generic is tricky when you want to pass in filter/converter factory names since these are defined at the annotation level. Ideally we should have a way to pass in filter/converter factory names programmatically. To avoid limiting ourselves, you could potentially pass in an instance of the annotation in an overloaded method or as optional parameter [[1|https://stackoverflow.com/questions/16299717/how-to-create-an-instance-of-an-annotation ]]. > All client listener parameters passed in programmatically > --------------------------------------------------------- > > Key: ISPN-9151 > URL: https://issues.jboss.org/browse/ISPN-9151 > Project: Infinispan > Issue Type: Enhancement > Components: Listeners, Remote Protocols > Reporter: Galder Zamarreño > Labels: redhat-summit-18 > > We're working with the OpenWhisk team to create a generic Feed that allows Infinispan remote events to be exposed in an OpenWhisk way. > So, you'd pass in Hot Rod endpoint information, name of cache and other details and you'd establish a feed of data from that cache for create/updated/removed data. > However, making this generic is tricky when you want to pass in filter/converter factory names since these are defined at the annotation level. > Ideally we should have a way to pass in filter/converter factory names programmatically. To avoid limiting ourselves, you could potentially pass in an instance of the annotation in an overloaded method or as optional parameter [[1|https://stackoverflow.com/questions/16299717/how-to-create-an-instance-of-an-annotation]]. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9162) Description of StateTransferManager.joinComplete does not match the behaviour

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created ISPN-9162: -------------------------------------- Summary: Description of StateTransferManager.joinComplete does not match the behaviour Key: ISPN-9162 URL: https://issues.jboss.org/browse/ISPN-9162 Project: Infinispan Issue Type: Bug Components: Core, Documentation-Core Reporter: Wolf-Dieter Fink Assignee: Dan Berindei Fix For: 9.3.0.CR1 Current description is: If true, the node has successfully joined the grid and is considered to hold state. If false, the join process is still in progress.. But the behaviour is: It doesn't wait for the initial state transfer, it just waits for the coordinator to send it a topology before joinComplete is set to TRUE -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9161) Description of StateTransferManager.joinComplete does not match the behaviour

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9161?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9161: ------------------------------- Fix Version/s: 9.3.0.CR1 > Description of StateTransferManager.joinComplete does not match the behaviour > ----------------------------------------------------------------------------- > > Key: ISPN-9161 > URL: https://issues.jboss.org/browse/ISPN-9161 > Project: Infinispan > Issue Type: Bug > Reporter: Wolf-Dieter Fink > Assignee: Dan Berindei > Fix For: 9.3.0.CR1 > > > Current description is: > If true, the node has successfully joined the grid and is considered to hold state. If false, the join process is still in progress.. > But the behaviour is: > It doesn't wait for the initial state transfer, it just waits for the coordinator to send it a topology before joinComplete is set to TRUE -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9161) Description of StateTransferManager.joinComplete does not match the behaviour

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9161?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9161: ------------------------------- Component/s: Core Documentation-Core > Description of StateTransferManager.joinComplete does not match the behaviour > ----------------------------------------------------------------------------- > > Key: ISPN-9161 > URL: https://issues.jboss.org/browse/ISPN-9161 > Project: Infinispan > Issue Type: Bug > Components: Core, Documentation-Core > Reporter: Wolf-Dieter Fink > Assignee: Dan Berindei > Fix For: 9.3.0.CR1 > > > Current description is: > If true, the node has successfully joined the grid and is considered to hold state. If false, the join process is still in progress.. > But the behaviour is: > It doesn't wait for the initial state transfer, it just waits for the coordinator to send it a topology before joinComplete is set to TRUE -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9161) Description of StateTransferManager.joinComplete does not match the behaviour

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9161?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9161: ------------------------------- Status: Open (was: New) > Description of StateTransferManager.joinComplete does not match the behaviour > ----------------------------------------------------------------------------- > > Key: ISPN-9161 > URL: https://issues.jboss.org/browse/ISPN-9161 > Project: Infinispan > Issue Type: Bug > Components: Core, Documentation-Core > Reporter: Wolf-Dieter Fink > Assignee: Dan Berindei > Fix For: 9.3.0.CR1 > > > Current description is: > If true, the node has successfully joined the grid and is considered to hold state. If false, the join process is still in progress.. > But the behaviour is: > It doesn't wait for the initial state transfer, it just waits for the coordinator to send it a topology before joinComplete is set to TRUE -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9161) Description of StateTransferManager.joinComplete does not match the behaviour

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9161?page=com.atlassian.jira.plugin.... ] Dan Berindei reassigned ISPN-9161: ---------------------------------- Assignee: Dan Berindei > Description of StateTransferManager.joinComplete does not match the behaviour > ----------------------------------------------------------------------------- > > Key: ISPN-9161 > URL: https://issues.jboss.org/browse/ISPN-9161 > Project: Infinispan > Issue Type: Bug > Reporter: Wolf-Dieter Fink > Assignee: Dan Berindei > > Current description is: > If true, the node has successfully joined the grid and is considered to hold state. If false, the join process is still in progress.. > But the behaviour is: > It doesn't wait for the initial state transfer, it just waits for the coordinator to send it a topology before joinComplete is set to TRUE -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2018