Pivotal Knowledge Base

Follow

segment instance crash with error "could not find block containing chunk"

Environment 

Product Version
Pivotal Greenplum (GPDB) 4.3.8.x
OS All OS
Others   

Symptom

Segment instance will crash with below error message:

ERROR","XX000","could not find block containing chunk 0x16cde720 (context 'DataSourceContext') (aset.c:1467) (mcxt.c:477)"
1 0xb0a52e postgres errstart + 0x4de
2 0xb457a9 postgres MemoryContextError + 0x619
3 0xb41bf5 postgres <symbol not found> + 0xb41bf5
4 0x7fc0957acfa3 libz.so.1 deflateEnd + 0x73
5 0xb29a75 postgres <symbol not found> + 0xb29a75
6 0x95681f postgres <symbol not found> + 0x95681f
7 0x9555a8 postgres <symbol not found> + 0x9555a8
8 0x544279 postgres AbortTransaction + 0x369
9 0x547945 postgres AbortCurrentTransaction + 0x25
10 0x99a127 postgres PostgresMain + 0x537
11 0x8fa50e postgres <symbol not found> + 0x8fa50e
12 0x8fd290 postgres PostmasterMain + 0xff0
13 0x7ff30f postgres main + 0x44f
14 0x7fc092895d5d libc.so.6 __libc_start_main + 0xfd
15 0x4c4a19 postgres <symbol not found> + 0x4c4a19 

Cause

This is a known issue in GPDB v438x, when "gp_workfile_compress_algorithm" set to 'zlib' by default. This may cause improper memory handling and finally cause segment crash with signal 6. 

Resolution

To prevent this issue from happening, we can either suggest the customer upgrade to version 4.3.9.0 and above or set this parameter "gp_workfile_compress_algorithm" to "none".

 

 

Comments

Powered by Zendesk