[JBoss JIRA] (ISPN-2402) Cache operations or transactions should never fail with SuspectException
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-2402?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-2402:
--------------------------------
Fix Version/s: 5.3.0.Beta2
(was: 5.3.0.Beta1)
> Cache operations or transactions should never fail with SuspectException
> ------------------------------------------------------------------------
>
> Key: ISPN-2402
> URL: https://issues.jboss.org/browse/ISPN-2402
> Project: Infinispan
> Issue Type: Task
> Components: RPC, State transfer
> Affects Versions: 5.2.0.Beta2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Minor
> Labels: 5.2.x
> Fix For: 5.3.0.Beta2
>
> Attachments: vrstt.log
>
>
> This is an extension of ISPN-1896 of sorts, but for all the cache operations that are visible to the user.
> After a node leaves, the other nodes that have sent commands to that node should either ignore SuspectExceptions or, if not possible, they should retry the operation (e.g. if they didn't get any response back).
> For example, VersionReplStateTransferTest quite often on my machine with a SuspectException, because the versioned prepare command expects a response from the coordinator and the coordinator has just left.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (ISPN-2810) In REST, default values for maxIdleTimeSeconds and timeToLiveSeconds should be 0
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-2810?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-2810:
--------------------------------
Fix Version/s: 5.3.0.Beta2
(was: 5.3.0.Beta1)
> In REST, default values for maxIdleTimeSeconds and timeToLiveSeconds should be 0
> --------------------------------------------------------------------------------
>
> Key: ISPN-2810
> URL: https://issues.jboss.org/browse/ISPN-2810
> Project: Infinispan
> Issue Type: Feature Request
> Components: Remote protocols
> Affects Versions: 5.2.0.Final
> Reporter: Dan Berindei
> Assignee: Galder Zamarreño
> Fix For: 5.3.0.Beta2
>
>
> Contrary to what ISPN-732 says, timeToLiveSeconds=0 and maxIdleTimeSeconds=0 are now treated correctly by the server and the entry is stored in the cache with the default lifespan/maxIdle.
> But if the user PUTs or POSTs an entry and doesn't specify timeToLiveSeconds=0 and maxIdleTimeSeconds=0 explicitly, the entries are stored with infinite lifespan/maxIdle.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months