How can I fix: DB::Exception: bad size of marks file

829 views
Skip to first unread message

ste...@activitystream.com

unread,
Jun 27, 2017, 7:49:38 AM6/27/17
to ClickHouse
Hi,

What is this and how can I fix it?

46, host: clickhouse, port: 8123; Code: 246, e.displayText() = DB::Exception: bad size of marks file `../data/.../20170501_20170529_4890_4932_2/classification%2Etype.null.mrk':432, must be: 224: (while reading column classification.type): (while reading from part ../data/../20170501_20170529_4890_4932_2/ from mark 3 to 4), e.what() = DB::Exception


Regards,
 -Stefán

mvav...@cloudflare.com

unread,
Jun 27, 2017, 10:19:26 PM6/27/17
to ClickHouse
The marks file for this part/column is corrupted. It could be a random disk error, but all the times I've seen it, the disk was going to die soon.
If it's a replicated table, you can just remove the part from disk and it will recover from peer replicas.
If it's unreplicated table, you can try to recover the data from columns, but they're written in native format and I'm not sure if there's an easy way how to reinsert them.

ste...@activitystream.com

unread,
Jul 2, 2017, 1:40:24 PM7/2/17
to ClickHouse

Thank you.

Jason Piper

unread,
May 6, 2018, 3:41:21 AM5/6/18
to ClickHouse
I had the same issue which was caused by a zookeeper cluster in a bad state.

To get the problem to fix, not only did I have to remove the part from the file, but I had to restart the clickhouse server on the node presenting this error as well.
Reply all
Reply to author
Forward
0 new messages