Hi!
"After I reduced the checkpointFrequency, the block time decrease to 10
seconds."
Good news!
"But I do not understand how the checkpointFrequency impacts the partition
map exchange, can someone explain it?"
Applying chages from WAL since last checkpoint (i.e. recovery) is a part of
PME
Thank Sergey!
>From the email that he sent to me(I do not know why the email doesn't
display in this post), I know that the default checkpointFrequency(18)
was too long, so it impacts the partition map exchange. After I reduced the
checkpointFrequency, the block time decrease to 10 seconds.
Sergey -
Thank for your reply.
Yes, I can find them in the logs, I attached the logs of three nodes, the
node that was restarted is node3.
BTW, I use the default Rebalance Mode(ASYNC), so the rebalancing may not
impact the whole cluster.
Am I getting it wrong?
ignite-003.log
Justin, may be problem in rebalancing?
https://apacheignite.readme.io/docs/rebalancing
Could you grep log messages by GridCachePartitionsExchangeManager with text
"Skipping rebalancing" or "Rebalancing scheduled" ?
пн, 28 янв. 2019 г. в 15:04, Justin Ji :
> Can someone give me some suggestions?
Can someone give me some suggestions?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Sergey -
Thank for your reply.
Yes, I defined consistentId for every node. Is it relates to partition map
exchange?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Sergey -
Thank for your reply.
Yes, I defined consistentId for every node. Does it relates to partition map
exchange?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi!
Did you define consistentId for nodes?
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/IgniteConfiguration.html#setConsistentId-java.io.Serializable-
пн, 28 янв. 2019 г. в 11:56, Justin Ji :
> I have a cluster(2.7.0) with persistence enabled, the cluster
I have a cluster(2.7.0) with persistence enabled, the cluster has three
server nodes(8c16g) and every node has 8 Gb data(1 primary and 1 backup).
When I restart one of them, the whole cluster will stop about 60 seconds and
do not process any request from the client.
>From the logs, I saw that
