Menu
▾
▴
Re: [Postgres-xc-general] replication problem?
|
From: Mason S. <mas...@en...> - 2010-10-14 14:14:00
|
I think this is related to what Koichi pointed out, that you have to resync the other coordinators. You may just want to use the latest code in the git repository so that you do not need to worry about it. On 10/14/10 5:18 AM, Dika Ye wrote: > > I install four datanode/coordinator servers (db01, db02, db03, db04, > each db server include datanode and coordinator service) and one gtm > server, I try to install dbt1-pgxc and run build_db.sh in server db01, > all things seems normal. > > After then, I can check the dbt1 in server db01: > > ################# cut here ######################## > > [root@db01 pgsql]# /usr/local/pgsql/bin/psql -p 5432 -d DBT1 -U postgres > > The session started: 7541 > > psql (8.4.3) > > Type "help" for help. > > DBT1=# \dt > > List of relations > > Schema | Name | Type | Owner > > --------+--------------------+-------+----------- > > public | address | table | messenger > > public | author | table | messenger > > public | cc_xacts | table | messenger > > public | country | table | messenger > > public | customer | table | messenger > > public | item | table | messenger > > public | order_line | table | messenger > > public | orders | table | messenger > > public | shopping_cart | table | messenger > > public | shopping_cart_line | table | messenger > > public | stock | table | messenger > > (11 rows) > > DBT1=# > > ################# cut here ######################## > > But I can't check dbt1 in server db02 or others: > > ################# cut here ######################## > > [root@db02 share]# /usr/local/pgsql/bin/psql -p 5432 -d DBT1 -U postgres > > The session started: 4583 > > FATAL: database "DBT1" does not exist > > psql: FATAL: database "DBT1" does not exist > > [root@db02 share]# The session started: 4584 > > ################# cut here ######################## > > I check my gtm.log, it seems abnormal, please check below: > > ################# cut here ######################## > > LOCATION: ReadCommand, main.c:867 > > 625:1101769024:2010-10-14 17:08:47.060 HKT -LOG: Cleaning up thread state > > LOCATION: GTM_ThreadCleanup, gtm_thread.c:265 > > 626:1101769024:2010-10-14 17:08:49.408 HKT -LOG: Sending transaction > id 4527 > > LOCATION: ProcessBeginTransactionGetGXIDCommand, gtm_txn.c:916 > > 627:1101769024:2010-10-14 17:08:49.426 HKT -LOG: unexpected EOF on > client connection > > LOCATION: ReadCommand, main.c:867 > > 628:1101769024:2010-10-14 17:08:49.426 HKT -LOG: Cleaning up thread state > > LOCATION: GTM_ThreadCleanup, gtm_thread.c:265 > > 629:1101769024:2010-10-14 17:08:54.594 HKT -LOG: Sending transaction > id 4528 > > LOCATION: ProcessBeginTransactionGetGXIDCommand, gtm_txn.c:916 > > 630:1101769024:2010-10-14 17:08:54.612 HKT -LOG: unexpected EOF on > client connection > > LOCATION: ReadCommand, main.c:867 > > 631:1101769024:2010-10-14 17:08:54.612 HKT -LOG: Cleaning up thread state > > LOCATION: GTM_ThreadCleanup, gtm_thread.c:265 > > 632:1101769024:2010-10-14 17:08:54.873 HKT -LOG: Sending transaction > id 4529 > > LOCATION: ProcessBeginTransactionGetGXIDCommand, gtm_txn.c:916 > > 633:1101769024:2010-10-14 17:08:54.892 HKT -LOG: unexpected EOF on > client connection > > LOCATION: ReadCommand, main.c:867 > > 634:1101769024:2010-10-14 17:08:54.892 HKT -LOG: Cleaning up thread state > > LOCATION: GTM_ThreadCleanup, gtm_thread.c:265 > > 635:1101769024:2010-10-14 17:08:57.605 HKT -LOG: Sending transaction > id 4530 > > LOCATION: ProcessBeginTransactionGetGXIDCommand, gtm_txn.c:916 > > 636:1101769024:2010-10-14 17:08:57.625 HKT -LOG: unexpected EOF on > client connection > > LOCATION: ReadCommand, main.c:867 > > 637:1101769024:2010-10-14 17:08:57.625 HKT -LOG: Cleaning up thread state > > LOCATION: GTM_ThreadCleanup, gtm_thread.c:265 > > 638:1101769024:2010-10-14 17:08:58.179 HKT -LOG: Sending transaction > id 4531 > > LOCATION: ProcessBeginTransactionGetGXIDCommand, gtm_txn.c:916 > > 639:1101769024:2010-10-14 17:08:58.197 HKT -LOG: unexpected EOF on > client connection > > LOCATION: ReadCommand, main.c:867 > > 640:1101769024:2010-10-14 17:08:58.197 HKT -LOG: Cleaning up thread state > > LOCATION: GTM_ThreadCleanup, gtm_thread.c:265 > > 641:1101769024:2010-10-14 17:09:01.424 HKT -LOG: Sending transaction > id 4532 > > LOCATION: ProcessBeginTransactionGetGXIDCommand, gtm_txn.c:916 > > 642:1101769024:2010-10-14 17:09:01.443 HKT -LOG: unexpected EOF on > client connection > > LOCATION: ReadCommand, main.c:867 > > 643:1101769024:2010-10-14 17:09:01.443 HKT -LOG: Cleaning up thread state > > LOCATION: GTM_ThreadCleanup, gtm_thread.c:265 > > ################# cut here ######################## > > What will cause these, thanks. > > Best wishes, > > Dika.Ye > ------------------------------------------------------------------------------------ > NTT Com Asia Network Systems (Guangzhou) Company Limited. > > Tel: (86)-20-8113 0687 > Fax: (86)-20-8135 0322 > Mobile: (86)-135 3371 0342 > Email: di...@nt... <mailto:di...@nt...> > > www.ntt.com.hk <http://www.ntt.com.hk/> > > > ------------------------------------------------------------------------------ > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2& L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today. > http://p.sf.net/sfu/beautyoftheweb > > > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > -- Mason Sharp EnterpriseDB Corporation The Enterprise Postgres Company This e-mail message (and any attachment) is intended for the use of the individual or entity to whom it is addressed. This message contains information from EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive this for the intended recipient, any use, dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete this message. |
