You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Anil <an...@gmail.com> on 2016/12/13 06:18:20 UTC
Cache stopped
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.
Re: Cache stopped
Posted by vkulichenko <va...@gmail.com>.
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.
Re: Cache stopped
Posted by Anil <an...@gmail.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 <ei...@gmail.com>
wrote:
> 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
> org.apache.ignite.Ignition#stop(java.lang.String, boolean)
>
> You could change IgniteConfiguration.setSegmentationPolicy()
> to SegmentationPolicy.NOOP, so the node will not be stopped upon
> segmentation (the default value is STOP).
>
> But the better way is to deploy the kafka streamer as a node singleton
> [1], and implement it as a service, which could be automatically stopped
> right before node do.
>
> [1] http://apacheignite.gridgain.org/docs/cluster-singletons
>
>
> 2016-12-16 13:29 GMT+07:00 Anil <an...@gmail.com>:
>
>> 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 like ignite is stopped from some where else because of network
>> segmentation? can you help me in understanding this. is there any to
>> intercept behavior ?
>>
>> In my scenario, i am starting kafka streamer when ignite is up and need
>> to stop the kafka streamer before closing the ignite due to any problem.
>> otherwise, it would lead to data problem. and i am using vertx-ignite.
>>
>> please share if there are other cluster manager better than vertx ?
>>
>> Thanks for you help.
>>
>>
>> - Anil
>>
>>
>
>
> --
> Thanks,
> Alexandr Kuramshin
>
Re: Cache stopped
Posted by Alexandr Kuramshin <ei...@gmail.com>.
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
org.apache.ignite.Ignition#stop(java.lang.String, boolean)
You could change IgniteConfiguration.setSegmentationPolicy()
to SegmentationPolicy.NOOP, so the node will not be stopped upon
segmentation (the default value is STOP).
But the better way is to deploy the kafka streamer as a node singleton [1],
and implement it as a service, which could be automatically stopped right
before node do.
[1] http://apacheignite.gridgain.org/docs/cluster-singletons
2016-12-16 13:29 GMT+07:00 Anil <an...@gmail.com>:
> 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 like ignite is stopped from some where else because of network
> segmentation? can you help me in understanding this. is there any to
> intercept behavior ?
>
> In my scenario, i am starting kafka streamer when ignite is up and need
> to stop the kafka streamer before closing the ignite due to any problem.
> otherwise, it would lead to data problem. and i am using vertx-ignite.
>
> please share if there are other cluster manager better than vertx ?
>
> Thanks for you help.
>
>
> - Anil
>
>
--
Thanks,
Alexandr Kuramshin
Re: Cache stopped
Posted by Anil <an...@gmail.com>.
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 like ignite is stopped from some where else because of network
segmentation? can you help me in understanding this. is there any to
intercept behavior ?
In my scenario, i am starting kafka streamer when ignite is up and need to
stop the kafka streamer before closing the ignite due to any problem.
otherwise, it would lead to data problem. and i am using vertx-ignite.
please share if there are other cluster manager better than vertx ?
Thanks for you help.
- Anil
Re: Cache stopped
Posted by Anil <an...@gmail.com>.
i see network segmentation in logs. ignore my previous question. thanks.
On 14 December 2016 at 16:06, Anil <an...@gmail.com> wrote:
>
> You are correct. i am using vertx-ignite. i dont understand the reason for
> stopping the ignite.
>
> I am using KafkaStreamer and it must be stopped on a node when is it leave
> the ignite cluster. Do you have any suggestions ?
>
> I mean -
>
> Lets say there are two ignite nodes (A & B). when ignite is started on a
> node and kafka streamer is started.
>
> now A & B forms the cluster. now A is not reachable to cluster because of
> some network issue. Does ignite is stopped on A ? or how A is notified that
> is not in the cluster ? A and B runs as separate ignite instances ? Please
> clarify.
>
> Thanks
>
> On 14 December 2016 at 14:34, Alexandr Kuramshin <ei...@gmail.com>
> wrote:
>
>> It's seems that you are trying to getOrCreateCache after the grid was
>> stopped.
>>
>> Message recieved by KafkaCacheDataStreamer's running in a parrallel
>> thread (pool-6-thread-1). You should first stop all streaming threads and
>> then stop the grid.
>>
>> 2016-12-14 11:12 GMT+07:00 Anil <an...@gmail.com>:
>>
>>> HI,
>>>
>>> I have attached the logs. thanks
>>>
>>> Thanks.
>>>
>>> On 13 December 2016 at 18:59, dkarachentsev <dk...@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
>>
>
>
Re: Cache stopped
Posted by Anil <an...@gmail.com>.
You are correct. i am using vertx-ignite. i dont understand the reason for
stopping the ignite.
I am using KafkaStreamer and it must be stopped on a node when is it leave
the ignite cluster. Do you have any suggestions ?
I mean -
Lets say there are two ignite nodes (A & B). when ignite is started on a
node and kafka streamer is started.
now A & B forms the cluster. now A is not reachable to cluster because of
some network issue. Does ignite is stopped on A ? or how A is notified that
is not in the cluster ? A and B runs as separate ignite instances ? Please
clarify.
Thanks
On 14 December 2016 at 14:34, Alexandr Kuramshin <ei...@gmail.com>
wrote:
> It's seems that you are trying to getOrCreateCache after the grid was
> stopped.
>
> Message recieved by KafkaCacheDataStreamer's running in a parrallel thread
> (pool-6-thread-1). You should first stop all streaming threads and then
> stop the grid.
>
> 2016-12-14 11:12 GMT+07:00 Anil <an...@gmail.com>:
>
>> HI,
>>
>> I have attached the logs. thanks
>>
>> Thanks.
>>
>> On 13 December 2016 at 18:59, dkarachentsev <dk...@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
>
Re: Cache stopped
Posted by Alexandr Kuramshin <ei...@gmail.com>.
It's seems that you are trying to getOrCreateCache after the grid was
stopped.
Message recieved by KafkaCacheDataStreamer's running in a parrallel thread
(pool-6-thread-1). You should first stop all streaming threads and then
stop the grid.
2016-12-14 11:12 GMT+07:00 Anil <an...@gmail.com>:
> HI,
>
> I have attached the logs. thanks
>
> Thanks.
>
> On 13 December 2016 at 18:59, dkarachentsev <dk...@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
Re: Cache stopped
Posted by Anil <an...@gmail.com>.
HI,
I have attached the logs. thanks
Thanks.
On 13 December 2016 at 18:59, dkarachentsev <dk...@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.
> 70518.x6.nabble.com/Cache-stopped-tp9503p9509.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
Re: Cache stopped
Posted by dkarachentsev <dk...@gridgain.com>.
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 Users mailing list archive at Nabble.com.