-
Notifications
You must be signed in to change notification settings - Fork 76
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
Big uploads seem to fail. #141
Comments
Looks like it is the same issue as this one: #24 |
While it does look similar at the first glance, they seem to get errors inside of attic logs, where I don't get any and the error, while occurring in both issues, seem to differ a bit. |
The "not a result of an error" is a symptom of hyperium/hyper#2500. I noticed this error with an attic instance deployed in a kubernetes cluster and behind the nginx ingress since nginx sends a GOAWAY after handling a certain number of requests. |
Does it work with Caddy? |
I don't actually control this kubernetes cluster, so I don't have an easy way to test it myself. I would say "This behavior is within-spec, and attic should handle it." except that that it looks to me like reqwest doesn't expose sufficient detail to make that happen, and handling it today would require using hyper directly. |
Maybe the same as: |
Whenever I try to upload larger files that have been added to the
/nix/store
(I need to package a proprietary project for our projects, so I'm unable to redistribute), which I add by manually downloading and then runningnix store add-file ~/Downloads/<file>
, the file weighs about 980MB.I tried pushing it using
attic push work /nix/store/<path>
, but it fails to upload (withSQLite
, it failed at 10MB, withPostgreSQL
it fails at 250MB).Log:
I can see that the database is getting spammed with the insert and update requests, so I guess that's where the difference between SQLite and PostgreSQL comes in.
I'm wondering if there's something else I could do to improve the performance and allow this to be uploaded.
The text was updated successfully, but these errors were encountered: