I think it is just H2 wrapper for string values.
On Tue, Feb 21, 2017 at 8:21 AM, Anil wrote:
> Thanks Andrey.
>
> I see node is down even gc log looks good. I will try to reproduce.
>
> May I know what is the org.h2.value.ValueString objects in the attached the
> screenshot
Anil,
No, it doesn't. Only client should left topology in this case.
On Mon, Feb 20, 2017 at 3:44 PM, Anil wrote:
> Hi Andrey,
>
> Does client ignite gc impact ignite cluster topology ?
>
> Thanks
>
> On 17 February 2017 at 22:56, Andrey Gura wrote:
>>
>>
Hi Andrey,
Does client ignite gc impact ignite cluster topology ?
Thanks
On 17 February 2017 at 22:56, Andrey Gura wrote:
> From GC logs at the end of files I see Full GC pauses like this:
>
> 2017-02-17T04:29:22.118-0800: 21122.643: [Full GC (Allocation Failure)
>
>From GC logs at the end of files I see Full GC pauses like this:
2017-02-17T04:29:22.118-0800: 21122.643: [Full GC (Allocation Failure)
10226M->8526M(10G), 26.8952036 secs]
[Eden: 0.0B(512.0M)->0.0B(536.0M) Survivors: 0.0B->0.0B Heap:
10226.0M(10.0G)->8526.8M(10.0G)], [Metaspace:
Hi Andrey,
I checked GClogs and everything looks good.
Thanks
On 17 February 2017 at 20:45, Andrey Gura wrote:
> Anil,
>
> IGNITE-4003 isn't related with your problem.
>
> I think that nodes are going out of topology due to long GC pauses.
> You can easily check this using
Anil,
IGNITE-4003 isn't related with your problem.
I think that nodes are going out of topology due to long GC pauses.
You can easily check this using GC logs.
On Fri, Feb 17, 2017 at 6:04 PM, Anil wrote:
> Hi,
>
> We noticed whenever long running queries fired, nodes are
Hi,
We noticed whenever long running queries fired, nodes are going out of
topology and entire ignite cluster is down.
In my case, a filter criteria could get 5L records. So each API request
could fetch 250 records. When page number is getting increased the query
execution time is high and
Anil,
Take a look at lifecycle beans:
https://apacheignite.readme.io/docs/ignite-life-cycle
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Cache-stopped-tp9503p10253.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi Alexandr,
ignite stop is not actual node failure in this case. isn't it ? how node
singleton helps in this case ? Am i missing anything?
is there any way to intercept cache start and stop ?
Thanks.
On 16 December 2016 at 15:51, Alexandr Kuramshin
wrote:
> Hi Anil,
>
Hi Anil,
Right, you get stopping the node by the cause of segmentation.
Call chain:
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.DiscoveryWorker#onSegmentation
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager#stopNode
Hi Anton and Alexandr,
I thought vertx is invoking IgniteClusterManager#leave because of network
segmentation. so I created wrapper to IgniteClusterManager and added logs
before invoking leave(). I did not see any log of wrapper. So ignite is not
closed from the IgniteClusterManager#leave
Looks
;dkarachent...@gridgain.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Cache could be stopped when was called IgniteCache.close(),
>>>> IgniteCache.destroy() or node is stopping.
>>>> Please, attach logs to find out your reason.
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context: http://apache-ignite-users.705
>>>> 18.x6.nabble.com/Cache-stopped-tp9503p9509.html
>>>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>>>
>>>
>>>
>>
>>
>> --
>> Thanks,
>> Alexandr Kuramshin
>>
>
>
rachent...@gridgain.com>
>> wrote:
>>
>>> Hi,
>>>
>>> Cache could be stopped when was called IgniteCache.close(),
>>> IgniteCache.destroy() or node is stopping.
>>> Please, attach logs to find out your reason.
>>>
>>>
>>>
>
stroy() or node is stopping.
>> Please, attach logs to find out your reason.
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-users.705
>> 18.x6.nabble.com/Cache-stopped-tp9503p9509.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>
--
Thanks,
Alexandr Kuramshin
Hi,
Cache could be stopped when was called IgniteCache.close(),
IgniteCache.destroy() or node is stopping.
Please, attach logs to find out your reason.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Cache-stopped-tp9503p9509.html
Sent from the Apache Ignite
Hi,
I am using vertx-ignite to establish ignite cluster and see cache is
stopped in logs.
May I know the cases where cache is stopped ? i can share the logs if
required.
Thanks.
-mix.readme.io/docs/kafka-streamer
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Cache-stopped-exception-with-KafkaStreamer-tp9326p9348.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi,
I am using KafkaStreamer to populate the data into cache.
i see following message in logs
java.lang.IllegalStateException: Grid is in invalid state to perform this
operation. It either not started yet or has already being or have stopped
18 matches
Mail list logo