January 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6677) Deal with unavailable dependencies during startup

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6677?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-6677: ------------------------------------------- Yes, retries are the only option. But I think we should implement reties in Core (this way we could use the same approach for both embedded and client server). WDYT? On Wed, Jan 18, 2017 at 10:27 AM, Gustavo Fernandes (JIRA) <issues(a)jboss.org > Deal with unavailable dependencies during startup > ------------------------------------------------- > > Key: ISPN-6677 > URL: https://issues.jboss.org/browse/ISPN-6677 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Blocker > > In Kubernetes not all Pods start at the same time. It is perfectly possible to start first Infinispan and a bit later the database (in this configuration we are assuming that Infinispan has a dependency to DB). Note that this setup would fails. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6677) Deal with unavailable dependencies during startup

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6677?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-6677: ------------------------------------------- Yes, retries are the only option. But I think we should implement reties in Core (this way we could use the same approach for both embedded and client server). WDYT? > Deal with unavailable dependencies during startup > ------------------------------------------------- > > Key: ISPN-6677 > URL: https://issues.jboss.org/browse/ISPN-6677 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Blocker > > In Kubernetes not all Pods start at the same time. It is perfectly possible to start first Infinispan and a bit later the database (in this configuration we are assuming that Infinispan has a dependency to DB). Note that this setup would fails. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6677) Deal with unavailable dependencies during startup

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6677?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes commented on ISPN-6677: ----------------------------------------- My thoughts on the subject in the blog post http://blog.infinispan.org/2016/12/composing-infinispan-docker-image.html , section " A thing or two about startup order". Hint: retries > Deal with unavailable dependencies during startup > ------------------------------------------------- > > Key: ISPN-6677 > URL: https://issues.jboss.org/browse/ISPN-6677 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Blocker > > In Kubernetes not all Pods start at the same time. It is perfectly possible to start first Infinispan and a bit later the database (in this configuration we are assuming that Infinispan has a dependency to DB). Note that this setup would fails. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7365) Administration console - creating template from existing template fails in some cases

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7365?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic reassigned ISPN-7365: ----------------------------------------- Assignee: Vladimir Blagojevic > Administration console - creating template from existing template fails in some cases > ------------------------------------------------------------------------------------- > > Key: ISPN-7365 > URL: https://issues.jboss.org/browse/ISPN-7365 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Beta1 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Attachments: domain.xml > > > Use the attached configuration file to reproduce. > click on cache container -> configuration -> templates -> add new template -> set name newTemplate and base configuration: replicatedCacheAsTemplate -> click create > Result: > There is an error pop up with empty message "{}" > The template is created but the configuration is not copied. > Note: I'm not sure which part of replicatedCacheAsTemplate configuration is causing this issue, but it's not happening with every template. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6677) Deal with unavailable dependencies during startup

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6677?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6677: -------------------------------------- Priority: Blocker (was: Major) > Deal with unavailable dependencies during startup > ------------------------------------------------- > > Key: ISPN-6677 > URL: https://issues.jboss.org/browse/ISPN-6677 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Blocker > > In Kubernetes not all Pods start at the same time. It is perfectly possible to start first Infinispan and a bit later the database (in this configuration we are assuming that Infinispan has a dependency to DB). Note that this setup would fails. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7367) CommandAckCollector Improvements

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7367?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-7367: ------------------------------------ We can improve the serialization of the address too, by making it implement {{AdvancedExternalizer}} directly instead of extending {{InstanceReusingAdvancedExternalizer}}. > CommandAckCollector Improvements > -------------------------------- > > Key: ISPN-7367 > URL: https://issues.jboss.org/browse/ISPN-7367 > Project: Infinispan > Issue Type: Enhancement > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > > Changes suggested: > * we can have a single {{CommandAckCollector}} per cache manager, since the {{CommandInvocationId}}s are unique. > * It doesn't need the complete {{CommandInvocationId}}. Only the {{long id}} is needed. > Result: > * Smaller payload in acks (no need to send the cache name neither the originator address) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7367) CommandAckCollector Improvements

by Pedro Ruivo (JIRA)

Pedro Ruivo created ISPN-7367: --------------------------------- Summary: CommandAckCollector Improvements Key: ISPN-7367 URL: https://issues.jboss.org/browse/ISPN-7367 Project: Infinispan Issue Type: Enhancement Reporter: Pedro Ruivo Assignee: Pedro Ruivo Changes suggested: * we can have a single {{CommandAckCollector}} per cache manager, since the {{CommandInvocationId}}s are unique. * It doesn't need the complete {{CommandInvocationId}}. Only the {{long id}} is needed. Result: * Smaller payload in acks (no need to send the cache name neither the originator address) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7366) Add trace information to TriangleOrderManager

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-7366?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-7366: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4772 > Add trace information to TriangleOrderManager > --------------------------------------------- > > Key: ISPN-7366 > URL: https://issues.jboss.org/browse/ISPN-7366 > Project: Infinispan > Issue Type: Enhancement > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > > Add trace log information to TriangleOrderManager to help debug issues. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7366) Add trace information to TriangleOrderManager

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-7366?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-7366: ------------------------------ Status: Open (was: New) > Add trace information to TriangleOrderManager > --------------------------------------------- > > Key: ISPN-7366 > URL: https://issues.jboss.org/browse/ISPN-7366 > Project: Infinispan > Issue Type: Enhancement > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > > Add trace log information to TriangleOrderManager to help debug issues. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7366) Add trace information to TriangleOrderManager

by Pedro Ruivo (JIRA)

Pedro Ruivo created ISPN-7366: --------------------------------- Summary: Add trace information to TriangleOrderManager Key: ISPN-7366 URL: https://issues.jboss.org/browse/ISPN-7366 Project: Infinispan Issue Type: Enhancement Reporter: Pedro Ruivo Assignee: Pedro Ruivo Add trace log information to TriangleOrderManager to help debug issues. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 January 2017