Re: persist periodically

2017-02-21 Thread vkulichenko 
Shawn,

If it's a standalone node, you can just terminate the process. There is a
shutdown hook that will gracefully stop the node. For example, kill command
(without -9) will do the job.

For embedded node call Ignition.stop().

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/persist-periodically-tp10621p10771.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: persist periodically

2017-02-14 Thread shawn.du 





Hi, Andrey,then do you know how to gracefully shut down ignite servers when write-behind enabled without data lose?






ThanksShawn





On 02/14/2017 14:04，shawn.du<shawn...@neulion.com.cn> wrote： 






exactly.  Thank you, Andrey!






ThanksShawn





On 02/14/2017 13:54，Andrey Mashenkov<amashen...@gridgain.com> wrote： 


Hi Shawn,Look at CacheConfiguration.setWriteBehindEnabled [1] and related methods.Does it meets your needs?[1] http://apacheignite.gridgain.org/v1.8/docs/persistent-store#write-behind-cachingOn Tue, Feb 14, 2017 at 8:40 AM, shawn.du <shawn...@neulion.com.cn> wrote:

  





Hi,ignite support persist data periodically?see blow use case:we want to implement storm state management using ignite.we maintain storm stateful object as caches in ignite.for storm used processing message in very low latency, so the stateful object maybe changed very fast.if ignite persist each change into storage, I think it will both decrease ignite and storm performance.how to make ignite persist periodically? like every seconds.

  



  
ThanksShawn

Re: persist periodically

2017-02-13 Thread shawn.du 






exactly.  Thank you, Andrey!






ThanksShawn





On 02/14/2017 13:54，Andrey Mashenkov<amashen...@gridgain.com> wrote： 


Hi Shawn,Look at CacheConfiguration.setWriteBehindEnabled [1] and related methods.Does it meets your needs?[1] http://apacheignite.gridgain.org/v1.8/docs/persistent-store#write-behind-cachingOn Tue, Feb 14, 2017 at 8:40 AM, shawn.du <shawn...@neulion.com.cn> wrote:

 





Hi,ignite support persist data periodically?see blow use case:we want to implement storm state management using ignite.we maintain storm stateful object as caches in ignite.for storm used processing message in very low latency, so the stateful object maybe changed very fast.if ignite persist each change into storage, I think it will both decrease ignite and storm performance.how to make ignite persist periodically? like every seconds.

 



 
ThanksShawn

Re: persist periodically

2017-02-13 Thread Andrey Mashenkov 
Hi Shawn,

Look at CacheConfiguration.setWriteBehindEnabled [1] and related methods.
Does it meets your needs?

[1]
http://apacheignite.gridgain.org/v1.8/docs/persistent-store#write-behind-caching

On Tue, Feb 14, 2017 at 8:40 AM, shawn.du <shawn...@neulion.com.cn> wrote:

> Hi,
>
> ignite support persist data periodically?
>
> see blow use case:
> we want to implement storm state management using ignite.
> we maintain storm stateful object as caches in ignite.
> for storm used processing message in very low latency, so the stateful
> object maybe changed very fast.
> if ignite persist each change into storage, I think it will both decrease
> ignite and storm performance.
> how to make ignite persist periodically? like every seconds.
>
> Thanks
> Shawn
>
>

persist periodically

2017-02-13 Thread shawn.du 






Hi,ignite support persist data periodically?see blow use case:we want to implement storm state management using ignite.we maintain storm stateful object as caches in ignite.for storm used processing message in very low latency, so the stateful object maybe changed very fast.if ignite persist each change into storage, I think it will both decrease ignite and storm performance.how to make ignite persist periodically? like every seconds.






ThanksShawn