We have migrated to new Google sites!

gpfdist error

Resolved gpfdist error in GPDB 4.2.8.1

1. The Greenplum Database gpfdist utility failed with a SIGSEGV error when the utility received a empty request with two consecutive return characters “\n\n”.
2. In some cases when network load was heavy, the Greenplum Database utility gpfdist intermittently failed with this error: gpfdist closed connection to server

Known bug GPDB 4.2.8.1

1. When a query joins an external table that uses the gpfdist protocol with a heap table, the planner might choose an incorrect plan that returns no results. Workaround: This can be avoided by running ANALYZE on the query before running the query.
2. The bytenum field (byte offset in the load file where the error occurred) in the error log when using gpfdist with data in text format errors is not populated, making it difficult to find the location of an error in the source file.
3. Running more than one gpfilespace command concurrently with itself to move either temporary files (--movetempfilespace) or transaction files (--movetransfilespace) to a new filespace can in some circumstances cause OID inconsistencies. Workaround: Do not run more than one gpfilespace command concurrently with itself. If an OID inconsistency is introduced gpfilespace --movetempfilespace or gpfilespace --movetransfilespace can be used to revert to the default filespace.
4. gpfdist shows the error “Address already in use” after successfully binding to socket IPv6.Greenplum supports IPv4 and IPv6. However, gpfdist fails to bind to socket IPv4, and shows the message “Address already in use”, but binds successfully to socket IPv6.

Report abuse