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

Various Windows fixes. #1114

Merged
merged 1 commit into from
Mar 25, 2015
Merged

Conversation

nicolasnoble
Copy link
Member

-) Introduce a wait-loop with a 100ms delay on iomgr shutdown, so that background threads have the chance to place last minute callbacks without having to stall for the whole 10 seconds deadline.
-) io completion ports will get notifications on socket shutdowns, so we need to delay their deletions for after we get a notification for them.
-) we need to keep some sense of how many orphan sockets are in, so we can properly collect them - let's not shutdown the iocp loop until after all orphans have been collected.

@nicolasnoble
Copy link
Member Author

I believe this may even be the fix for #546.

@codeandroid
Copy link

@nicolasnoble fyi - my tests show it partially fixes #546.

@ctiller
Copy link
Member

ctiller commented Mar 23, 2015

Can you rename short_timeout to short_deadline - we're fairly consistent
that timeout is relative and deadline is absolute across the codebase.

On Tue, Mar 24, 2015, 5:46 AM codeandroid notifications@github.com wrote:

@nicolasnoble https://github.com/nicolasnoble fyi - my tests show it
partially fixes #546 #546.


Reply to this email directly or view it on GitHub
#1114 (comment).

@nicolasnoble
Copy link
Member Author

Oh, sorry, you're right. I started having that variable as an actual timeout, then the code evolved a bit.

-) Introduce a wait-loop with a 100ms delay on iomgr shutdown, so that background threads have the chance to place last minute callbacks without having to stall for the whole 10 seconds deadline.
-) io completion ports will get notifications on socket shutdowns, so we need to delay their deletions for after we get a notification for them.
-) we need to keep some sense of how many orphan sockets are in, so we can properly collect them - let's not shutdown the iocp loop until after all orphans have been collected.
jtattermusch added a commit that referenced this pull request Mar 25, 2015
@jtattermusch jtattermusch merged commit 0992749 into grpc:master Mar 25, 2015
@lock lock bot locked as resolved and limited conversation to collaborators Feb 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants