Skip to content
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

LOG-4241: upgrade to fluentd v1.16.2 to address file handle issue #96

Merged
merged 1 commit into from
Aug 10, 2023

Conversation

jcantrill
Copy link
Member

Description

This PR:

Links

Based upon my testing this change demonstrates better management of tailed files being followed by inode. Additionally it still shows to avoid "stuck" logs, with improved cpu, memory.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 7, 2023

@jcantrill: This pull request references LOG-4241 which is a valid jira issue.

In response to this:

Description

This PR:

Links

Based upon my testing this change demonstrates better management of tailed files being followed by inode. Additionally it still shows to avoid "stuck" logs, with improved cpu, memory.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@jcantrill
Copy link
Member Author

/hold

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 7, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcantrill

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved label Aug 7, 2023
@jcantrill
Copy link
Member Author

/test cluster-logging-operator-e2e

@jcantrill
Copy link
Member Author

Comparison of v1.14.6 versus v1.16.2 under same conditions where there is no log loss.

@jcantrill jcantrill changed the base branch from ruby31-v1.14.x to v1.16.x August 9, 2023 18:41
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 9, 2023

@jcantrill: This pull request references LOG-4241 which is a valid jira issue.

In response to this:

Description

This PR:

Links

Based upon my testing this change demonstrates better management of tailed files being followed by inode. Additionally it still shows to avoid "stuck" logs, with improved cpu, memory.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@jcantrill
Copy link
Member Author

/test clo-e2e-ubi8-ruby31

@jcantrill
Copy link
Member Author

/override ci/prow/cluster-logging-operator-e2e

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 9, 2023

@jcantrill: Overrode contexts on behalf of jcantrill: ci/prow/cluster-logging-operator-e2e

In response to this:

/override ci/prow/cluster-logging-operator-e2e

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@jcantrill
Copy link
Member Author

ci/prow/cluster-logging-operator-e2e is retired

@jcantrill
Copy link
Member Author

/hold cancel

@jcantrill
Copy link
Member Author

/hold

@jcantrill
Copy link
Member Author

/hold cancel

@cahartma
Copy link

/lgtm

@jcantrill
Copy link
Member Author

/hold cancel

@jcantrill
Copy link
Member Author

/refresh

@jcantrill jcantrill deleted the v1.16.2_on58 branch August 14, 2023 12:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants