Thanks Alexey,
I will consider an option to get familiar more deeply with product and
contribute some patch.
2016-03-04 1:03 GMT+02:00 Alexey Goncharuk :
> Myron,
>
> I believe IGNITE-2645 should be fixed in the near future since the issue
> is critical, and will definitely be included to 1.6.
>
Alexey,
Thanks for advice.
But could you also provide any timelines for listed issues?
2016-03-02 1:14 GMT+02:00 Alexey Goncharuk :
> Oh, I see now what you mean, IGNITE-1018 has escaped my view. Then, until
> IGNITE-1018 is fixed, the only guaranteed approach is to wait on a CDL.
> Here is t
Alexey,
My initial approach was to put reference into NodeLocalMap after "start"
method since I saw no other possibility to do that since I was a little bit
bit confused of - https://issues.apache.org/jira/browse/IGNITE-1018.
But then I tried to go with LifecycleBean but with AFTER_NODE_START.
So
ases?
Finally (since I've touched resource injection chapter), what are the plans
of adding resource injection support for EntryProcessor and nodeLocalMap
initialization/availability (I saw some related issues in Jira)?
Thanks,
2016-02-29 18:20 GMT+02:00 Myron Chelyada :
> Alexey,
>
&
Alexey,
For now, I've only figured out that problem is on node that is joining the
grid and with records/keys for which it becomes primary.
Also I tried different rebalance modes but with no luck. But now I can
confirm that "cacheStore" makes no impact on that (tried to disable
cacheStore and resu
Hello team,
Could you please provide your input on that?
Thanks,
2016-02-25 16:28 GMT+02:00 Myron Chelyada :
> Hello Team,
>
> Looks like I am faced to similar issue in case of cache rebalancing.
> I.e. there are few nodes and cache data are being modified/updated via
> EntryPr
smaller version
than current (will ignore) ...
So, I am wondering is it related to versioning issue described previously
in this thread or is it another (known?) issue or perhaps it is not an
issue at all and I am doing/expecting something wrong?
Thanks,
2016-02-13 9:17 GMT+02:00 Myron Chelyada
Hello team,
In my eviction policy I am trying to check if two EvictableEntry(ies) are
equals.
I expected that such entries are being using on entry's key. After quick
look into the code(i.e. CacheEvictableEntryImpl class) I saw that it is
intended to be so.
But after some testing I observed that i
>
> Thoughts?
>
> Vladimir.
>
> On Mon, Feb 15, 2016 at 10:32 PM, Myron Chelyada > wrote:
>
>> Hello Alexey,
>>
>> This is actually not real code but just extracted part for test. That's
>> why it looks incorrect.
>> And I've already cap
Hello Alexey,
This is actually not real code but just extracted part for test. That's why
it looks incorrect.
And I've already captured infinite loop because of 0 being returned. And
imagine use case when I need to read until end of stream. So question is
why 0 is returned but not -1 (according to
Hello team,
I am faced to issue with putting "Externalizable" value into cache.
I.e. when I am trying to put instance of my custom "externalizable" class
into cache program hangs on put operation.
After some investigation I've figured out that it happens when "put" event
is included.
Test class t
Will try to apply some workaround and looking forward to fix.
2016-02-12 16:58 GMT+02:00 Alexey Goncharuk :
> Myron,
>
> Thank you for reporting the issue. The assertion happens when the value is
> present in the store, absent in the cache and you run invokeAll(). As a
> temporary solution, you c
e not enabled there.
2016-02-11 19:31 GMT+02:00 Myron Chelyada :
> Hi Alexey,
>
> Will try to extract main logic into some test that would allow to
> reproduce it.
> But in meanwhile I figured out that issue appears only on cache that is
> store backed. I.e. as soon as I set
Hi Alexey,
Will try to extract main logic into some test that would allow to reproduce
it.
But in meanwhile I figured out that issue appears only on cache that is
store backed. I.e. as soon as I set either "readThrough" or "writeThrough"
to "false" (or both) issue disappear.
But actually in my cas
Team,
Could you please provide some input on that?
I am blocked since it looks like EntryProcessor can't be used at all (at
least with PARTITIONED cache).
Thanks,
2016-02-09 15:57 GMT+02:00 Myron Chelyada :
> Hmm, doing the same but with:
>
> atomicWriteOrd
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.invokeAll(IgniteCacheProxy.java:1537)
2016-02-09 13:18 GMT+02:00 Myron Chelyada :
> Hi Alexey,
>
> Thanks for reply.
>
> Are there any other similar limitations with modes related to entry
> processor?
> Perhaps there is some detailed documen
Hi Alexey,
Thanks for reply.
Are there any other similar limitations with modes related to entry
processor?
Perhaps there is some detailed documentation (more detailed than I see on
site)?
2016-02-09 12:09 GMT+02:00 Alexey Goncharuk :
> Myron,
>
> This is a known usability issue, see [1]. You n
Hello team,
I am performing concurrent updates on the same entries in cache by using
EntryProcessor.
(Entry processor just sums existing values with provided delta values. I.e.
I have List of doubles as cache value).
And after performing such updates N times I expected to have final values
equal t
18 matches
Mail list logo
