Dear Ivan,
Thank you for your reply this clarifies the mater for me.
Kind regards
Dr. Evangelos Morakis
Software Architect
> On 8 May 2019, at 09:00, Ivan Pavlukhina wrote:
>
> Evangelos,
>
> Thank you for your feedback!
>
> Regarding your questions:
> 1. Sounds quite widely. To avoid
Evangelos,
Thank you for your feedback!
Regarding your questions:
1. Sounds quite widely. To avoid misunderstanding I try to give a general hint
only. Actually a decision to rebalance data or not is made after PME. So, it is
true that not every PME leads to a rebalance. (one more example when
Dear Ivan,
Thank you very much for you comprehensive answer, may I just say that ignite is
definitely my favorite “beast” amongst the existing solutions due to its
versatility and the power it delivers when it comes to designing complex
distributed solutions as in my specific use case. In
Hi Evangelos and Matt,
As far as know there were issues with a join of a client node in
previous Ignite versions. In new versions a joining client should not
cause any spikes.
In fact PME is (unfortunately) a widely known beast in the Ignite
world. Fundamentally PME can (and should) perform
Matt thank you for your reply,
Indeed I saw your question too yesterday. In regards to points 3-4 of my
question I suppose that as you mention, if one shuts down gracefully the client
node and if the number of threads responsible for rebalancing the data gets
tweaked, then I guess the amount
I have these same questions and posted about this yesterday
(http://apache-ignite-users.70518.x6.nabble.com/What-happens-when-a-client-gets-disconnected-td27959.html).
Based on my understanding:
1) Yes, PME will always happen when a server node joins
2) This is my biggest question. I'm
Hi everyone,
We are currently using ignite 2.7 and
I have some basic questions in regards to ignite’s behavior during PME. After
referring to ignite’s documentation and the cwiki’s section about PME(partition
map exchange under the hood) the following has been made apparent. When a new
node
