Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Add connection check at startup when out_forward. #2184
Added an option to check the out_forward node and communication when starting fluentd.
It is a matter with the following mailing list.
I am using fluentd v1.2.6 in TLS encryption mode when forwarding in out_forward -> in_forward.
At fluentd startup I'd like to check if the out_forward process can connection with the in_forward node before listening for the forward port.
The use case is below.
The out_forward on the AWS side is redundant with the Active / Standby configuration.
I think that it is desirable that fluentd gets an error as it is when the out_forward -> in_forward connection can not be performed by the new deployment so that the crash occurs.
The assumed error is a certificate validation failure or SHARD key mismatch.
I recognize that these errors are not checked at startup in fluentd now
I am not familiar with Ruby, and since I read the Fluentd code for the first time this time, please let me know if there is a better implementation.
This pull request is the same as below. #2180