Replies: 8 comments
-
|
I didn't reproduce the problem, as you can see from my chart that the juicefs service reported normal data after recovery.
I think your case may be caused by one of the following reasons:
You can check these issues through the consul web ui with the prometheus web ui. |
Beta Was this translation helpful? Give feedback.
-
|
@zhijian-pro |
Beta Was this translation helpful? Give feedback.
-
|
Please check the juicefs log for output related to this code.
Lines 69 to 133 in b08a7f6 |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
It shows that we cannot get metrics of node40 in prometheus: |
Beta Was this translation helpful? Give feedback.
-
|
And i cannot find node40 in consul web ui |
Beta Was this translation helpful? Give feedback.
-
|
Can you send your WeChat account to my email : jiaxingduan@gmail.com ? I can help you isolate it. |
Beta Was this translation helpful? Give feedback.






Uh oh!
There was an error while loading. Please reload this page.
-
What happened:

juicefs client monitoring does not automatically reply after a drop
How to reproduce it (as minimally and precisely as possible):
Nodes with juicefs client resume normal operation after an OOM
Anything else we need to know?
Our juicefs client uses consul for service discovery
Environment:
juicefs --version) or Hadoop Java SDK version:root@node75:~/juicefs-u# ./juicefs --version juicefs version 1.0.0+2022-08-08.cf0c269cat /etc/os-release):jfs client nodes information that cannot be recovered after a drop
Beta Was this translation helpful? Give feedback.
All reactions