[JBoss JIRA] (ISPN-10997) REST Docs: Minor fixes for productization
by Donald Naro (Jira)
[ https://issues.redhat.com/browse/ISPN-10997?page=com.atlassian.jira.plugi... ]
Donald Naro closed ISPN-10997.
------------------------------
> REST Docs: Minor fixes for productization
> -----------------------------------------
>
> Key: ISPN-10997
> URL: https://issues.redhat.com/browse/ISPN-10997
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Minor
> Fix For: 10.1.0.CR1
>
>
> Some errors related to invalid anchors and references appear in the logs for docs tooling. Simple fixes to clean these up.
> asciidoctor: ERROR: stories/topics/ref_rest_caches.adoc: line 29: include file not found: ../topics/topics/ref_xml_configuration.adoc
> asciidoctor: ERROR: stories/topics/ref_rest_caches.adoc: line 30: include file not found: ../topics/topics/ref_json_configuration.adoc
> Error: no ID for constraint linkend: "rest_accept".
> XLink to nonexistent id: rest_accept
> Error: no ID for constraint linkend: "rest_key_content_type".
> XLink to nonexistent id: rest_key_content_type
> Error: no ID for constraint linkend: "rest_key_content_type".
> XLink to nonexistent id: rest_key_content_type
> Error: no ID for constraint linkend: "rest_accept".
> XLink to nonexistent id: rest_accept
> Error: no ID for constraint linkend: "rest_key_content_type".
> XLink to nonexistent id: rest_key_content_type
> Error: no ID for constraint linkend: "rest_key_content_type".
> XLink to nonexistent id: rest_key_content_type
> Error: no ID for constraint linkend: "rest_accept".
> XLink to nonexistent id: rest_accept
> Error: no ID for constraint linkend: "rest_accept".
> XLink to nonexistent id: rest_accept
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10882) Remove the warn message ISPN000026: Caught exception purging data container
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-10882?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-10882:
--------------------------------
Issue Type: Bug (was: Enhancement)
> Remove the warn message ISPN000026: Caught exception purging data container
> ---------------------------------------------------------------------------
>
> Key: ISPN-10882
> URL: https://issues.redhat.com/browse/ISPN-10882
> Project: Infinispan
> Issue Type: Bug
> Reporter: Diego Lovison
> Priority: Major
>
> When the node1 is leaving the cluster we could have the following warn message:
> {noformat}
> [0m[33m18:43:28,387 WARN [org.infinispan.expiration.impl.ClusterExpirationManager] (expiration-thread--p7-t1) ISPN000026: Caught exception purging data container!: java.lang.IllegalArgumentException: Node edg-perf01-2556 is not a member
> at org.infinispan.distribution.ch.impl.DefaultConsistentHash.getPrimarySegmentsForOwner(DefaultConsistentHash.java:128)
> at org.infinispan.distribution.group.impl.PartitionerConsistentHash.getPrimarySegmentsForOwner(PartitionerConsistentHash.java:76)
> at org.infinispan.expiration.impl.ClusterExpirationManager.purgeInMemoryContents(ClusterExpirationManager.java:123)
> at org.infinispan.expiration.impl.ClusterExpirationManager.processExpiration(ClusterExpirationManager.java:98)
> at org.infinispan.expiration.impl.ExpirationManagerImpl$ScheduledTask.run(ExpirationManagerImpl.java:282)
> at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
> at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
> at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {noformat}
> Dan added the following comments:
> {noformat}
> Dan: but I think it can actually happen during start and/or after a merge
> Dan: when joining, the first cache topology usually doesn't have the joiner as a member
> Dan: after a merge as well, nodes that are not in the majority partition will receive a cache topology in which they are not members
> Dan: luckily StateConsumerImpl clears the data container and private stores after receiving that cache topology anyway, so there's nothing to expire
> Dan: and after the node becomes a full member again expiration will work
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10882) Remove the warn message ISPN000026: Caught exception purging data container
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-10882?page=com.atlassian.jira.plugi... ]
Dan Berindei reassigned ISPN-10882:
-----------------------------------
Assignee: Dan Berindei
> Remove the warn message ISPN000026: Caught exception purging data container
> ---------------------------------------------------------------------------
>
> Key: ISPN-10882
> URL: https://issues.redhat.com/browse/ISPN-10882
> Project: Infinispan
> Issue Type: Bug
> Reporter: Diego Lovison
> Assignee: Dan Berindei
> Priority: Major
>
> When the node1 is leaving the cluster we could have the following warn message:
> {noformat}
> [0m[33m18:43:28,387 WARN [org.infinispan.expiration.impl.ClusterExpirationManager] (expiration-thread--p7-t1) ISPN000026: Caught exception purging data container!: java.lang.IllegalArgumentException: Node edg-perf01-2556 is not a member
> at org.infinispan.distribution.ch.impl.DefaultConsistentHash.getPrimarySegmentsForOwner(DefaultConsistentHash.java:128)
> at org.infinispan.distribution.group.impl.PartitionerConsistentHash.getPrimarySegmentsForOwner(PartitionerConsistentHash.java:76)
> at org.infinispan.expiration.impl.ClusterExpirationManager.purgeInMemoryContents(ClusterExpirationManager.java:123)
> at org.infinispan.expiration.impl.ClusterExpirationManager.processExpiration(ClusterExpirationManager.java:98)
> at org.infinispan.expiration.impl.ExpirationManagerImpl$ScheduledTask.run(ExpirationManagerImpl.java:282)
> at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
> at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
> at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {noformat}
> Dan added the following comments:
> {noformat}
> Dan: but I think it can actually happen during start and/or after a merge
> Dan: when joining, the first cache topology usually doesn't have the joiner as a member
> Dan: after a merge as well, nodes that are not in the majority partition will receive a cache topology in which they are not members
> Dan: luckily StateConsumerImpl clears the data container and private stores after receiving that cache topology anyway, so there's nothing to expire
> Dan: and after the node becomes a full member again expiration will work
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-11043) Upgrade to infinispan doclets 1.2.1.Final and use DocletMultiplexer to exclude non-API elements
by Nistor Adrian (Jira)
[ https://issues.redhat.com/browse/ISPN-11043?page=com.atlassian.jira.plugi... ]
Nistor Adrian updated ISPN-11043:
---------------------------------
Summary: Upgrade to infinispan doclets 1.2.1.Final and use DocletMultiplexer to exclude non-API elements (was: Upgrade to infinispan doclets 1.2.0.Final and use DocletMultiplexer to exclude non-API elements)
> Upgrade to infinispan doclets 1.2.1.Final and use DocletMultiplexer to exclude non-API elements
> -----------------------------------------------------------------------------------------------
>
> Key: ISPN-11043
> URL: https://issues.redhat.com/browse/ISPN-11043
> Project: Infinispan
> Issue Type: Enhancement
> Components: JMX, reporting and management
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.1.0.CR1
>
>
> The JmxDoclet and StandardDoclet should be run by the multiplexer rather than separately.
> The non-API elements should be excluded from processing of standard doclet but not from jmx components doc.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months