Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Ywqho-0006jI-KH for pgsql-admin@arkaria.postgresql.org; Mon, 25 May 2015 11:38:04 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Ywqhn-0000VC-6A for pgsql-admin@arkaria.postgresql.org; Mon, 25 May 2015 11:38:03 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Ywqhm-0000V1-0R for pgsql-admin@postgresql.org; Mon, 25 May 2015 11:38:02 +0000 Received: from smtp.nixsolutions.com ([91.208.153.2]) by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1Ywqhi-0003JP-HF for pgsql-admin@postgresql.org; Mon, 25 May 2015 11:38:00 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=nixsolutions.com; s=mail; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:To:MIME-Version:From:Date:Message-ID; bh=tvCoccchqukqJ6nPgS8GymeJomvWZ+TeTXRSDFFSDns=; b=OsfY4eEDf4iPTfZBaWS9lvLg39zGXVxSesZWYHfI4ZeJfVdckmgP7KiTHjgWnaAy/OzYvxhQmIzrj4jqWLs7bqp9/keNdBx3rgaZKw5P3NmZ6fpuz3CdQO9JzJZ+wPAB+ipUyuuinviGiMOCLKZ/hBQ0+4IRa0pLBRaFdRsU4V8=; Received: from [10.10.100.113] by smtp.nixsolutions.com with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.76) (envelope-from ) id 1Ywqis-0002cc-1e; Mon, 25 May 2015 14:39:11 +0300 Message-ID: <556309B5.1010305@nixsolutions.com> Date: Mon, 25 May 2015 14:38:29 +0300 From: Mikhail Levandovskiy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: "Sagar R. Jadhav" , pgsql-admin@postgresql.org Subject: Re: postgresql-9.4-BDR replication issue References: <5562FEAB.1040903@nixsolutions.com> <2d5d14e5a4ceda065ea28ad04bf9409c@email.shreeyansh.com> In-Reply-To: <2d5d14e5a4ceda065ea28ad04bf9409c@email.shreeyansh.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org No, i've already runned SELECT bdr.bdr_node_join_wait_for_ready(); on first and second nodes, and on first node it shows: SELECT bdr.bdr_node_join_wait_for_ready(); bdr_node_join_wait_for_ready ------------------------------ (1 row) but on second it hung. On 25/05/15 14:04, Sagar R. Jadhav wrote: > This error may cause because of on node1 you did not execute the function bdr.bdr_node_join_wait_for_ready(); > try to execute it and also execute it on second node after executing bdr.bdr_group_join(....). > > > > > -- > Thanks & Regards, > Sagar R. Jadhav > Ph: +91-9552688400 / 7400 > Skype ID: sagarjdhv24 > Email ID: sagar.jadhav@shreeyansh.com > www.shreeyansh.com > > May 25 2015 3:51 AM, "Mikhail Levandovskiy" wrote: >> Hi all. >> >> I've installed postgresql-9.4 with BDR from its official repository, and >> trying to create replication group with database on two nodes: >> on first node runned: >> CREATE EXTENSION btree_gist; >> CREATE EXTENSION bdr; >> SELECT bdr.bdr_group_create(local_node_name := 'node1', >> node_external_dsn := 'host=10.10.1.39 dbname=bdrdemo2'); >> >> on second node runned: >> CREATE EXTENSION btree_gist; >> CREATE EXTENSION bdr; >> SELECT bdr.bdr_group_join(local_node_name := 'node2', node_external_dsn >> := 'host=10.10.5.107 dbname=bdrdemo2', join_using_dsn := >> 'host=10.10.1.39 dbname=bdrdemo2' ); >> >> And then getting this error on second node: >> < 2015-05-25 03:38:37.714 PDT >LOG: starting background worker process >> "bdr db: bdrdemo" >> < 2015-05-25 03:38:37.731 PDT >ERROR: previous init failed, manual >> cleanup is required >> < 2015-05-25 03:38:37.731 PDT >DETAIL: Found bdr.bdr_nodes entry for >> bdr (6152755282451262703,1,16407,) with state=i in remote bdr.bdr_nodes >> < 2015-05-25 03:38:37.731 PDT >HINT: Remove all replication identifiers >> and slots corresponding to this node from the init target node then drop >> and recreate this database and try again >> < 2015-05-25 03:38:37.732 PDT >LOG: worker process: bdr db: bdrdemo >> (PID 25402) exited with exit code 1 >> >> I've tried to remove all replication slots on both nodes: >> select * from pg_replication_slots; >> select pg_drop_replication_slot('replication_slot_name'); >> tried to clean bdr.bdr_nodes, bdr.bdr_node_slots and bdr.bdr_connections, >> tried to drop database and create it again - all was useless. >> >> What's missed? >> >> Thanks. >> >> -- >> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgsql-admin -- ------------------------ Best regards, System Administration Dept. NIX Solutions Ltd. -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin