Actions
Bug #4575
closed
Single threaded rpcbind is not scalable
Start date:
2014-02-05
Due date:
% Done:
100%
Estimated time:
Difficulty:
Hard
Tags:
Gerrit CR:
External Bug:
Description
In a case there are many (thousands) clients trying to talk with rpcbind in the same time, the single threaded rpcbind will handle the requests sequentially. Since the request handling (plus sending the response to the client) is usually much slower than receiving the request, the last arrived request might be serviced after very long time.
To solve this issue we should make the rpcbind multithreaded.
Related issues
Updated by Robert Mustacchi about 9 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
- Tags deleted (
needs-triage)
Updated by Electric Monk about 9 years ago
git commit 8f6d9dae92449b59bdafcb7777bc32f1b2726e48
Author: Marcel Telka <marcel.telka@nexenta.com> 4575 Single threaded rpcbind is not scalable 4483 rpcbind: Reply for remote calls comes from incorrect UDP port Reviewed by: Ilya Usvyatsky <ilya.usvyatsky@nexenta.com> Reviewed by: Jan Kryl <jan.kryl@nexenta.com> Reviewed by: Michael Schuster <michaelsprivate@gmail.com> Reviewed by: Gary Mills <gary_mills@fastmail.fm> Reviewed by: Jerry Jelinek <jerry.jelinek@joyent.com> Approved by: Robert Mustacchi <rm@joyent.com>
Actions