From: Julian <jul...@gm...> - 2013-10-02 15:53:22
|
Dear Sir, I have a cluster with 3 coordinators and 3 datanodes on 3 VM, today i was try to added a new coordinator to the cluster, when i using command "psql postgres -f coordinator.sql -p 5455" to restore the backup file to the new coordinator. Then i got this message : psql:coordinator-dump.sql:105: connection to server was lost In the log file: ---------------------------------------------------------------------------------------------------------------------------------------------------------------- 2013-10-02 23:00:09.811 CST,,,29061,,524c34de.7185,2,,2013-10-02 22:59:42 CST,,0,LOG,00000,"server process (PID 29094) was terminated by signal 11: Segmentation fault","Failed process was r unning: CREATE TABLE user_info_hash ( id integer NOT NULL, firstname text, lastname text, info text ) DISTRIBUTE BY HASH (id) TO NODE (dn2,dn1,dn3);",,,,,,,,"" 2013-10-02 23:00:09.811 CST,,,29061,,524c34de.7185,3,,2013-10-02 22:59:42 CST,,0,LOG,00000,"terminating any other active server processes",,,,,,,,,"" ------------------------------------------------------------------------------------------------------------------------------------------------------------------ refer to http://postgres-xc.sourceforge.net/docs/1_1/add-node-coordinator.html Is there something i doing worng? Thanks for your kindly reply. And sorry for my poor english. Best regards. |
From: Koichi S. <koi...@gm...> - 2013-10-03 01:31:26
|
You cannot add a coordinator in such a way. There're many issued to be resolved internally. You can configure and operate whole cluster with pgxc_ctl to get handy way to add coordinator/datanode. I understand you have your cluster configured without pgxc_ctl. In this case, adding coordinator manually could be a bit complicated work. Sorry, I've not uploaded the detailed step to do it. Whole steps will be found in add_coordinatorMaster() function defined in coord_cmd.c of pgxc_ctl source code. It will be found at contrib/pgxc_ctl in the release material. Please allow a bit of time to find my time to upload this information to XC wiki. Or, you can backup whole database with pg_dumpall, then reconfigure new xc cluster with additional coordinator, and then restore the backup. Regards; --- Koichi Suzuki 2013/10/3 Julian <jul...@gm...> > Dear Sir, > > I have a cluster with 3 coordinators and 3 datanodes on 3 VM, today i > was try to added a new coordinator to the cluster, when i using command > "psql postgres -f coordinator.sql -p 5455" to restore the backup file to > the new coordinator. > > Then i got this message : > > psql:coordinator-dump.sql:105: connection to server was lost > > In the log file: > > ---------------------------------------------------------------------------------------------------------------------------------------------------------------- > 2013-10-02 23:00:09.811 CST,,,29061,,524c34de.7185,2,,2013-10-02 > 22:59:42 CST,,0,LOG,00000,"server process (PID 29094) was terminated by > signal 11: Segmentation fault","Failed process was r > unning: CREATE TABLE user_info_hash ( > id integer NOT NULL, > firstname text, > lastname text, > info text > ) > DISTRIBUTE BY HASH (id) > TO NODE (dn2,dn1,dn3);",,,,,,,,"" > 2013-10-02 23:00:09.811 CST,,,29061,,524c34de.7185,3,,2013-10-02 > 22:59:42 CST,,0,LOG,00000,"terminating any other active server > processes",,,,,,,,,"" > > ------------------------------------------------------------------------------------------------------------------------------------------------------------------ > refer to > http://postgres-xc.sourceforge.net/docs/1_1/add-node-coordinator.html > > Is there something i doing worng? > > > Thanks for your kindly reply. > > And sorry for my poor english. > > > Best regards. > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most > from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > |
From: Julian <jul...@gm...> - 2013-10-04 09:59:47
|
Dear Sir, My cluster has configured by pg_ctl now, but till filed. Error message -------------------------------------------------------------------------------- PGXC add coordinator master coord4 node4 20004 20010 /opt/pgxc/nodes/coord …... Actual Command: ssh pgxc@node4 "( pg_ctl start -Z restoremode -D /opt/pgxc/nodes/coord -o -i ) > /tmp/squeeze-10-200_STDOUT_2618_16 2>&1" < /dev/null > /dev/null 2>&1 Bring remote stdout: scp pgxc@node4:/tmp/squeeze-10-200_STDOUT_2618_16 /tmp/STDOUT_2618_17 > /dev/null 2>&1 SET SET psql:/tmp/GENERAL_2618_15:12: ERROR: role "pgxc" already exists ALTER ROLE REVOKE REVOKE GRANT GRANT CREATE NODE CREATE NODE CREATE NODE CREATE NODE CREATE NODE CREATE NODE You are now connected to database "postgres" as user "pgxc". SET SET SET SET SET COMMENT CREATE EXTENSION COMMENT SET SET SET psql:/tmp/GENERAL_2618_15:92: connection to server was lost Actual Command: ssh pgxc@node4 "( pg_ctl stop -Z restoremode -D /opt/pgxc/nodes/coord ) > /tmp/squeeze-10-200_STDOUT_2618_18 2>&1" < /dev/null > /dev/null 2>&1 Bring remote stdout: scp pgxc@node4:/tmp/squeeze-10-200_STDOUT_2618_18 /tmp/STDOUT_2618_19 > /dev/null 2>&1 Starting coordinator master coord4 Done. CREATE NODE CREATE NODE CREATE NODE ALTER NODE ---------------------------------------------------------------- Error log -------------------------------------------------------------------- ERROR: role "pgxc" already exists STATEMENT: CREATE ROLE pgxc; LOG: server process (PID 3013) was terminated by signal 11: Segmentation fault DETAIL: Failed process was running: CREATE TABLE user_info_hash ( id integer NOT NULL, firstname text, lastname text, info text ) DISTRIBUTE BY HASH (id) TO NODE (datanode1,datanode2,datanode3); 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 co rrupted shared memory. HINT: In a moment you should be able to reconnect to the database and repeat your command. --------------------------------------------------------------------------- Any comments are appreciated Best Regards, -- Julian 使用 Sparrow (http://www.sparrowmailapp.com/?sig) 發信 On 2013年10月3日Thursday at 上午9:31, Koichi Suzuki wrote: > You cannot add a coordinator in such a way. There're many issued to be resolved internally. You can configure and operate whole cluster with pgxc_ctl to get handy way to add coordinator/datanode. > > I understand you have your cluster configured without pgxc_ctl. In this case, adding coordinator manually could be a bit complicated work. Sorry, I've not uploaded the detailed step to do it. > > Whole steps will be found in add_coordinatorMaster() function defined in coord_cmd.c of pgxc_ctl source code. It will be found at contrib/pgxc_ctl in the release material. > > Please allow a bit of time to find my time to upload this information to XC wiki. > > Or, you can backup whole database with pg_dumpall, then reconfigure new xc cluster with additional coordinator, and then restore the backup. > > Regards; > > --- > Koichi Suzuki > > > > > 2013/10/3 Julian <jul...@gm... (mailto:jul...@gm...)> > > Dear Sir, > > > > I have a cluster with 3 coordinators and 3 datanodes on 3 VM, today i > > was try to added a new coordinator to the cluster, when i using command > > "psql postgres -f coordinator.sql -p 5455" to restore the backup file to > > the new coordinator. > > > > Then i got this message : > > > > psql:coordinator-dump.sql:105: connection to server was lost > > > > In the log file: > > ---------------------------------------------------------------------------------------------------------------------------------------------------------------- > > 2013-10-02 23:00:09.811 CST,,,29061,,524c34de.7185,2,,2013-10-02 > > 22:59:42 CST,,0,LOG,00000,"server process (PID 29094) was terminated by > > signal 11: Segmentation fault","Failed process was r > > unning: CREATE TABLE user_info_hash ( > > id integer NOT NULL, > > firstname text, > > lastname text, > > info text > > ) > > DISTRIBUTE BY HASH (id) > > TO NODE (dn2,dn1,dn3);",,,,,,,,"" > > 2013-10-02 23:00:09.811 CST,,,29061,,524c34de.7185,3,,2013-10-02 > > 22:59:42 CST,,0,LOG,00000,"terminating any other active server > > processes",,,,,,,,,"" > > ------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > refer to > > http://postgres-xc.sourceforge.net/docs/1_1/add-node-coordinator.html > > > > Is there something i doing worng? > > > > > > Thanks for your kindly reply. > > > > And sorry for my poor english. > > > > > > Best regards. > > > > ------------------------------------------------------------------------------ > > October Webinars: Code for Performance > > Free Intel webinars can help you accelerate application performance. > > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > > the latest Intel processors and coprocessors. See abstracts and register > > > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk > > _______________________________________________ > > Postgres-xc-general mailing list > > Pos...@li... (mailto:Pos...@li...) > > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > |
From: Koichi S. <koi...@gm...> - 2013-10-07 06:41:03
|
I supporte the error was encountered in pg_resgtore and pgxc is the owner of postgres-XC in your pgxc_ctl.conf file. The issue looks some (not necessarily just one) bugs. Can I have log files at the new coordinator? This may have some more information on the issue. Regards; --- Koichi Suzuki 2013/10/4 Julian <jul...@gm...> > Dear Sir, > > My cluster has configured by pg_ctl now, but till filed. > > Error message > > -------------------------------------------------------------------------------- > PGXC add coordinator master coord4 node4 20004 20010 /opt/pgxc/nodes/coord > …... > Actual Command: ssh pgxc@node4 "( pg_ctl start -Z restoremode -D > /opt/pgxc/nodes/coord -o -i ) > /tmp/squeeze-10-200_STDOUT_2618_16 2>&1" < > /dev/null > /dev/null 2>&1 > Bring remote stdout: scp pgxc@node4:/tmp/squeeze-10-200_STDOUT_2618_16 > /tmp/STDOUT_2618_17 > /dev/null 2>&1 > SET > SET > psql:/tmp/GENERAL_2618_15:12: ERROR: role "pgxc" already exists > ALTER ROLE > REVOKE > REVOKE > GRANT > GRANT > CREATE NODE > CREATE NODE > CREATE NODE > CREATE NODE > CREATE NODE > CREATE NODE > You are now connected to database "postgres" as user "pgxc". > SET > SET > SET > SET > SET > COMMENT > CREATE EXTENSION > COMMENT > SET > SET > SET > psql:/tmp/GENERAL_2618_15:92: connection to server was lost > Actual Command: ssh pgxc@node4 "( pg_ctl stop -Z restoremode -D > /opt/pgxc/nodes/coord ) > /tmp/squeeze-10-200_STDOUT_2618_18 2>&1" < > /dev/null > /dev/null 2>&1 > Bring remote stdout: scp pgxc@node4:/tmp/squeeze-10-200_STDOUT_2618_18 > /tmp/STDOUT_2618_19 > /dev/null 2>&1 > Starting coordinator master coord4 > Done. > CREATE NODE > CREATE NODE > CREATE NODE > ALTER NODE > ---------------------------------------------------------------- > > Error log > -------------------------------------------------------------------- > ERROR: role "pgxc" already exists > STATEMENT: CREATE ROLE pgxc; > LOG: *server process (PID 3013) was terminated by signal 11: > Segmentation fault* > DETAIL: Failed process was running: CREATE TABLE user_info_hash ( > id integer NOT NULL, > firstname text, > lastname text, > info text > ) > DISTRIBUTE BY HASH (id) > TO NODE (datanode1,datanode2,datanode3); > 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 co > rrupted shared memory. > HINT: In a moment you should be able to reconnect to the database and > repeat your command. > --------------------------------------------------------------------------- > > Any comments are appreciated > > > Best Regards, > > -- > Julian > 使用 Sparrow <http://www.sparrowmailapp.com/?sig> 發信 > > On 2013年10月3日Thursday at 上午9:31, Koichi Suzuki wrote: > > You cannot add a coordinator in such a way. There're many issued to be > resolved internally. You can configure and operate whole cluster with > pgxc_ctl to get handy way to add coordinator/datanode. > > I understand you have your cluster configured without pgxc_ctl. In this > case, adding coordinator manually could be a bit complicated work. Sorry, > I've not uploaded the detailed step to do it. > > Whole steps will be found in add_coordinatorMaster() function defined in > coord_cmd.c of pgxc_ctl source code. It will be found at contrib/pgxc_ctl > in the release material. > > Please allow a bit of time to find my time to upload this information to > XC wiki. > > Or, you can backup whole database with pg_dumpall, then reconfigure new xc > cluster with additional coordinator, and then restore the backup. > > Regards; > > --- > Koichi Suzuki > > > 2013/10/3 Julian <jul...@gm...> > > Dear Sir, > > I have a cluster with 3 coordinators and 3 datanodes on 3 VM, today i > was try to added a new coordinator to the cluster, when i using command > "psql postgres -f coordinator.sql -p 5455" to restore the backup file to > the new coordinator. > > Then i got this message : > > psql:coordinator-dump.sql:105: connection to server was lost > > In the log file: > > ---------------------------------------------------------------------------------------------------------------------------------------------------------------- > 2013-10-02 23:00:09.811 CST,,,29061,,524c34de.7185,2,,2013-10-02 > 22:59:42 CST,,0,LOG,00000,"server process (PID 29094) was terminated by > signal 11: Segmentation fault","Failed process was r > unning: CREATE TABLE user_info_hash ( > id integer NOT NULL, > firstname text, > lastname text, > info text > ) > DISTRIBUTE BY HASH (id) > TO NODE (dn2,dn1,dn3);",,,,,,,,"" > 2013-10-02 23:00:09.811 CST,,,29061,,524c34de.7185,3,,2013-10-02 > 22:59:42 CST,,0,LOG,00000,"terminating any other active server > processes",,,,,,,,,"" > > ------------------------------------------------------------------------------------------------------------------------------------------------------------------ > refer to > http://postgres-xc.sourceforge.net/docs/1_1/add-node-coordinator.html > > Is there something i doing worng? > > > Thanks for your kindly reply. > > And sorry for my poor english. > > > Best regards. > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most > from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > > > |
From: Koichi S. <koi...@gm...> - 2013-10-07 08:44:47
|
I checked two files. Did you specify pgxc as a database owner? It seems that the role pgxc already exists when pg_restore tries to restore the role "pgxc". Maybe we need to control internal pg_dump to exclude such existing superusers from the restore list, and also need to fix the crash to move forward with the same situation. Are you using different operating system user and XC owner name? If then, could you try to use the same name for these? Regards; --- Koichi Suzuki 2013/10/7 Julian <jul...@gm...> > Hi, > > Here is the log file at the new coordinator and scheme file > > > > -- > Julian > 使用 Sparrow <http://www.sparrowmailapp.com/?sig> 發信 > > On 2013年10月7日Monday at 下午2:40, Koichi Suzuki wrote: > > I supporte the error was encountered in pg_resgtore and pgxc is the owner > of postgres-XC in your pgxc_ctl.conf file. The issue looks some (not > necessarily just one) bugs. Can I have log files at the new coordinator? > This may have some more information on the issue. > > Regards; > > --- > Koichi Suzuki > > > 2013/10/4 Julian <jul...@gm...> > > Dear Sir, > > My cluster has configured by pg_ctl now, but till filed. > > Error message > > -------------------------------------------------------------------------------- > PGXC add coordinator master coord4 node4 20004 20010 /opt/pgxc/nodes/coord > …... > Actual Command: ssh pgxc@node4 "( pg_ctl start -Z restoremode -D > /opt/pgxc/nodes/coord -o -i ) > /tmp/squeeze-10-200_STDOUT_2618_16 2>&1" < > /dev/null > /dev/null 2>&1 > Bring remote stdout: scp pgxc@node4:/tmp/squeeze-10-200_STDOUT_2618_16 > /tmp/STDOUT_2618_17 > /dev/null 2>&1 > SET > SET > psql:/tmp/GENERAL_2618_15:12: ERROR: role "pgxc" already exists > ALTER ROLE > REVOKE > REVOKE > GRANT > GRANT > CREATE NODE > CREATE NODE > CREATE NODE > CREATE NODE > CREATE NODE > CREATE NODE > You are now connected to database "postgres" as user "pgxc". > SET > SET > SET > SET > SET > COMMENT > CREATE EXTENSION > COMMENT > SET > SET > SET > psql:/tmp/GENERAL_2618_15:92: connection to server was lost > Actual Command: ssh pgxc@node4 "( pg_ctl stop -Z restoremode -D > /opt/pgxc/nodes/coord ) > /tmp/squeeze-10-200_STDOUT_2618_18 2>&1" < > /dev/null > /dev/null 2>&1 > Bring remote stdout: scp pgxc@node4:/tmp/squeeze-10-200_STDOUT_2618_18 > /tmp/STDOUT_2618_19 > /dev/null 2>&1 > Starting coordinator master coord4 > Done. > CREATE NODE > CREATE NODE > CREATE NODE > ALTER NODE > ---------------------------------------------------------------- > > Error log > -------------------------------------------------------------------- > ERROR: role "pgxc" already exists > STATEMENT: CREATE ROLE pgxc; > LOG: *server process (PID 3013) was terminated by signal 11: > Segmentation fault* > DETAIL: Failed process was running: CREATE TABLE user_info_hash ( > id integer NOT NULL, > firstname text, > lastname text, > info text > ) > DISTRIBUTE BY HASH (id) > TO NODE (datanode1,datanode2,datanode3); > 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 co > rrupted shared memory. > HINT: In a moment you should be able to reconnect to the database and > repeat your command. > --------------------------------------------------------------------------- > > Any comments are appreciated > > > Best Regards, > > -- > Julian > 使用 Sparrow <http://www.sparrowmailapp.com/?sig> 發信 > > On 2013年10月3日Thursday at 上午9:31, Koichi Suzuki wrote: > > You cannot add a coordinator in such a way. There're many issued to be > resolved internally. You can configure and operate whole cluster with > pgxc_ctl to get handy way to add coordinator/datanode. > > I understand you have your cluster configured without pgxc_ctl. In this > case, adding coordinator manually could be a bit complicated work. Sorry, > I've not uploaded the detailed step to do it. > > Whole steps will be found in add_coordinatorMaster() function defined in > coord_cmd.c of pgxc_ctl source code. It will be found at contrib/pgxc_ctl > in the release material. > > Please allow a bit of time to find my time to upload this information to > XC wiki. > > Or, you can backup whole database with pg_dumpall, then reconfigure new xc > cluster with additional coordinator, and then restore the backup. > > Regards; > > --- > Koichi Suzuki > > > 2013/10/3 Julian <jul...@gm...> > > Dear Sir, > > I have a cluster with 3 coordinators and 3 datanodes on 3 VM, today i > was try to added a new coordinator to the cluster, when i using command > "psql postgres -f coordinator.sql -p 5455" to restore the backup file to > the new coordinator. > > Then i got this message : > > psql:coordinator-dump.sql:105: connection to server was lost > > In the log file: > > ---------------------------------------------------------------------------------------------------------------------------------------------------------------- > 2013-10-02 23:00:09.811 CST,,,29061,,524c34de.7185,2,,2013-10-02 > 22:59:42 CST,,0,LOG,00000,"server process (PID 29094) was terminated by > signal 11: Segmentation fault","Failed process was r > unning: CREATE TABLE user_info_hash ( > id integer NOT NULL, > firstname text, > lastname text, > info text > ) > DISTRIBUTE BY HASH (id) > TO NODE (dn2,dn1,dn3);",,,,,,,,"" > 2013-10-02 23:00:09.811 CST,,,29061,,524c34de.7185,3,,2013-10-02 > 22:59:42 CST,,0,LOG,00000,"terminating any other active server > processes",,,,,,,,,"" > > ------------------------------------------------------------------------------------------------------------------------------------------------------------------ > refer to > http://postgres-xc.sourceforge.net/docs/1_1/add-node-coordinator.html > > Is there something i doing worng? > > > Thanks for your kindly reply. > > And sorry for my poor english. > > > Best regards. > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most > from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > > > > > |
From: Julian <jul...@gm...> - 2013-10-07 08:53:46
|
I did not specify pgxc as a database owner, but i create user pgxc to do these job. -- Julian 使用 Sparrow (http://www.sparrowmailapp.com/?sig) 發信 On 2013年10月7日Monday at 下午4:44, Koichi Suzuki wrote: > Did you specify pgxc as a database owner |
From: Koichi S. <koi...@gm...> - 2013-10-07 09:32:07
|
Okay. I'm wondering why internal pg_restore complains pgxc already exists. If you do not specify pgxc in pgxc_ctl and created it manually, newly-craeted node should not contain the role pgxc, though we have different massage. Could you let me know if you have any idea? Best; --- Koichi Suzuki 2013/10/7 Julian <jul...@gm...> > I did not specify pgxc as a database owner, but i create user pgxc to do > these job. > > -- > Julian > 使用 Sparrow <http://www.sparrowmailapp.com/?sig> 發信 > > On 2013年10月7日Monday at 下午4:44, Koichi Suzuki wrote: > > Did you specify pgxc as a database owner > > > |
From: Koichi S. <koi...@gm...> - 2013-10-07 10:04:57
|
I understood the situation. Could you let me know if pgxc is not the operating system user name you are using? If so, I will run the test with this situation and see what is going to happen. Maybe a bug (not Postgres-XC core, but pgxc_ctl). If pgxc is the operating system user you are using, then there could be another cause. Also, please let me know your setting of pgxcUser in pgxc_ctl.conf? Best; --- Koichi Suzuki 2013/10/7 Julian <jul...@gm...> > Sorry, i found i have already config pgxcOwner=pgxc in pxc_ctl.conf. > > And i forgot to mention there's something strange about to add new > coordinator, > i can’t add coord4 by "add coordinator master coord4 node4 20004 20010 > /opt/pgxc/nodes/coord” > > it will show me > ERROR: sorry found some inconflicts in coordinator master > configuration.PGXC$ > > unless i add coord4 to pgxc_ctl.conf and remove it at PGXC shell > PGXC$ remove coordinator master coord4 > ERROR: PGXC Node coord4: object not defined > ERROR: PGXC Node coord4: object not defined > ERROR: PGXC Node coord4: object not defined > > Is it normal ? > > attach file is my pgxc config > > Julian > 使用 Sparrow <http://www.sparrowmailapp.com/?sig> 發信 > > On 2013年10月7日Monday at 下午5:31, Koichi Suzuki wrote: > > Okay. I'm wondering why internal pg_restore complains pgxc already > exists. If you do not specify pgxc in pgxc_ctl and created it manually, > newly-craeted node should not contain the role pgxc, though we have > different massage. > > Could you let me know if you have any idea? > > Best; > > --- > Koichi Suzuki > > > 2013/10/7 Julian <jul...@gm...> > > I did not specify pgxc as a database owner, but i create user pgxc to do > these job. > > -- > Julian > 使用 Sparrow <http://www.sparrowmailapp.com/?sig> 發信 > > On 2013年10月7日Monday at 下午4:44, Koichi Suzuki wrote: > > Did you specify pgxc as a database owner > > > > > |
From: Koichi S. <koi...@gm...> - 2013-10-07 10:18:46
|
I found your configuration, in terms of owner and user, is the same as my demonstration scenario. Then what you should do is: 1. Log in to your operating system as pgxcUser, 2. Initialize Postgres-XC cluster with "init all" command of pgxc_ctl, Then the database user $pgxcOwner should have been created and you don't have to worry about it. When you add a coordinator, simply issue "add coordinator master" command. It should work. If you have any other issue, please let me know. My pgxc_ctl demonstration scenario will be found at https://sourceforge.net/apps/mediawiki/postgres-xc/index.php?title=PGOpen2013_Postgres_Open_2013 The configuration is with full slaves, which you can disable. The demo adds a datanode, not a coordinator. I believe there's no significant differences. Regards; --- Koichi Suzuki 2013/10/7 Koichi Suzuki <koi...@gm...> > I understood the situation. Could you let me know if pgxc is not the > operating system user name you are using? If so, I will run the test with > this situation and see what is going to happen. Maybe a bug (not > Postgres-XC core, but pgxc_ctl). If pgxc is the operating system user you > are using, then there could be another cause. Also, please let me know > your setting of pgxcUser in pgxc_ctl.conf? > > Best; > > --- > Koichi Suzuki > > > 2013/10/7 Julian <jul...@gm...> > >> Sorry, i found i have already config pgxcOwner=pgxc in pxc_ctl.conf. >> >> And i forgot to mention there's something strange about to add new >> coordinator, >> i can’t add coord4 by "add coordinator master coord4 node4 20004 20010 >> /opt/pgxc/nodes/coord” >> >> it will show me >> ERROR: sorry found some inconflicts in coordinator master >> configuration.PGXC$ >> >> unless i add coord4 to pgxc_ctl.conf and remove it at PGXC shell >> PGXC$ remove coordinator master coord4 >> ERROR: PGXC Node coord4: object not defined >> ERROR: PGXC Node coord4: object not defined >> ERROR: PGXC Node coord4: object not defined >> >> Is it normal ? >> >> attach file is my pgxc config >> >> Julian >> 使用 Sparrow <http://www.sparrowmailapp.com/?sig> 發信 >> >> On 2013年10月7日Monday at 下午5:31, Koichi Suzuki wrote: >> >> Okay. I'm wondering why internal pg_restore complains pgxc already >> exists. If you do not specify pgxc in pgxc_ctl and created it manually, >> newly-craeted node should not contain the role pgxc, though we have >> different massage. >> >> Could you let me know if you have any idea? >> >> Best; >> >> --- >> Koichi Suzuki >> >> >> 2013/10/7 Julian <jul...@gm...> >> >> I did not specify pgxc as a database owner, but i create user pgxc to do >> these job. >> >> -- >> Julian >> 使用 Sparrow <http://www.sparrowmailapp.com/?sig> 發信 >> >> On 2013年10月7日Monday at 下午4:44, Koichi Suzuki wrote: >> >> Did you specify pgxc as a database owner >> >> >> >> >> > |
From: Julian <jul...@gm...> - 2013-10-07 14:27:54
|
I can not just issue "add coordinator master",it alway asked me for more here is my step: # Deploy binaries PGXC$ depoly all #initialize everyting: one GTM Master, three GTM_Proxy, three coordinator, three datanode PGXC$ init all .... PGXC$ Createdb pgxc .... PGXC$ Psql pgxc=# select * from pgxc_node; node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id .... pgxc=# create table user_info_hash(id int primary key,firstname text,lastname text,info text) distribute by hash(id); NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "user_info_hash_pkey" for table "user_info_hash" CREATE TABLE ... PGXC$ deploy node4 PGXC$ add datanode master datanode4 *ERROR: please specify the host for the datanode masetr* PGXC$ add datanode master datanode4 node4 20008 /opt/pgxc/nodes/dn_master *ERROR: sorry found some inconflicts in datanode master configuration.* -------------------------------------------------------------- 2. and i found when the dump file contain table with CREATE TABLE user_info_hash ( id integer NOT NULL, firstname text, lastname text, info text ) DISTRIBUTE BY HASH (id) TO NODE (datanode1,datanode2,datanode3); is alway failed to add new coordinator but with this CREATE TABLE user_id ( id integer NOT NULL ) DISTRIBUTE BY HASH (id) TO NODE (dn2,dn1,dn3); it's sucessed to add the new coordinator to the cluster 於 7/10/2013 18:18, Koichi Suzuki 提到: > I found your configuration, in terms of owner and user, is the same as > my demonstration scenario. Then what you should do is: > > 1. Log in to your operating system as pgxcUser, > 2. Initialize Postgres-XC cluster with "init all" command of pgxc_ctl, > > Then the database user $pgxcOwner should have been created and you > don't have to worry about it. When you add a coordinator, simply issue > "add coordinator master" command. It should work. If you have any > other issue, please let me know. > > My pgxc_ctl demonstration scenario will be found at > https://sourceforge.net/apps/mediawiki/postgres-xc/index.php?title=PGOpen2013_Postgres_Open_2013 > > The configuration is with full slaves, which you can disable. The demo > adds a datanode, not a coordinator. I believe there's no significant > differences. > > Regards; > > --- > Koichi Suzuki > > > 2013/10/7 Koichi Suzuki <koi...@gm... > <mailto:koi...@gm...>> > > I understood the situation. Could you let me know if pgxc is not > the operating system user name you are using? If so, I will run > the test with this situation and see what is going to happen. > Maybe a bug (not Postgres-XC core, but pgxc_ctl). If pgxc is the > operating system user you are using, then there could be another > cause. Also, please let me know your setting of pgxcUser in > pgxc_ctl.conf? > > Best; > > --- > Koichi Suzuki > > > 2013/10/7 Julian <jul...@gm... <mailto:jul...@gm...>> > > Sorry, i found i have already config pgxcOwner=pgxc in > pxc_ctl.conf. > > And i forgot to mention there's something strange about to add > new coordinator, > i can’t add coord4 by "add coordinator master coord4 node4 > 20004 20010 /opt/pgxc/nodes/coord” > > it will show me > ERROR: sorry found some inconflicts in coordinator master > configuration.PGXC$ > > unless i add coord4 to pgxc_ctl.conf and remove it at PGXC shell > PGXC$ remove coordinator master coord4 > ERROR: PGXC Node coord4: object not defined > ERROR: PGXC Node coord4: object not defined > ERROR: PGXC Node coord4: object not defined > > Is it normal ? > > attach file is my pgxc config > > Julian > 使用 Sparrow <http://www.sparrowmailapp.com/?sig> 發信 > > On 2013年10月7日Monday at 下午5:31, Koichi Suzuki wrote: > >> Okay. I'm wondering why internal pg_restore complains pgxc >> already exists. If you do not specify pgxc in pgxc_ctl and >> created it manually, newly-craeted node should not contain >> the role pgxc, though we have different massage. >> >> Could you let me know if you have any idea? >> >> Best; >> >> --- >> Koichi Suzuki >> >> >> 2013/10/7 Julian <jul...@gm... <mailto:jul...@gm...>> >>> I did not specify pgxc as a database owner, but i create >>> user pgxc to do these job. >>> >>> -- >>> Julian >>> 使用 Sparrow <http://www.sparrowmailapp.com/?sig> 發信 >>> >>> On 2013年10月7日Monday at 下午4:44, Koichi Suzuki wrote: >>> >>>> Did you specify pgxc as a database owner >>> >> > > > |
From: 鈴木 幸市 <ko...@in...> - 2013-10-08 01:08:54
|
On 2013/10/07, at 23:27, Julian <jul...@gm...<mailto:jul...@gm...>> wrote: I can not just issue "add coordinator master",it alway asked me for more here is my step: # Deploy binaries PGXC$ depoly all #initialize everyting: one GTM Master, three GTM_Proxy, three coordinator, three datanode PGXC$ init all These commands are for the initial ones. I think you've already done that. ..... PGXC$ Createdb pgxc ..... PGXC$ Psql pgxc=# select * from pgxc_node; node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id ..... pgxc=# create table user_info_hash(id int primary key,firstname text,lastname text,info text) distribute by hash(id); NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "user_info_hash_pkey" for table "user_info_hash" CREATE TABLE .... PGXC$ deploy node4 PGXC$ add datanode master datanode4 ERROR: please specify the host for the datanode masetr PGXC$ add datanode master datanode4 node4 20008 /opt/pgxc/nodes/dn_master ERROR: sorry found some inconflicts in datanode master configuration. add command syntax will be found at http://postgres-xc.sourceforge.net/docs/1_1/pgxc-ctl.html. Please take a look at the section F.32.12. -------------------------------------------------------------- 2. and i found when the dump file contain table with CREATE TABLE user_info_hash ( id integer NOT NULL, firstname text, lastname text, info text ) DISTRIBUTE BY HASH (id) TO NODE (datanode1,datanode2,datanode3); is alway failed to add new coordinator but with this CREATE TABLE user_id ( id integer NOT NULL ) DISTRIBUTE BY HASH (id) TO NODE (dn2,dn1,dn3); it's sucessed to add the new coordinator to the cluster No. To add a coordinator, you should have correct resource in "add" command. The error message above indicates there are some conflict in the resource you specified with another node. You must specify unique port number and work directory within the server. To add a coordinator, you should issue the following command: PGXC$ add coordinator master name host port pooler dir When you issue this command and it is successful, your pgxc_ctl.conf will have additional line with this additional node. Please take a look at it. If it fails and you'd like to restore to the previous configuration, you can edit pgxc_ctl.conf by yourself. In this point, pgxc_ctl is still "primitive". Regards; --- Koichi Suzuki 於 7/10/2013 18:18, Koichi Suzuki 提到: I found your configuration, in terms of owner and user, is the same as my demonstration scenario. Then what you should do is: 1. Log in to your operating system as pgxcUser, 2. Initialize Postgres-XC cluster with "init all" command of pgxc_ctl, Then the database user $pgxcOwner should have been created and you don't have to worry about it. When you add a coordinator, simply issue "add coordinator master" command. It should work. If you have any other issue, please let me know. My pgxc_ctl demonstration scenario will be found at https://sourceforge.net/apps/mediawiki/postgres-xc/index.php?title=PGOpen2013_Postgres_Open_2013 The configuration is with full slaves, which you can disable. The demo adds a datanode, not a coordinator. I believe there's no significant differences. Regards; --- Koichi Suzuki 2013/10/7 Koichi Suzuki <koi...@gm...<mailto:koi...@gm...>> I understood the situation. Could you let me know if pgxc is not the operating system user name you are using? If so, I will run the test with this situation and see what is going to happen. Maybe a bug (not Postgres-XC core, but pgxc_ctl). If pgxc is the operating system user you are using, then there could be another cause. Also, please let me know your setting of pgxcUser in pgxc_ctl.conf? Best; --- Koichi Suzuki 2013/10/7 Julian <jul...@gm...<mailto:jul...@gm...>> Sorry, i found i have already config pgxcOwner=pgxc in pxc_ctl.conf. And i forgot to mention there's something strange about to add new coordinator, i can’t add coord4 by "add coordinator master coord4 node4 20004 20010 /opt/pgxc/nodes/coord” it will show me ERROR: sorry found some inconflicts in coordinator master configuration.PGXC$ unless i add coord4 to pgxc_ctl.conf and remove it at PGXC shell PGXC$ remove coordinator master coord4 ERROR: PGXC Node coord4: object not defined ERROR: PGXC Node coord4: object not defined ERROR: PGXC Node coord4: object not defined Is it normal ? attach file is my pgxc config Julian 使用 Sparrow<http://www.sparrowmailapp.com/?sig> 發信 On 2013年10月7日Monday at 下午5:31, Koichi Suzuki wrote: Okay. I'm wondering why internal pg_restore complains pgxc already exists.. If you do not specify pgxc in pgxc_ctl and created it manually, newly-craeted node should not contain the role pgxc, though we have different massage. Could you let me know if you have any idea? Best; --- Koichi Suzuki 2013/10/7 Julian <jul...@gm...<mailto:jul...@gm...>> I did not specify pgxc as a database owner, but i create user pgxc to do these job. -- Julian 使用 Sparrow<http://www.sparrowmailapp.com/?sig> 發信 On 2013年10月7日Monday at 下午4:44, Koichi Suzuki wrote: Did you specify pgxc as a database owner ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk_______________________________________________ Postgres-xc-general mailing list Pos...@li... https://lists.sourceforge.net/lists/listinfo/postgres-xc-general |