LOG: worker process: worker0 [pipeline] (PID 16887) was terminated by signal 11: Segmentation fault #72
Comments
|
@gb198871 thanks for the report! Is there no stack trace in the logs? |
|
@derekjn All are build by master pipelinedb\ pipeline_kafka\ librdkafka ，how can i config print stack trace logs ? thanks!!! |
|
2017-11-18 17:26:59 CSTLOG: 00000: [pipeline_kafka] kafka_userlog_stream <- pipelineUserlog (PID 4448): librdkafka error: [thrd:slave-67:9090/bootstrap]: slave-67:9090/3: Receive failed: Disconnected |
|
Relevant stack trace: @gb198871 thanks, this is very helpful! |
|
@derekjn this is a bug or configuration problems ？ can repair ？thanks！ |
|
@gb198871 are you able to provide any sample data to reproduce this issue with? If not we'll keep digging but that would make it really easy for us. |
|
I am try to debug code,find out throw exception row,but i don't know how to repair: }` sample data produce to kafka topic "pipelineUserlog" 40000 record one second： I discovery when add config on pipeline_kafka.c kafka_produce_msg function recompile: and comsumer kafka data batchSize change smaller 500: It is running more than 24 hour ,did not happend ' was terminated by signal 11: Segmentation fault ' error. Another how to configuration optimization pipeinedb.conf ? thank you very much! |
|
I am try debug code ,find throw exception on this row,but i don’t know how to repairkkk2017-11-29 09:09:18 CSTLOG: [pipeline_kafka] kafka_userlog_stream <- pipelineUserlog (PID 9359): librdkafka error: [thrd:slave-75:9090/2]: slave-75:9090/2: Receive failed: Disconnected Always print this error but running normal still |
hi,
I only use pipeline_kafka.consume_begin is no propelm, but use pipeline_kafka.emit_tuple have this propelm.
CREATE STREAM kafka_userlog_stream (time_tamp bigint, uuid text, age bigint,a1 text,a2 bigint,a3 numeric,a4 bool);
CREATE CONTINUOUS VIEW LOG_COUNT_VIEW WITH (sw = '30 minute') as select count(*) from kafka_userlog_stream;
CREATE TABLE DIM_AGE(begin_age int,end_age int, catalog varchar(300),PRIMARY KEY(begin_age,end_age));
insert into DIM_AGE values(0,30,'少年');
insert into DIM_AGE values(30,60,'中年');
insert into DIM_AGE values(60,120,'老年');
CREATE CONTINUOUS TRANSFORM CT_USER_AGE_CATALOG_TOKAFKA AS SELECT s.time_tamp::bigint, s.uuid::text,a.begin_age::int,s.a2::text,a.catalog::text FROM kafka_userlog_stream s JOIN DIM_AGE a ON s.age >= a.begin_age and s.age >= a.end_age THEN EXECUTE PROCEDURE pipeline_kafka.emit_tuple('pipelinedbTriggerTest');
SELECT pipeline_kafka.consume_begin('pipelineUserlog', 'kafka_userlog_stream',format := 'text', delimiter := E'|',batchsize := 1000, maxbytes := 32000000, parallelism := 5,start_offset := '-1');
error log：
LOG: worker process: worker0 [pipeline] (PID 16887) was terminated by signal 11: Segmentation fault
DETAIL: Failed process was running: worker0 [pipeline]
LOG: terminating any other active server processes
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
LOG: all server processes terminated; reinitializing
LOG: database system was interrupted; last known up at 2017-11-06 18:14:24 CST
LOG: database system was not properly shut down; automatic recovery in progress
LOG: redo starts at 18/44E7DEE8
LOG: unexpected pageaddr 17/FA5CC000 in log segment 000000010000001800000045, offset 6078464
LOG: redo done at 18/455CBB68
LOG: last completed transaction was at log time 2017-11-06 18:16:55.555403+08
LOG: MultiXact member wraparound protections are now enabled
The text was updated successfully, but these errors were encountered: