-
Notifications
You must be signed in to change notification settings - Fork 226
Can't PIP install KCL all the time because of 429 responses from Maven #99
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
Comments
It looks like the problem is here: https://github.com/awslabs/amazon-kinesis-client-python/blob/master/setup.py#L188 If we caught a 429 and applied some backoff, I think this wouldn't be a problem. |
We just hit this issue with a very similar setup. We have KCL inside of a Docker container and during the initial container build Maven had 429 errors which prevented a jar file from being available at runtime. For searching purposes, the runtime error message was:
The error output during container build was the same as posted in the image above. Again, for searching purposes here is the text:
And:
It took me about 5 hours to figure out what went wrong. The workaround was to babysit the container build until it worked as expected and then deploy the container. It would be great if the PR that fixes this issue could get merged and deployed. |
@MrHen the issue is fixed in #100. Until the fix is applied upstream, we put git+https://github.com/alight-analytics/[email protected]#egg=amazon_kclpy in our requirements for our dockerfile. Since then our builds have been consistently stable. |
@jtfalkenstein , @MrHen
|
So we're working on beginning to use the KCL. We've got a Dockerized build that pip-install's
amazon_kclpy==2.0.1
. Sometimes this works, but sometimes we get 429s from Maven for all the things it needs to install.This is a big problem, since if we cannot do this install, we cannot use the KCL. Is there either an alternative way to install this stuff? Or is there something that can be done that would make this all consistently install?
The text was updated successfully, but these errors were encountered: