[
https://issues.apache.org/jira/browse/GOBBLIN-724?focusedWorklogId=223366&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-223366
]
ASF GitHub Bot logged work on GOBBLIN-724:
------------------------------------------
Author: ASF GitHub Bot
Created on: 04/Apr/19 23:47
Start Date: 04/Apr/19 23:47
Worklog Time Spent: 10m
Work Description: ibuenros commented on pull request #2591: [GOBBLIN-724]
Upgrade throttling server so waiting until tokens can be used is done…
URL: https://github.com/apache/incubator-gobblin/pull/2591
… by the client instead of the server. See GOBBLIN-724.
Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I
have checked off all the steps below!
### JIRA
- [ ] My PR addresses the following [Gobblin
JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references
them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
- https://issues.apache.org/jira/browse/GOBBLIN-XXX
### Description
- [ ] Here are some details about my PR, including screenshots (if
applicable):
### Tests
- [ ] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
### Commits
- [ ] My commits all reference JIRA issues in their subject lines, and I
have squashed multiple commits if they address the same issue. In addition, my
commits follow the guidelines from "[How to write a good git commit
message](http://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
2. Subject is limited to 50 characters
3. Subject does not end with a period
4. Subject uses the imperative mood ("add", not "adding")
5. Body wraps at 72 characters
6. Body explains "what" and "why", not "how"
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 223366)
Time Spent: 10m
Remaining Estimate: 0h
> Throttling server delays responses for throttling causing too many connections
> ------------------------------------------------------------------------------
>
> Key: GOBBLIN-724
> URL: https://issues.apache.org/jira/browse/GOBBLIN-724
> Project: Apache Gobblin
> Issue Type: Bug
> Reporter: Issac Buenrostro
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, the throttling server implements throttling in part by delaying
> the response with the permit allocation. However, when waiting to respond,
> the request remains in flight utilizing system resources and severely
> limiting how many clients can use the throttling server.
> As a fix, the server should respond immediately and ask the client to wait
> before distributing the permits.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
