-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
[Bug] SIGSEGV: segmentation violation in banyand/query.(*topNQueryProcessor).Rev.func1() #12219
Comments
Your configuration is not well formatted. Please correct them. And what does And we don't have banyandb-helm 0.2 release, how do you deploy the database? |
@lujiajing1126 What is the case of occurring this error? |
It`s docker-compose.yml file. Right way to run it: |
Are you using docker quick start? We haven't upgraded it to latest. It needs v10 oap and latest banyandb 0.6. |
This error is easy to fix, @Almot77 but we want to know how you could trigger it, as we have run many tests to verify features. |
The nil error is fixed by https://github.com/apache/skywalking-banyandb/pull/445/files#diff-695073ea8dec3fcdaae77a3fcfb4eabc7290daade34399aee1de429999d7b476R124 But the error below is a bit tricky.
@Almot77 Would you pls use the last banyandb image built from apache/skywalking-banyandb#445 to output more context about this error? If you have an appropriate docker environment, issuing |
I reopened this as we don't know gow this happens. @Almot77 We will need more, could you package the whole data folder to us, then we could address what is the illegal data. Or could you share how we could reproduce this. |
Okay, i'l test it now. We use php application in docker + sw php libay for trace collecting + grafana dashboards (made from sw examples for grafana) |
How to install go libaries ?
$ make docker.build
I try get libs:
|
Or simply, try dev image from here, https://github.com/apache/skywalking-banyandb/pkgs/container/skywalking-banyandb/215721861?tag=c8270670d47a9c6caa2661af434157656c4b7eaf |
Ok, db start success, but i have 3 troubles:
Query to Grafana query inspect:
Query:
in docker-compose i have env SW_DCS_MAX_INBOUND_MESSAGE_SIZE when i run Skywalking:
When i use elastic - i have no doubles, i have all panels, and i still have a lot gRPC messages :) I attach my docker log |
If your data is just for testing, could you tar the whole data folder and upload here? It would be eaiser to verified your query through the same dataset. |
Its data from skywalking php exporter, i don`t now how to collect and save it, may be export docker container with collected data ? |
SW_DCS_MAX_INBOUND_MESSAGE_SIZE is not for this case. We need to check BanyanDB Java client(storage/banyandb/... in application.yml) for relative settings(maybe missed for now). |
@Almot77 could you mount your host path to the banyandb's |
Sure.
banyandb container log: tmp: |
@Almot77 Could you try ghcr.io/apache/skywalking-banyandb:4270ef1ff8adab3c5de68f9b5c467e838d8bc8ae which contains the patch raised by apache/skywalking-banyandb#447 |
@Almot77 Thank you for your feedback. Since there are several issues here, let's focus on the "errors" in bdb's log. I have created a debug image If you're interested, please join our Slack channel at https://skywalking.apache.org/docs/main/next/en/guides/community/. This will help us communicate more efficiently. |
Hi! I send request to join, thank you. |
Please verify through https://github.com/apache/skywalking-banyandb/pkgs/container/skywalking-banyandb/220984457?tag=6b79695976e8a7531c70f785a100193b6863495d Both bugs should be fixed. |
Search before asking
Apache SkyWalking Component
BanyanDB (apache/skywalking-banyandb)
What happened
Server crash on segmentation fault in docker. I use :latest SW and BYDB images (new releases).
What you expected to happen
How to reproduce
Docker compose
docker compose --profile banyandb up -d
Anything else
No response
Are you willing to submit a pull request to fix on your own?
Code of Conduct
The text was updated successfully, but these errors were encountered: