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
column format error in part gc thread #1198
Comments
@dogauzuncukoglu it looks like the columns.txt file in this part 20240205_447510457035260771_447510457035260771_1_447510459719091038 has wrong encoded text. Does it happen for many parts or just this one? |
Hi @dogauzuncukoglu, would you please check the file nudles listed? |
I see that happening in a few tables on different parts. How can I get the columns.txt file for specific parts on S3? |
hi, @ozcelgozde @dogauzuncukoglu . You can download the part data from S3 by using the relative path "bucket/{YOUR_PREFIX}/part_id/data". part_id is the uuid of part reporting such error in the log. You can get part_id from system.cnch_parts by using part name |
@ozcelgozde @dogauzuncukoglu any updates on this? are you still encountering this issue? |
We are still encountering the issue because we were not able to update Byconity version if any fixes were introduced due to blocking issue
its still trying to delete a part from February. Ofcourse this part no longer exists in cnch_parts table so I cannot check the part_id to look in s3. Something might be stuck on cache or fdb |
hi @ozcelgozde . Such part has been moved to trashed items, so you have to access FDB to get the part_id for downloading this part. The key format for trashed items in KV is GCTRASH_{table_uuid}_{part_name}. In the lastest version of ByConity, part_id is recorded in server_part_log. |
@ozcelgozde Does the method @smmsmm1988 suggested work for you ? |
Bug Report
Briefly describe the bug
We started observing an error being logged on the server component. Here is the error log. If we can collect anything else that might be helpful please let us know.
The result you expected
How to Reproduce
Version
cc4e467
The text was updated successfully, but these errors were encountered: