-
Notifications
You must be signed in to change notification settings - Fork 101
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
Fluentd stops processing the logs if a pod is restarted #296
Comments
Duplicate of #289 |
|
Is this issue only with type mounted-file?, if so can I use any other type. |
Yes, it only affects mounted-file types. We are working on a resolution that may work. Are you able to switch to logging to stdout for the jboss server in the container/pod? If you do that then you will not face this problem when pods restart. |
@Cryptophobia Thanks for the update, we are in process of moving the logs to stdout but since we have some applications already running in prod we are finding for a fix. The mounted-file plugin only supports emptydir volume or we can use a persistant storage. |
@Cryptophobia If I restart teh configmap in few seconds to minutes, will fluentd be able to capture all the logs without any miss? |
@dhineshbabuelango , KFO only supports mounted-files logs as
If you write a hook to reload the configmap to delete and recreate the configmap right away after restarting the pods, it should work. It needs to happen right after the restart of the pods though. |
@Cryptophobia thanks for your response. Will refreshing(delete & recreate) the configmap will lead to fluentd missing any of the logs that was currently reading during the restart ? |
Hi Team,
We are using fluentd in EKS cluster, we are injesting logs from a file in the container to fluentd through a configmap, using grok parser, while the initial setup working fine everytime when a deployment or pod is restarted, we had to recreate the config map(without any change) as well only then fluentd processing the logs
The text was updated successfully, but these errors were encountered: