December 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3748) Add additional server functionality around Remote Query

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3748?page=com.atlassian.jira.plugin.... ] Adrian Nistor reassigned ISPN-3748: ----------------------------------- Assignee: Adrian Nistor (was: Mircea Markus) > Add additional server functionality around Remote Query > ------------------------------------------------------- > > Key: ISPN-3748 > URL: https://issues.jboss.org/browse/ISPN-3748 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 6.0.0.Final > Reporter: William Burns > Assignee: Adrian Nistor > > ISPN-3587 added very minimal support for remote query in the server. > There are quite a few changes that are hoped will go into remote query in infinispan. > # ISPN-3480 should make deployments easier (currently we are limited to URL only - could use string passing the protoc contents instead). > # persistence (allow for added definitions to persist between restarts) > # preload (allow for xml definition in server) > More info on some of these can be found here [1] as well > [1] https://community.jboss.org/message/844268?et=watches.email.thread#844268 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-1239) Graceful shutdown should be supported

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-1239?page=com.atlassian.jira.plugin.... ] Radim Vansa commented on ISPN-1239: ----------------------------------- Shouldn't this be closed as well? > Graceful shutdown should be supported > ------------------------------------- > > Key: ISPN-1239 > URL: https://issues.jboss.org/browse/ISPN-1239 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Affects Versions: 5.0.0.FINAL > Reporter: Manik Surtani > Assignee: Dan Berindei > Priority: Critical > Labels: clean_shutdown, rehashing > > Currently, killing any node will result in a rehash. A mechanism for clean shutdown should also be supported, so that a rehash is *not* triggered. Useful when the entire cluster is being intentionally brought down. > Need to think about how we do this; perhaps a LEAVE message that will prevent nodes triggering a rehash when a subsequent view change is detected. This could be done programmatically via a {{clean}} parameter to {{stop()}}, but we should explore alternatives here. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-1239) Graceful shutdown should be supported

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-1239?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated ISPN-1239: --------------------------------- Comment: was deleted (was: Ladislav Thon <lthon(a)redhat.com> made a comment on [bug 919399|https://bugzilla.redhat.com/show_bug.cgi?id=919399] Update from EAP 6.1.0.ER8 testing cycle: This issue was not seen during this cycle. This can mean that it was either fixed unintentionally (maybe as a by-product of the Infinispan upgrade to 5.2.6.Final) or this issue just became rarer. Either way, we decided not to close this issue.) > Graceful shutdown should be supported > ------------------------------------- > > Key: ISPN-1239 > URL: https://issues.jboss.org/browse/ISPN-1239 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Affects Versions: 5.0.0.FINAL > Reporter: Manik Surtani > Assignee: Dan Berindei > Priority: Critical > Labels: clean_shutdown, rehashing > > Currently, killing any node will result in a rehash. A mechanism for clean shutdown should also be supported, so that a rehash is *not* triggered. Useful when the entire cluster is being intentionally brought down. > Need to think about how we do this; perhaps a LEAVE message that will prevent nodes triggering a rehash when a subsequent view change is detected. This could be done programmatically via a {{clean}} parameter to {{stop()}}, but we should explore alternatives here. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-1239) Graceful shutdown should be supported

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-1239?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated ISPN-1239: --------------------------------- Comment: was deleted (was: Paul Ferraro <paul.ferraro(a)redhat.com> made a comment on [bug 919399|https://bugzilla.redhat.com/show_bug.cgi?id=919399] Does not appear to be an issue anymore.) > Graceful shutdown should be supported > ------------------------------------- > > Key: ISPN-1239 > URL: https://issues.jboss.org/browse/ISPN-1239 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Affects Versions: 5.0.0.FINAL > Reporter: Manik Surtani > Assignee: Dan Berindei > Priority: Critical > Labels: clean_shutdown, rehashing > > Currently, killing any node will result in a rehash. A mechanism for clean shutdown should also be supported, so that a rehash is *not* triggered. Useful when the entire cluster is being intentionally brought down. > Need to think about how we do this; perhaps a LEAVE message that will prevent nodes triggering a rehash when a subsequent view change is detected. This could be done programmatically via a {{clean}} parameter to {{stop()}}, but we should explore alternatives here. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-1239) Graceful shutdown should be supported

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-1239?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated ISPN-1239: --------------------------------- Comment: was deleted (was: Radoslav Husar <rhusar(a)redhat.com> changed the Status of [bug 919399|https://bugzilla.redhat.com/show_bug.cgi?id=919399] from NEW to CLOSED) > Graceful shutdown should be supported > ------------------------------------- > > Key: ISPN-1239 > URL: https://issues.jboss.org/browse/ISPN-1239 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Affects Versions: 5.0.0.FINAL > Reporter: Manik Surtani > Assignee: Dan Berindei > Priority: Critical > Labels: clean_shutdown, rehashing > > Currently, killing any node will result in a rehash. A mechanism for clean shutdown should also be supported, so that a rehash is *not* triggered. Useful when the entire cluster is being intentionally brought down. > Need to think about how we do this; perhaps a LEAVE message that will prevent nodes triggering a rehash when a subsequent view change is detected. This could be done programmatically via a {{clean}} parameter to {{stop()}}, but we should explore alternatives here. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-1239) Graceful shutdown should be supported

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-1239?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated ISPN-1239: --------------------------------- Comment: was deleted (was: A comment with security level 'JBoss Employee' was removed.) > Graceful shutdown should be supported > ------------------------------------- > > Key: ISPN-1239 > URL: https://issues.jboss.org/browse/ISPN-1239 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Affects Versions: 5.0.0.FINAL > Reporter: Manik Surtani > Assignee: Dan Berindei > Priority: Critical > Labels: clean_shutdown, rehashing > > Currently, killing any node will result in a rehash. A mechanism for clean shutdown should also be supported, so that a rehash is *not* triggered. Useful when the entire cluster is being intentionally brought down. > Need to think about how we do this; perhaps a LEAVE message that will prevent nodes triggering a rehash when a subsequent view change is detected. This could be done programmatically via a {{clean}} parameter to {{stop()}}, but we should explore alternatives here. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2445) Graceful shutdown - transfer data to other nodes

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-2445?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated ISPN-2445: --------------------------------- Summary: Graceful shutdown - transfer data to other nodes (was: Gracefull shutdown - transfer data to other nodes) > Graceful shutdown - transfer data to other nodes > ------------------------------------------------ > > Key: ISPN-2445 > URL: https://issues.jboss.org/browse/ISPN-2445 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Reporter: Matej Lazar > Assignee: Mircea Markus > > Distributed cache should provide an configuration option to block shutdown until data from shutting down node is transferred to other nodes. > This feature is useful if Infinispan is used as persistent storage. > Without this option, in a cloud environment, where server node is deleted on scale down event, users are forced to use external storage, if they don't want to loose data. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3327) Server init.d script should be customized for Infinispan

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3327?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3327: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 6.1.0.Final (was: 6.0.0.Alpha4) Resolution: Done > Server init.d script should be customized for Infinispan > -------------------------------------------------------- > > Key: ISPN-3327 > URL: https://issues.jboss.org/browse/ISPN-3327 > Project: Infinispan > Issue Type: Bug > Reporter: NadirX > Assignee: Tristan Tarrant > Labels: 620 > Fix For: 6.1.0.Final > > > The current init.d script included in Infinispan Server should be appropriately renamed and verified -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3827) JON server plugin is NOT imported into JON properly

by Tomas Sykora (JIRA)

[ https://issues.jboss.org/browse/ISPN-3827?page=com.atlassian.jira.plugin.... ] Tomas Sykora edited comment on ISPN-3827 at 12/13/13 5:01 AM: -------------------------------------------------------------- Thank you very much for info! I had some difficulties with step 7. I will verify it once more, but it seems it will be working and this JIRA looks like false alarm. Uhm, just got an info that there might be some difficulties from JON side. I suppose I have met one of them. was (Author: tsykora): Thank you very much for info! I had some difficulties with step 7. I will verify it once more, but it seems it will be working and this JIRA looks like false alarm. > JON server plugin is NOT imported into JON properly > --------------------------------------------------- > > Key: ISPN-3827 > URL: https://issues.jboss.org/browse/ISPN-3827 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 6.0.0.Final > Reporter: Tomas Sykora > Assignee: William Burns > Labels: 620 > > See linked bugzilla. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3827) JON server plugin is NOT imported into JON properly

by Tomas Sykora (JIRA)

[ https://issues.jboss.org/browse/ISPN-3827?page=com.atlassian.jira.plugin.... ] Tomas Sykora commented on ISPN-3827: ------------------------------------ Thank you very much for info! I had some difficulties with step 7. I will verify it once more, but it seems it will be working and this JIRA looks like false alarm. > JON server plugin is NOT imported into JON properly > --------------------------------------------------- > > Key: ISPN-3827 > URL: https://issues.jboss.org/browse/ISPN-3827 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 6.0.0.Final > Reporter: Tomas Sykora > Assignee: William Burns > Labels: 620 > > See linked bugzilla. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2013