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

snappy error for variable-length data #450

Open
ifokeev opened this issue May 18, 2021 · 3 comments
Open

snappy error for variable-length data #450

ifokeev opened this issue May 18, 2021 · 3 comments

Comments

@ifokeev
Copy link

ifokeev commented May 18, 2021

I'm getting very often:

{"level":"error","timestamp":"2021-05-18T10:53:29.489Z","msg":"Error returned from query scanner: snappy: corrupt input\n"}
{"level":"error","timestamp":"2021-05-18T10:53:35.467Z","msg":"Error returned from query scanner: snappy: corrupt input\n"}
{"level":"error","timestamp":"2021-05-18T10:53:41.476Z","msg":"Error returned from query scanner: snappy: corrupt input\n"}
{"level":"error","timestamp":"2021-05-18T10:53:53.545Z","msg":"Error returned from query scanner: snappy: corrupt input\n"}
{"level":"error","timestamp":"2021-05-18T10:53:59.447Z","msg":"Error returned from query scanner: snappy: corrupt input\n"}
{"level":"error","timestamp":"2021-05-18T10:54:01.434Z","msg":"Error returned from query scanner: snappy: corrupt input\n"}
{"level":"error","timestamp":"2021-05-18T10:54:05.378Z","msg":"Error returned from query scanner: snappy: corrupt input\n"}
{"level":"error","timestamp":"2021-05-18T10:54:11.468Z","msg":"Error returned from query scanner: snappy: corrupt input\n"}
{"level":"error","timestamp":"2021-05-18T10:54:23.359Z","msg":"Error returned from query scanner: snappy: corrupt input\n"}
{"level":"error","timestamp":"2021-05-18T10:54:25.866Z","msg":"Error returned from query scanner: snappy: corrupt input\n"}
{"level":"error","timestamp":"2021-05-18T10:54:31.764Z","msg":"Error returned from query scanner: snappy: corrupt input\n"}
{"level":"error","timestamp":"2021-05-18T10:54:35.473Z","msg":"Error returned from query scanner: snappy: corrupt input\n"}
{"level":"error","timestamp":"2021-05-18T10:54:41.432Z","msg":"Error returned from query scanner: snappy: corrupt input\n"}
{"level":"error","timestamp":"2021-05-18T10:54:45.369Z","msg":"Error returned from query scanner: snappy: corrupt input\n"}
{"level":"error","timestamp":"2021-05-18T10:54:47.497Z","msg":"Error returned from query scanner: snappy: corrupt input\n"}
{"level":"error","timestamp":"2021-05-18T10:54:49.420Z","msg":"Error returned from query scanner: snappy: corrupt input\n"}
{"level":"error","timestamp":"2021-05-18T10:54:53.438Z","msg":"Error returned from query scanner: snappy: corrupt input\n"}

How is it possible to fix this error? only by removing the compression?
Thanks

@Bexanderthebex
Copy link

@ifokeev can you describe reproductions steps in order to arrive to this scenario?

@goodboy
Copy link
Contributor

goodboy commented May 10, 2023

We have been seeing this same issue for quite a while now as per:
pikers/piker#443

I did a ton of digging as well down to the external snappy go lib which seems to be the root cause.

Recently after deploying to a new nixos install i've found that a similar issue will always show up when querying large data sets

purerpc.grpclib.exceptions.UnknownError: RPC failed with status UNKNOWN (2): EOF

It all seems to be gRPC related for which we have our own async client you can find under the same org.


NB: we're probably going to be dropping mkts outright just because there tends to be a lot of unreliability in terms of pushing / pulling large data sets in general.

Going to be tinkering with the new release of arcticdb in the coming weeks: https://github.com/man-group/ArcticDB

@goodboy
Copy link
Contributor

goodboy commented May 10, 2023

How is it possible to fix this error? only by removing the compression?

No, tried that and it just results in an even more vague rpc error...

See the details of the deep dive here:
pikers/piker#443 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants