-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HA configuration performs incorrectly #67
Comments
Digging around, I ran into the |
Here is a check:
So the problem is StandbyException happens with non WebHDFS::IOError ?
|
Correct.
|
Versions:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem:
I am running HDFS within my Mesos cluster. It is fully HA. I have configured a matcher to point to both NameNodes. However, when the first listed NameNode is in standby mode, the standby_namenode is never used.
Expected behavior:
Connection to the
namenode
NameNode succeeds, finds its instandby
mode, and attempts to send tostandby_namenode
which is now the active NameNode.Actual results:
This is using td-agent 3.1.1 (fluentd 1.0.2) with the shipped fluent-plugin-webhdfs 1.2.2 plugin.
Forcing a NameNode failover caused logs to start flowing, again. However, this required manual intervention and I think the driver should do the correct thing in this state.
The text was updated successfully, but these errors were encountered: