January 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10603) Docs Productization: Partition handling

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10603?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-10603: ------------------------------- Sprint: (was: DataGrid Sprint #39) > Docs Productization: Partition handling > --------------------------------------- > > Key: ISPN-10603 > URL: https://issues.redhat.com/browse/ISPN-10603 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11201) Operator Docs: Final review feedback

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11201?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-11201: ------------------------------- Sprint: (was: DataGrid Sprint #39) > Operator Docs: Final review feedback > ------------------------------------ > > Key: ISPN-11201 > URL: https://issues.redhat.com/browse/ISPN-11201 > Project: Infinispan > Issue Type: Task > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Some review feedback from Galder. Needs backport to 1.1.x. > 1. Remove xsite url. Not implemented. > - name: google > url: xsite://google.host:23456 > 2. backups should say locations > 3. "defines local and backup sites" > 4. In " JVM, CPU, and Memory Resources", can you explain that the cpu/memory set is used to set the pod cpu/memory limits. And also say that in terms of pod cpu requets, it sets half of that. For memory requests, it sets the same as memory limits. https://medium.com/@betz.mark/understanding-resource-limits-in-kubernetes... is a good document that explains the difference between requests and limits > 5. add is "<name>-sites" service to the reference. That's created when x-site is enabled. This is independent of the external service -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11200) Doc Productization: Cache Authorization

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11200?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-11200: ------------------------------- Sprint: (was: DataGrid Sprint #39) > Doc Productization: Cache Authorization > --------------------------------------- > > Key: ISPN-11200 > URL: https://issues.redhat.com/browse/ISPN-11200 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > RHDG 8.0 cache authorization -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11201) Operator Docs: Final review feedback

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11201?page=com.atlassian.jira.plugi... ] Donald Naro closed ISPN-11201. ------------------------------ > Operator Docs: Final review feedback > ------------------------------------ > > Key: ISPN-11201 > URL: https://issues.redhat.com/browse/ISPN-11201 > Project: Infinispan > Issue Type: Task > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Some review feedback from Galder. Needs backport to 1.1.x. > 1. Remove xsite url. Not implemented. > - name: google > url: xsite://google.host:23456 > 2. backups should say locations > 3. "defines local and backup sites" > 4. In " JVM, CPU, and Memory Resources", can you explain that the cpu/memory set is used to set the pod cpu/memory limits. And also say that in terms of pod cpu requets, it sets half of that. For memory requests, it sets the same as memory limits. https://medium.com/@betz.mark/understanding-resource-limits-in-kubernetes... is a good document that explains the difference between requests and limits > 5. add is "<name>-sites" service to the reference. That's created when x-site is enabled. This is independent of the external service -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11201) Operator Docs: Final review feedback

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11201?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-11201: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Operator Docs: Final review feedback > ------------------------------------ > > Key: ISPN-11201 > URL: https://issues.redhat.com/browse/ISPN-11201 > Project: Infinispan > Issue Type: Task > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Some review feedback from Galder. Needs backport to 1.1.x. > 1. Remove xsite url. Not implemented. > - name: google > url: xsite://google.host:23456 > 2. backups should say locations > 3. "defines local and backup sites" > 4. In " JVM, CPU, and Memory Resources", can you explain that the cpu/memory set is used to set the pod cpu/memory limits. And also say that in terms of pod cpu requets, it sets half of that. For memory requests, it sets the same as memory limits. https://medium.com/@betz.mark/understanding-resource-limits-in-kubernetes... is a good document that explains the difference between requests and limits > 5. add is "<name>-sites" service to the reference. That's created when x-site is enabled. This is independent of the external service -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11227) Cluster fails to startup due to initial state transfer timing out

by Johno Crawford (Jira)

[ https://issues.redhat.com/browse/ISPN-11227?page=com.atlassian.jira.plugi... ] Johno Crawford updated ISPN-11227: ---------------------------------- Steps to Reproduce: Reproducing this requires two nodes, node A and node B with zeroCapacityNode set to true. Once node A and B are clustered, node A will hang on restart ( invoking org.infinispan.manager.DefaultCacheManager#getCache(java.lang.String) will result in a initial state timeout in 4 minutes ).. 1. Open the attached project and refresh the Maven project. 2. Start NodeAMain and NodeBMain, wait a few seconds. 3. Restart NodeAMain. was:Reproducing this requires two nodes, node A and node B with zeroCapacityNode set to true. Once node A and B are clustered, node A will hang on restart ( invoking org.infinispan.manager.DefaultCacheManager#getCache(java.lang.String) will result in a initial state timeout in 4 minutes ).. > Cluster fails to startup due to initial state transfer timing out > ----------------------------------------------------------------- > > Key: ISPN-11227 > URL: https://issues.redhat.com/browse/ISPN-11227 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.1.Final > Reporter: Johno Crawford > Priority: Major > Attachments: ISPN11227.zip > > > If a zero capacity node is part of a running cluster and all other nodes are restarted, the nodes will hang on startup. > {code:java} > "ForkJoinPool.commonPool-worker-2@11514" daemon prio=5 tid=0xa3 nid=NA waiting > java.lang.Thread.State: WAITING > at sun.misc.Unsafe.park(Unsafe.java:-1) > at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328) > at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277) > at org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete(StateTransferManagerImpl.java:270) > at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:1091) > at org.infinispan.cache.impl.AbstractDelegatingCache.start(AbstractDelegatingCache.java:513) > at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:693) > at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:632) > at org.infinispan.manager.DefaultCacheManager.internalGetCache(DefaultCacheManager.java:517) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:498) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:491) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11227) Cluster fails to startup due to initial state transfer timing out

by Johno Crawford (Jira)

[ https://issues.redhat.com/browse/ISPN-11227?page=com.atlassian.jira.plugi... ] Johno Crawford commented on ISPN-11227: --------------------------------------- Attaching reproducer. > Cluster fails to startup due to initial state transfer timing out > ----------------------------------------------------------------- > > Key: ISPN-11227 > URL: https://issues.redhat.com/browse/ISPN-11227 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.1.Final > Reporter: Johno Crawford > Priority: Major > Attachments: ISPN11227.zip > > > If a zero capacity node is part of a running cluster and all other nodes are restarted, the nodes will hang on startup. > {code:java} > "ForkJoinPool.commonPool-worker-2@11514" daemon prio=5 tid=0xa3 nid=NA waiting > java.lang.Thread.State: WAITING > at sun.misc.Unsafe.park(Unsafe.java:-1) > at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328) > at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277) > at org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete(StateTransferManagerImpl.java:270) > at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:1091) > at org.infinispan.cache.impl.AbstractDelegatingCache.start(AbstractDelegatingCache.java:513) > at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:693) > at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:632) > at org.infinispan.manager.DefaultCacheManager.internalGetCache(DefaultCacheManager.java:517) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:498) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:491) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11227) Cluster fails to startup due to initial state transfer timing out

by Johno Crawford (Jira)

[ https://issues.redhat.com/browse/ISPN-11227?page=com.atlassian.jira.plugi... ] Johno Crawford updated ISPN-11227: ---------------------------------- Attachment: ISPN11227.zip > Cluster fails to startup due to initial state transfer timing out > ----------------------------------------------------------------- > > Key: ISPN-11227 > URL: https://issues.redhat.com/browse/ISPN-11227 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.1.Final > Reporter: Johno Crawford > Priority: Major > Attachments: ISPN11227.zip > > > If a zero capacity node is part of a running cluster and all other nodes are restarted, the nodes will hang on startup. > {code:java} > "ForkJoinPool.commonPool-worker-2@11514" daemon prio=5 tid=0xa3 nid=NA waiting > java.lang.Thread.State: WAITING > at sun.misc.Unsafe.park(Unsafe.java:-1) > at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328) > at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277) > at org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete(StateTransferManagerImpl.java:270) > at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:1091) > at org.infinispan.cache.impl.AbstractDelegatingCache.start(AbstractDelegatingCache.java:513) > at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:693) > at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:632) > at org.infinispan.manager.DefaultCacheManager.internalGetCache(DefaultCacheManager.java:517) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:498) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:491) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11227) Cluster fails to startup due to initial state transfer timing out

by Johno Crawford (Jira)

Johno Crawford created ISPN-11227: ------------------------------------- Summary: Cluster fails to startup due to initial state transfer timing out Key: ISPN-11227 URL: https://issues.redhat.com/browse/ISPN-11227 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 10.1.1.Final Reporter: Johno Crawford If a zero capacity node is part of a running cluster and all other nodes are restarted, the nodes will hang on startup. {code:java} "ForkJoinPool.commonPool-worker-2@11514" daemon prio=5 tid=0xa3 nid=NA waiting java.lang.Thread.State: WAITING at sun.misc.Unsafe.park(Unsafe.java:-1) at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037) at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328) at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277) at org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete(StateTransferManagerImpl.java:270) at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:1091) at org.infinispan.cache.impl.AbstractDelegatingCache.start(AbstractDelegatingCache.java:513) at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:693) at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:632) at org.infinispan.manager.DefaultCacheManager.internalGetCache(DefaultCacheManager.java:517) at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:498) at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:491) {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10889) Error building infinispan on ppc64le

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-10889?page=com.atlassian.jira.plugi... ] Ryan Emerson commented on ISPN-10889: ------------------------------------- [~dan.berindei] Sure. It would be an easy enough change to https://github.com/infinispan/infinispan-maven-plugins/blob/master/proto-... > Error building infinispan on ppc64le > ------------------------------------ > > Key: ISPN-10889 > URL: https://issues.redhat.com/browse/ISPN-10889 > Project: Infinispan > Issue Type: Bug > Reporter: Rashmi Salgaonkar > Priority: Major > > Apache Maven 3.6.2 > Java version: 11.0.5 > OS: linux-ppc64le > Error building infinispan:- > [INFO] Alternative client marshallers ..................... SKIPPED > [INFO] Infinispan Common Marshaller Test Classes .......... SKIPPED > [INFO] Infinispan Kryo Marshaller Bridge .................. SKIPPED > [INFO] Infinispan Kryo Marshaller Bridge Bundle ........... SKIPPED > [INFO] Infinispan Protostuff Marshaller Bridge ............ SKIPPED > [INFO] Infinispan Protostuff Marshaller Bridge Bundle ..... SKIPPED > [INFO] Infinispan Hibernate 5.1 Cache ..................... SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 48.824 s > [INFO] Finished at: 2019-11-01T10:46:39Z > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.infinispan.maven-plugins:proto-schema-compatibility:1.0.1.Final:proto-schema-compatibility-check (default) on project infinispan-commons: *OS not supported. Unable to find a protolock binary for the classifier linux-ppcle_64 *-> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the command > [ERROR] mvn <args> -rf :infinispan-commons > bash-4.4# > I was able to build https://github.com/infinispan/infinispan-maven-plugins repo. > I need details on how I can generate the architecture specific protolock binary file. > https://github.com/infinispan/infinispan-maven-plugins/tree/master/proto-... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2020