How is this related to web2py? On Sunday, 2 September 2018 11:03:30 UTC-7, Soumitra Bhandary wrote: > > Hi, > > I have performed below steps and after that , it seems that BDR > replication is broken . No DML statement is getting replicated and DDL > statements getting hanged . Any suggestion to this please . > > > 1. Executed in Postgres NODE 1 : Below statements : > > Insert into test_bdr_16 values(generate_series(1,100000000)) ; > commit ; > Insert into test_bdr_17 values(generate_series(1,100000000)) ; > commit ; > Insert into test_bdr_18 values(generate_series(1,100000000)) ; > commit ; > Insert into test_bdr_19 values(generate_series(1,100000000)) ; > > commit ; > > 2. Once transaction got finished it took around 35 Minutes to clear the > retention log bytes from one node to another . > > And both the node DB size was same 22 GB . > > 3. After that I executed in the same DB some normal DDL . It got hanged . > > create table test12345(id int primary key ) ; > > Postgres LOG : > > 2018-08-24 10:31:47.365 GMT-dbname -18552 LOG: statement: create table > test12345(id int primary key ) ; > 2018-08-24 10:31:47.366 GMT-dbname -18552 LOG: DDL LOCK TRACE: acquiring > in mode <ddl_lock> for (bdr (6587226886794590652,2,16395,)) > [tracelevel=statement] > 2018-08-24 10:31:47.366 GMT-dbname -18552 STATEMENT: create table > test12345(id int primary key ) ; > 2018-08-24 10:32:02.493 GMT-[unknown]-19545 LOG: connection received: > host=127.0.0.1 port=60560 > 2018-08-24 10:32:02.494 GMT-dbname -19545 LOG: connection authorized: > user=postgres database=dbname > 2018-08-24 10:32:02.495 GMT-dbname -19545 LOG: disconnection: session > time: 0:00:00.002 user=postgres database=dbname host=127.0.0.1 port=60560 > 2018-08-24 10:32:32.507 GMT-[unknown]-21062 LOG: connection received: > host=127.0.0.1 port=60728 > 2018-08-24 10:32:32.508 GMT-dbname -21062 LOG: connection authorized: > user=postgres database=dbname > > 4. After cancelling the statement I executed simple DML which got > succeeded in same postgres node but did not replicate in the other node . > > 5. I have verified all the bdr related system views which looks perfect to > me as per the replication status in both nodes . > > select * from bdr.bdr_nodes ; > -[ RECORD 1 > ]------+------------------------------------------------------------------------------------------ > node_sysid | XXXXXXXXXXXXXXXXXXXXX > node_timeline | 2 > node_dboid | XXXXXXXX > node_status | r > node_name | XXXXXXXXXXXXXXXXXXXXXXXXXXXXX.com > node_local_dsn | host=XXXXXXXXXXXXXXXXXXXXXXXXX port=5432 dbname=db > node_init_from_dsn | > node_read_only | f > node_seq_id | > -[ RECORD 2 > ]------+------------------------------------------------------------------------------------------ > node_sysid | XXXXXXXXXXXXXXXXXXXXX > node_timeline | 3 > node_dboid | XXXXXXXX > node_status | r > node_name | XXXXXXXXXXXXXXXXXXXXXXXXXXXXX.com > node_local_dsn | host=XXXXXXXX port=5432 dbname=dbname > node_init_from_dsn | user=XXXXXXXX' port=5432 dbname=dbname > node_read_only | f > node_seq_id | > > > select * from pg_replication_slots ; > -[ RECORD 1 ]+---------------------------------------- > slot_name | bdr_16395_6588xxxxxxxx8855xxxxx48_3_16395__ > plugin | bdr > slot_type | logical > datoid | xxxxxx > database | xxxxxx > active | t > xmin | > catalog_xmin | 96393353 > restart_lsn | 1E/E6898ED0 >
-- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
