[JBoss JIRA] (ISPN-10990) The Hot Rod server logs warnings about non-tx caches too much
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-10990?page=com.atlassian.jira.plugin... ]
Ryan Emerson resolved ISPN-10990.
---------------------------------
Resolution: Done
> The Hot Rod server logs warnings about non-tx caches too much
> -------------------------------------------------------------
>
> Key: ISPN-10990
> URL: https://issues.jboss.org/browse/ISPN-10990
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.4.16.Final, 10.1.0.Beta1
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.1.0.CR1
>
>
> Certain Hot Rod logs should be logged only once:
> ISPN-006010 Conditional operation '%s' should be used with transactional caches, otherwise data inconsistency issues could arise under failure situations
> ISPN-006011 Operation '%s' forced to return previous value should be used on transactional caches, otherwise data inconsistency issues could arise under failure situations
> ISPN-028024 Not wrapping custom marshaller with media type '%s' since the format is already supported by the server
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (ISPN-11014) Query returns wrong "total_count"
by Jens Reimann (Jira)
[ https://issues.jboss.org/browse/ISPN-11014?page=com.atlassian.jira.plugin... ]
Jens Reimann commented on ISPN-11014:
-------------------------------------
Re-running the query will return the same result over and over again. Also using the HotRod client. Exactly the same result: 9 entries.
{quote}Also, could you tell if you could be deleting data from the cache while simultaneously doing the query? {quote}
I am not sure what you mean by that. The process does 1) query 2) delete. No other process does access the data in the meantime.
> Query returns wrong "total_count"
> ---------------------------------
>
> Key: ISPN-11014
> URL: https://issues.jboss.org/browse/ISPN-11014
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Querying
> Affects Versions: 10.0.1.Final
> Reporter: Jens Reimann
> Assignee: Gustavo Fernandes
> Priority: Major
> Attachments: infinispan.xml
>
>
> Doing a query returns a wrong "total_results" value:
> {code:java}
> oc -n enmasse-infra rsh infinispan-0 curl 'http://app:test12@infinispan-0:11222/rest/v2/caches/devices?action=search...'
> {
> "total_results" : 9,
> "hits" : [ ]
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (ISPN-10997) REST Docs: Minor fixes for productization
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-10997?page=com.atlassian.jira.plugin... ]
Ryan Emerson resolved ISPN-10997.
---------------------------------
Fix Version/s: 10.1.0.CR1
Resolution: Done
> REST Docs: Minor fixes for productization
> -----------------------------------------
>
> Key: ISPN-10997
> URL: https://issues.jboss.org/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
[JBoss JIRA] (ISPN-10966) StateTransferLockImpl.topologyFuture should complete exceptionally after stop
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-10966?page=com.atlassian.jira.plugin... ]
Ryan Emerson resolved ISPN-10966.
---------------------------------
Resolution: Done
> StateTransferLockImpl.topologyFuture should complete exceptionally after stop
> -----------------------------------------------------------------------------
>
> Key: ISPN-10966
> URL: https://issues.jboss.org/browse/ISPN-10966
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 10.1.0.Beta1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.1.0.CR1
>
>
> When a cache is shutting down, the topology id is increased to {{Integer.MAX_VALUE}}.
> If a component uses {{StateTransferLock.topologyUpdate()}} to retry in the next topology and doesn't explicitly check if the cache is running, it could retry 2^^31 times before giving up.
> This causes {{StreamDistPartitionHandlingTest.clearContent}} to hang randomly:
> {noformat}
> 11:58:14,655 TRACE (testng-Test:[]) [StateTransferLockImpl] Signalling topology 2147483647 is installed
> 11:58:14,655 TRACE (testng-Test:[]) [ClusterPublisherManagerImpl] Segments {0-3 8 12 21-22 25-26 29 31 35 37-39 41-42 47 52-54 56-58 73-75 77 85 93-95 97-99 104-105 107 118 121-122 126-129 133 140 145 149 151-154 161 167-168 170-171 177-178 186 189-190 195-196 199-205 212-214 216-217 221-222 224 226-227 232-233 243-244} not completed - retrying
> 11:58:14,655 TRACE (testng-Test:[]) [ClusterPublisherManagerImpl] Retrying segments {0-3 8 12 21-22 25-26 29 31 35 37-39 41-42 47 52-54 56-58 73-75 77 85 93-95 97-99 104-105 107 118 121-122 126-129 133 140 145 149 151-154 161 167-168 170-171 177-178 186 189-190 195-196 199-205 212-214 216-217 221-222 224 226-227 232-233 243-244} after 16 is installed for Test-NodeA-12596#7046
> ...
> 12:03:16,127 TRACE (testng-Test:[]) [ClusterPublisherManagerImpl] Segments {0-3 8 12 21-22 25-26 29 31 35 37-39 41-42 47 52-54 56-58 73-75 77 85 93-95 97-99 104-105 107 118 121-122 126-129 133 140 145 149 151-154 161 167-168 170-171 177-178 186 189-190 195-196 199-205 212-214 216-217 221-222 224 226-227 232-233 243-244} not completed - retrying
> 12:03:16,127 TRACE (testng-Test:[]) [ClusterPublisherManagerImpl] Retrying segments {0-3 8 12 21-22 25-26 29 31 35 37-39 41-42 47 52-54 56-58 73-75 77 85 93-95 97-99 104-105 107 118 121-122 126-129 133 140 145 149 151-154 161 167-168 170-171 177-178 186 189-190 195-196 199-205 212-214 216-217 221-222 224 226-227 232-233 243-244} after 16 is installed for Test-NodeA-12596#7046
> ...
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years