[JBoss JIRA] (ISPN-10664) Expiration should not be replicated cross site
by Pedro Ruivo (Jira)
Pedro Ruivo created ISPN-10664:
----------------------------------
Summary: Expiration should not be replicated cross site
Key: ISPN-10664
URL: https://issues.jboss.org/browse/ISPN-10664
Project: Infinispan
Issue Type: Bug
Components: Cross-Site Replication, Expiration
Affects Versions: 9.4.16.Final, 10.0.0.CR2
Reporter: Will Burns
Assignee: Will Burns
Fix For: 10.0.0.CR3, 9.4.17.Final
There is no reason currently to replicate expiration commands across site.
Lifespan will work just fine without without replicating as the entry is expired on either side properly, irrespective of system clocks.
However max idle doesn't support the given semantics with xsite. We currently only confirm from other nodes in the same cluster for max idle before removing. It would be extremely costly to query all the cross sites to see if they have a read on the same entry before expiring. Also this requires having system clocks somewhat close in time, which can be even more problematic with clusters in disparate locations. We need to document that this doesn't work as well.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (ISPN-10662) Metrict for evictions does not count entries but memory bytes if <off-heap> is used
by Wolf-Dieter Fink (Jira)
Wolf-Dieter Fink created ISPN-10662:
---------------------------------------
Summary: Metrict for evictions does not count entries but memory bytes if <off-heap> is used
Key: ISPN-10662
URL: https://issues.jboss.org/browse/ISPN-10662
Project: Infinispan
Issue Type: Bug
Reporter: Wolf-Dieter Fink
Assignee: Will Burns
Configuration with off-heap
<cache-container name="clustered" default-cache="ExpirationCache" statistics="true">
<transport lock-timeout="60000"/>
<global-state/>
<distributed-cache name="ExpirationCache">
<memory>
<off-heap eviction="COUNT" size="120"/>
</memory>
</distributed-cache>
Any eviction will increase the counter evictions not by 1 for entry but by a value which seems the amount of bytes.
<object> or <binary> configuration work as expected
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (ISPN-10661) Avoid blocking IO threads on CacheInputStream
by Gustavo Fernandes (Jira)
[ https://issues.jboss.org/browse/ISPN-10661?page=com.atlassian.jira.plugin... ]
Gustavo Fernandes updated ISPN-10661:
-------------------------------------
Description:
As part of ISPN-10376, the REST server is serving keys using Netty's {{ChunkedWriteHandler}} that will convert a InputStream into chunks and will write it to the client.
As the source of the InputStream is a CacheStream, that can block, it's desirable to do the retrieval of the cache data in a separate thread, using the suspend and resume capabilities of the {{ChunkedWriteHandler}} when data is available
[https://netty.io/4.0/api/io/netty/handler/stream/ChunkedWriteHandler.html...]
was:
As part of ISPN-10376, the REST server is serving keys using Netty's {{ChunkedWriteHandler}} that will convert a InputStream into chunks and will write it to the client.
As the source of the InputStream is a CacheStream, that can block, it's desirable to do the retrieval of the cache data in a separate thread, using the suspend and resume capabilities of the {{ChunkedWriteHandler}} when data is available
https://netty.io/4.0/api/io/netty/handler/strea/ChunkedWriteHandler.html#...
> Avoid blocking IO threads on CacheInputStream
> ---------------------------------------------
>
> Key: ISPN-10661
> URL: https://issues.jboss.org/browse/ISPN-10661
> Project: Infinispan
> Issue Type: Enhancement
> Components: REST
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> As part of ISPN-10376, the REST server is serving keys using Netty's {{ChunkedWriteHandler}} that will convert a InputStream into chunks and will write it to the client.
> As the source of the InputStream is a CacheStream, that can block, it's desirable to do the retrieval of the cache data in a separate thread, using the suspend and resume capabilities of the {{ChunkedWriteHandler}} when data is available
> [https://netty.io/4.0/api/io/netty/handler/stream/ChunkedWriteHandler.html...]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (ISPN-10661) Avoid blocking on CacheInputStream
by Gustavo Fernandes (Jira)
Gustavo Fernandes created ISPN-10661:
----------------------------------------
Summary: Avoid blocking on CacheInputStream
Key: ISPN-10661
URL: https://issues.jboss.org/browse/ISPN-10661
Project: Infinispan
Issue Type: Enhancement
Components: REST
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
As part of ISPN-10376, the REST server is serving keys using Netty's {{ChunkedWriteHandler}} that will convert a InputStream into chunks and will write it to the client.
As the source of the InputStream is a CacheStream, that can block, it's desirable to do the retrieval of the cache data in a separate thread, using the suspend and resume capabilities of the {{ChunkedWriteHandler}} when data is available
https://netty.io/4.0/api/io/netty/handler/strea/ChunkedWriteHandler.html#...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years