[JBoss JIRA] (ISPN-9707) Getting keys via REST fails with SerializationException
by Katia Aresti (Jira)
[ https://issues.jboss.org/browse/ISPN-9707?page=com.atlassian.jira.plugin.... ]
Katia Aresti updated ISPN-9707:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Getting keys via REST fails with SerializationException
> -------------------------------------------------------
>
> Key: ISPN-9707
> URL: https://issues.jboss.org/browse/ISPN-9707
> Project: Infinispan
> Issue Type: Bug
> Components: REST
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> Obtaining all the keys from a cache, e.g.: http://192.168.1.7:8080/rest/my_default_cache causes errors for clustered servers:
> {noformat}
> ERROR [org.infinispan.remoting.rpc.RpcManagerImpl] (REST-ServerWorker-4-5) ISPN000073: Unexpected error while replicating:
> org.infinispan.commons.marshall.NotSerializableException: org.infinispan.rest.operations.mediatypes.impl.TextOutputPrinter
> Caused by: an exception which occurred:
> in field capturedArgs
> in object org.infinispan.rest.operations.mediatypes.impl.TextOutputPrinter$$Lambda$495/1513688834@5bc665d
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9749) Rest PUT fails to replace value when storing pojos without equality
by Katia Aresti (Jira)
[ https://issues.jboss.org/browse/ISPN-9749?page=com.atlassian.jira.plugin.... ]
Katia Aresti updated ISPN-9749:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Rest PUT fails to replace value when storing pojos without equality
> -------------------------------------------------------------------
>
> Key: ISPN-9749
> URL: https://issues.jboss.org/browse/ISPN-9749
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.2.4.Final, 9.3.5.Final, 9.4.1.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> According to the documentations, when doing a REST PUT, "Any existing data will be replaced", but when the cache is configured to store "application/x-java-object" (unserialized objects) and the object does not implement the equals method, the replace always fails and the server returns HTTP 412 (precondition failed).
> This is due to the fact that internally the REST server first retrieves the existing value, and then does a conditional replace with this value that never matches.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-1195) Rehashing and state transfer to use digesting
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-1195?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-1195:
----------------------------------
Component/s: Cross-Site Replication
> Rehashing and state transfer to use digesting
> ---------------------------------------------
>
> Key: ISPN-1195
> URL: https://issues.jboss.org/browse/ISPN-1195
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core, Cross-Site Replication, State Transfer
> Reporter: Manik Surtani
> Assignee: Dan Berindei
> Priority: Critical
> Labels: rehash, state_transfer, versioning
>
> Rather than pushing entire state to new joiners, a mechanism of digests should be used to minimise network transfers. For example, Merkle trees can be used to determine which entries are out of date and need pushing, in the case of nodes that persist to a local cache store, and is restarted but still has access to some state on disk.
> This would require versioned entries though.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-1195) Rehashing and state transfer to use digesting
by Sanne Grinovero (Jira)
[ https://issues.jboss.org/browse/ISPN-1195?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero reassigned ISPN-1195:
-------------------------------------
Assignee: Dan Berindei
> Rehashing and state transfer to use digesting
> ---------------------------------------------
>
> Key: ISPN-1195
> URL: https://issues.jboss.org/browse/ISPN-1195
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core, State Transfer
> Reporter: Manik Surtani
> Assignee: Dan Berindei
> Priority: Critical
> Labels: rehash, state_transfer, versioning
>
> Rather than pushing entire state to new joiners, a mechanism of digests should be used to minimise network transfers. For example, Merkle trees can be used to determine which entries are out of date and need pushing, in the case of nodes that persist to a local cache store, and is restarted but still has access to some state on disk.
> This would require versioned entries though.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-8412) Conflict resolution should utilise Merkle trees to improve performance
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-8412?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8412:
----------------------------------
Component/s: State Transfer
> Conflict resolution should utilise Merkle trees to improve performance
> ----------------------------------------------------------------------
>
> Key: ISPN-8412
> URL: https://issues.jboss.org/browse/ISPN-8412
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core, State Transfer
> Affects Versions: 9.2.0.Alpha1
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
>
> Currently we detect conflicts between CacheEntry replicas by retrieving all entries for a cache segment and comparing their values on the node initiating the conflict resolution. This does not scale. Instead, we should generate a Merkle tree for each segment on the replica nodes. When initiating conflict resolution, it is then possible to retrieve a segments hash from each of its owners and determine if a conflict is present before requesting the conflicting entries.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months