As I mentioned above, it was hanged PME. PME is a cluster-wide operation
that leads to refreshing information about partition distribution across
nodes. Ans any cache operations should await PME ending. In your case,
client reconnection to another server node does not resolve the issue,
because the
Apologies can't paste logs due to firm policy. What do you think about my
questions regarding clients switching to good nodes automatically?
On Tue, Sep 7, 2021 at 4:14 AM Ilya Kazakov wrote:
> Hello Mike. According to your description, there was a hanging PME. If you
> need more detailed analys
Hello Mike. According to your description, there was a hanging PME. If you
need more detailed analysis, could you share your logs and thread dumps?
---
Ilya
пн, 6 сент. 2021 г. в 22:21, Mike Wiesenberg :
> Using Ignite 2.10.0
>
> We had a frustrating series of issues with Ignite
Using Ignite 2.10.0
We had a frustrating series of issues with Ignite the other day. We're
using a 4-node cluster with 1 backup per table and cacheMode set to
Partitioned, and write behind enabled. We have a client that inserts data
into caches and another client that listens for new data in thos
