-
Notifications
You must be signed in to change notification settings - Fork 590
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
Issue with new files on minio storage #17991
Comments
Would you mind sharing the logs for the compute pods? |
Logs:
After few minutes:
|
From diagnose:
|
I think there are two issues here:
For issue 1, I can successfully reproduce and it seems to be related to #18017. Let's wait for the PR to see whether it can resolve the issue. For issue 2, I cannot successfully reproduce. Based on the implementation, I think the panic can happen only when there is some corruption in the metadata. Can you consistently reproduce issue 2? Would you mind double checking whether the meta store backend pg db is healthy and never crashes ? |
For issue 2, It's difficult to say because it was one time and right now I'm not able to reproduce it. |
I think this can be fixed in #18017 |
close as completed |
Describe the bug
After creating a source and a materialized view in the RisingWave application, new data does not appear in the sink, despite uploading new files to the MinIO storage.
Error message/log
To Reproduce
First clone https://github.com/risingwavelabs/risingwave go to docer and run:
Create new bucket on minio
examples
Create source:
Then create view:
Please create table and sink:
Then upload file
expanses.ndjson
with content:Please run sql after few seconds
SELECT * FROM stats;
Expected behavior
I expect to see new records in table
stats
.How did you deploy RisingWave?
docker-compose up, docker compose is:
The version of RisingWave
RisingWave 1.10.
Additional context
No response
The text was updated successfully, but these errors were encountered: