8.x6.nabble.com/igfs-meta-behavior-when-node-restarts-tp13155p13599.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
al 4 TX op/s grows to
> ~200 TX op/s across all my nodes. I'm assuming if this grows unbounded, the
> cluster performance and stability will eventually be affected.
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/igfs-meta
ntext:
http://apache-ignite-users.70518.x6.nabble.com/igfs-meta-behavior-when-node-restarts-tp13155p13446.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
I tried to reproduce this with 2-node Ignite cluster running upon HDFS.
I tried action sequences like this: put some files/dirs , move/delete some
files/dirs, restart one of the nodes.
The metrics were observed via JConsole.
I used Ignite 2.1.
Unfortunately, I was not able to reproduce the issue.
M
t/_temporary/part-n... to
> /data/path/output/part-n... and deletes the _temporary directory.
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/igfs-meta-behavior-when-node-restarts-
> tp13155p13322.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
he-ignite-users.70518.x6.nabble.com/igfs-meta-behavior-when-node-restarts-tp13155p13322.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
I suppose, the file system contents and the sequence of the operations on
them may play a role there.
What is the sequence of operations in your case, at least approximately?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/igfs-meta-behavior-when-node-restarts
nabble.com/igfs-meta-behavior-when-node-restarts-tp13155p13299.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
and fix the issue is a minimal possible
scenario that reproduces the problem.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/igfs-meta-behavior-when-node-restarts-tp13155p13283.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/igfs-meta-behavior-when-node-restarts-tp13155p13246.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
-5552cbfa6204]
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/igfs-meta-behavior-when-node-restarts-
> tp13155p13239.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
a6204]
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/igfs-meta-behavior-when-node-restarts-tp13155p13239.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
rom normal operation--there's nothing indicating
retries of any sort. Are there other classes I should try?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/igfs-meta-behavior-when-node-restarts-tp13155p13238.html
Sent from the Apache Ignite Users mailing
ransaction
many times per one operation) if some overlapping operations are attempted
concurrently.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/igfs-meta-behavior-when-node-restarts-tp13155p13206.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi, Joe,
how are you getting the cache commit rate in this measurement?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/igfs-meta-behavior-when-node-restarts-tp13155p13201.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
x6.nabble.com/file/n13155/rollback.png>
In the screenshot, I've restarted all the nodes in the cluster a little
after 14:30, and restarted one of the nodes around 16:30.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/igfs-meta-behavior-when-node-resta
16 matches
Mail list logo
