March 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10039) Create a cluster without defining cluster size, default should be 1 node

by Vittorio Rigamonti (Jira)

Vittorio Rigamonti created ISPN-10039: ----------------------------------------- Summary: Create a cluster without defining cluster size, default should be 1 node Key: ISPN-10039 URL: https://issues.jboss.org/browse/ISPN-10039 Project: Infinispan Issue Type: Feature Request Components: Operator Reporter: Vittorio Rigamonti Assignee: Vittorio Rigamonti All the int32 fields non specified in the .yaml file are defaulted to 0. The code to default to 1 the spec.size field can be easily added. The side effect of this is that the spec.size field cannot be 0 neither if explicitly set in the yaml. The 0 value could be used for a clean shoutdown of the StatefulSet, see [here|https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#limitations]. Is this ok? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10027) Operator README and repo docs

by Don Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10027?page=com.atlassian.jira.plugin... ] Don Naro updated ISPN-10027: ---------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan-operator/pull/30 > Operator README and repo docs > ----------------------------- > > Key: ISPN-10027 > URL: https://issues.jboss.org/browse/ISPN-10027 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Reporter: Don Naro > Assignee: Don Naro > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10027) Operator README and repo docs

by Don Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10027?page=com.atlassian.jira.plugin... ] Work on ISPN-10027 started by Don Naro. --------------------------------------- > Operator README and repo docs > ----------------------------- > > Key: ISPN-10027 > URL: https://issues.jboss.org/browse/ISPN-10027 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Reporter: Don Naro > Assignee: Don Naro > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10027) Operator README and repo docs

by Don Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10027?page=com.atlassian.jira.plugin... ] Don Naro updated ISPN-10027: ---------------------------- Status: Open (was: New) > Operator README and repo docs > ----------------------------- > > Key: ISPN-10027 > URL: https://issues.jboss.org/browse/ISPN-10027 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Reporter: Don Naro > Assignee: Don Naro > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10038) Console counters unable to correctly display all long values

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-10038: ----------------------------------- Summary: Console counters unable to correctly display all long values Key: ISPN-10038 URL: https://issues.jboss.org/browse/ISPN-10038 Project: Infinispan Issue Type: Bug Components: Clustered Counter, Console Affects Versions: 9.4.9.Final, 10.0.0.Beta2 Reporter: Ryan Emerson Assignee: Ryan Emerson Currently the console is unable to display all possible counter values, as the max integer that can be represented by javascript is (2^53)-1, whereas Java is (2^63)-1. Normally the workaround for this would be to simply store the number as a String, however the counter value is returned as a number in the returned JSON, so it is automatically parsed as a number by the console and the exact value is lost. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10036) Setting Up Infinispan Operator Docs

by Don Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10036?page=com.atlassian.jira.plugin... ] Don Naro updated ISPN-10036: ---------------------------- Summary: Setting Up Infinispan Operator Docs (was: Infinispan Operator Docs) > Setting Up Infinispan Operator Docs > ----------------------------------- > > Key: ISPN-10036 > URL: https://issues.jboss.org/browse/ISPN-10036 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core, Website > Reporter: Don Naro > Assignee: Don Naro > Priority: Major > > # Set up docs under `infinispan-operator/documentation/asciidoc` > # Update infinispan.github.io scripts to build Operator docs on infinispan.org. > Result should be that documentation for the Infinispan Operator is built and correctly formatted on infinispan.org. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10037) Create 0.2 Docs for the Infinispan Operator

by Don Naro (Jira)

Don Naro created ISPN-10037: ------------------------------- Summary: Create 0.2 Docs for the Infinispan Operator Key: ISPN-10037 URL: https://issues.jboss.org/browse/ISPN-10037 Project: Infinispan Issue Type: Enhancement Components: Documentation-Core Reporter: Don Naro Assignee: Don Naro Define and develop a set of titles based on customer use cases for the Infinispan operator. Docs should be sourced as modular asciidoc under infinispan-operator/documentation/asciidoc -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10036) Infinispan Operator Docs

by Don Naro (Jira)

Don Naro created ISPN-10036: ------------------------------- Summary: Infinispan Operator Docs Key: ISPN-10036 URL: https://issues.jboss.org/browse/ISPN-10036 Project: Infinispan Issue Type: Enhancement Components: Documentation-Core, Website Reporter: Don Naro Assignee: Don Naro # Set up docs under `infinispan-operator/documentation/asciidoc` # Update infinispan.github.io scripts to build Operator docs on infinispan.org. Result should be that documentation for the Infinispan Operator is built and correctly formatted on infinispan.org. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9852) Invocations waiting for a new topology should resume in parallel

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9852?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9852: ------------------------------- Fix Version/s: 10.0.0.Beta3 9.4.10.Final > Invocations waiting for a new topology should resume in parallel > ---------------------------------------------------------------- > > Key: ISPN-9852 > URL: https://issues.jboss.org/browse/ISPN-9852 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.0.0.Alpha2, 9.4.5.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta3, 9.4.10.Final > > > When a command requires a topology newer than the current topology, it uses {{StateTransferLock.transactionDataFuture()}} to wait for the newer topology. When the tx data is received for the newer topology, some (most?) of the waiting operations do not use a separate executor, instead they are all resumed on the thread that received the tx data. If some operations block (e.g. because of a store), it could take a very long time to finish all the blocked operations. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9852) Invocations waiting for a new topology should resume in parallel

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9852?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-9852: ------------------------------------ It shouldn't be {{StateTransferLock}}'s job to resume invocations in parallel, it should be the caller: {{StateTransferInterceptor}} already uses {{thenRunAsync(remoteExecutor}}, but {{DefaultTopologyRunnable}}/{{BaseBlockingRunnable}} use {{whenComplete()}}. > Invocations waiting for a new topology should resume in parallel > ---------------------------------------------------------------- > > Key: ISPN-9852 > URL: https://issues.jboss.org/browse/ISPN-9852 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.0.0.Alpha2, 9.4.5.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > > When a command requires a topology newer than the current topology, it uses {{StateTransferLock.transactionDataFuture()}} to wait for the newer topology. When the tx data is received for the newer topology, some (most?) of the waiting operations do not use a separate executor, instead they are all resumed on the thread that received the tx data. If some operations block (e.g. because of a store), it could take a very long time to finish all the blocked operations. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2019