I'm wrong
Correct ticket is https://issues.apache.org/jira/browse/IGNITE-1889
On Wed, Nov 11, 2015 at 3:25 PM, Sergey Kozlov wrote:
> Thanks Andrey for notes!
>
> I've file the ticket https://issues.apache.org/jira/browse/IGNITE-1888
>
>
> On Wed, Nov 11, 2015 at 3:16 PM, Andrey Gura wrote:
>
Sergey Kozlov created IGNITE-1889:
-
Summary: FIFO eviction for atomic cache after removeAll
Key: IGNITE-1889
URL: https://issues.apache.org/jira/browse/IGNITE-1889
Project: Ignite
Issue Type
Thanks Andrey for notes!
I've file the ticket https://issues.apache.org/jira/browse/IGNITE-1888
On Wed, Nov 11, 2015 at 3:16 PM, Andrey Gura wrote:
> Not quite. Actual the following operations sequence lead to this behavior:
>
> 1. put entries
> 2. remove all entries
> 3. put entries
>
> On We
Not quite. Actual the following operations sequence lead to this behavior:
1. put entries
2. remove all entries
3. put entries
On Wed, Nov 11, 2015 at 2:59 PM, Sergey Kozlov wrote:
> It seems this behavior caused removeAll on empty cache executed before
> puts.
>
> On Wed, Nov 11, 2015 at 1:16
It seems this behavior caused removeAll on empty cache executed before puts.
On Wed, Nov 11, 2015 at 1:16 PM, Sergey Kozlov wrote:
> Hi
>
> I've tested some cache configurations with eviction policy and found a bit
> strange behavior.
>
> For instance the cache configuration is following and I w
Hi
I've tested some cache configurations with eviction policy and found a bit
strange behavior.
For instance the cache configuration is following and I want to have only
50 recent entries in cache (swap is disabled):
1. I
