Thanks Val!
Can you explain more detail how "invoke" works internally comparing with put
operation. For we pass a "function" to ignite.
I see below Java Doc about "invoke"
* An instance of entry processor must be stateless as it may be invoked
multiple times on primary and
* backup nodes in the
error prone.
Thanks
Shawn
-邮件原件-
发件人: Shawn Du [mailto:shawn...@neulion.com.cn]
发送时间: 2016年12月22日 10:34
收件人: user@ignite.apache.org
主题: 答复: Cache.invoke are terribly slow and can't update cache
Thanks Val!
Can you explain more detail how "invoke" works internally comparin
Shawn,
#1 - Yes, peer class loading is needed if you don't have entry processor
implementation class deployed on server nodes.
#2 - Correct. Moreover, I would recommend not to use lambdas or anonymous
classes for anything that can be serialized, but to use static classes
instead (this is actually
Thanks Val!Now I understood entryprocessor better. as to "error prone", I meant if we follow the document,it will be error prone. For EntryProcessor is just an interface, it doesn't prohibit user to use lamda or anonymous classes.
When
Shawn,
You just should keep in mind that this is an object that will be serialized,
sent across network and invoked on other side. The purpose of entry
processor is to be executed on server side and atomically read and update a
single entry. Having said that, the logic you described doesn't make m
Thanks Val, that's good.
-邮件原件-
发件人: vkulichenko [mailto:valentin.kuliche...@gmail.com]
发送时间: 2016年12月23日 9:47
收件人: user@ignite.apache.org
主题: Re: 回复:Re: 答复: Cache.invoke are terribly slow and can't update
cache
Shawn,
You just should keep in mind that this is an object th