-
Notifications
You must be signed in to change notification settings - Fork 80
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
[WFLY-17766] undertow access log graceful termination #374
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please adjust the filename of the proposal and the title of the PR to use WFLY-13933 and not EAP7-1642
The proposals are a public project so we should be using the community issues as the primary reference.
tmp update until process stuff will be sorted out. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are some questions that need to be discussed.
- number of retries between NIO worker state polls | ||
- interim period | ||
|
||
NOTE: fix also slightly change how access log is being rotated. Previously it has been done on every write OP, which incured overhead. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
incurred
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
Async close will wait till aloted time( with interim checks ) runs off to take over agressively write OPs or until NIO worker yield. As is, in fix number of interim checks and wait period is fixed(interim_period*number_of_retries). | ||
|
||
RFE commits add changes to model and services in order to allow configuration of: | ||
- number of retries between NIO worker state polls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we really want to configure the number of retries, or just the maximum amount of delay here will be enough to server users? What I would like to know if there is a specific case where the final user might want to tweak the number of retries. Maybe we should come up with an algorithm that infers the number of retries based on the amount of delay that was configured.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Granularity? GIves users better control.
4f9b81b
to
7dbbc55
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @baranowb
I have added some comments.
Please feel free to let me know if you have any questions :)
Looks good to me! Thanks @baranowb |
ISSUE: https://issues.redhat.com/browse/EAP7-1642
RFE: https://issues.redhat.com/browse/WFLY-17766
https://issues.redhat.com/browse/WFLY-13933