postgres-xc-general

[Postgres-xc-general] How to stop promoted GTM slave after failover and bring back orginal

[Juned K. <jkh...@gm...>]

Hi All,

I have been configured pgxc with four servers.

> PGXC monitor all
> Running: gtm master
> Running: gtm slave
> Running: gtm proxy gtm_pxy1
> Running: gtm proxy gtm_pxy2
> Running: coordinator master coord1
> Running: coordinator master coord2
> Running: datanode master datanode1
> Running: datanode master datanode2
>

I have configured slave for GTM, when i killed master GTM and promoted
slave as master
that's also worked fine.

But i want to know what is exact procedure to bring original master to back
using *pgxc_ctl*

Even i tried with that manul process but still i am not able to bring it
back. i think i messed up
because now gtm proxies are fails to start

PGXC monitor all
> Running: gtm master
> Running: gtm proxy gtm_pxy1
> Running: gtm proxy gtm_pxy2
> Not running: coordinator master coord1
> Not running: coordinator master coord2
> Running: datanode master datanode1
> Running: datanode master datanode2
>

And still i don't see GTM slave running
Can anyone please suggest me how to do this using pgxc_ctl?


-- 
Thanks,
Juned Khan
iNextrix Technologies Pvt Ltd.
www.inextrix.com

Re: [Postgres-xc-general] How to stop promoted GTM slave after failover and bring back orginal

[Koichi S. <koi...@gm...>]

When you fail-over GTM, you should reconnect gym-proxies to the new
gtm.   This could have been done automatically but now you need to do
this annually using reconnect command of pgxc_ctl.   When you find gym
proxy is down, you can just restart it.

Regards;
---
Koichi Suzuki


2014-03-07 13:55 GMT+00:00 Juned Khan <jkh...@gm...>:
> Hi All,
>
> I have been configured pgxc with four servers.
>>
>> PGXC monitor all
>> Running: gtm master
>> Running: gtm slave
>> Running: gtm proxy gtm_pxy1
>> Running: gtm proxy gtm_pxy2
>> Running: coordinator master coord1
>> Running: coordinator master coord2
>> Running: datanode master datanode1
>> Running: datanode master datanode2
>
>
> I have configured slave for GTM, when i killed master GTM and promoted slave
> as master
> that's also worked fine.
>
> But i want to know what is exact procedure to bring original master to back
> using pgxc_ctl
>
> Even i tried with that manul process but still i am not able to bring it
> back. i think i messed up
> because now gtm proxies are fails to start
>
>> PGXC monitor all
>> Running: gtm master
>> Running: gtm proxy gtm_pxy1
>> Running: gtm proxy gtm_pxy2
>> Not running: coordinator master coord1
>> Not running: coordinator master coord2
>> Running: datanode master datanode1
>> Running: datanode master datanode2
>
>
> And still i don't see GTM slave running
> Can anyone please suggest me how to do this using pgxc_ctl?
>
>
> --
> Thanks,
> Juned Khan
> iNextrix Technologies Pvt Ltd.
> www.inextrix.com
>
> ------------------------------------------------------------------------------
> Subversion Kills Productivity. Get off Subversion & Make the Move to
> Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works.
> Faster operations. Version large binaries.  Built-in WAN optimization and
> the
> freedom to use Git, Perforce or both. Make the move to Perforce.
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>

Re: [Postgres-xc-general] How to stop promoted GTM slave after failover and bring back orginal

[Juned K. <jkh...@gm...>]

Hi Koichi,

Yeah failover GTM and reconnection to GTM proxies to new GTM just works fine
but how to reconnect to master GTM when it comes up ?


On Sat, Mar 8, 2014 at 8:24 PM, Koichi Suzuki <koi...@gm...> wrote:

> When you fail-over GTM, you should reconnect gym-proxies to the new
> gtm.   This could have been done automatically but now you need to do
> this annually using reconnect command of pgxc_ctl.   When you find gym
> proxy is down, you can just restart it.
>
> Regards;
> ---
> Koichi Suzuki
>
>
> 2014-03-07 13:55 GMT+00:00 Juned Khan <jkh...@gm...>:
> > Hi All,
> >
> > I have been configured pgxc with four servers.
> >>
> >> PGXC monitor all
> >> Running: gtm master
> >> Running: gtm slave
> >> Running: gtm proxy gtm_pxy1
> >> Running: gtm proxy gtm_pxy2
> >> Running: coordinator master coord1
> >> Running: coordinator master coord2
> >> Running: datanode master datanode1
> >> Running: datanode master datanode2
> >
> >
> > I have configured slave for GTM, when i killed master GTM and promoted
> slave
> > as master
> > that's also worked fine.
> >
> > But i want to know what is exact procedure to bring original master to
> back
> > using pgxc_ctl
> >
> > Even i tried with that manul process but still i am not able to bring it
> > back. i think i messed up
> > because now gtm proxies are fails to start
> >
> >> PGXC monitor all
> >> Running: gtm master
> >> Running: gtm proxy gtm_pxy1
> >> Running: gtm proxy gtm_pxy2
> >> Not running: coordinator master coord1
> >> Not running: coordinator master coord2
> >> Running: datanode master datanode1
> >> Running: datanode master datanode2
> >
> >
> > And still i don't see GTM slave running
> > Can anyone please suggest me how to do this using pgxc_ctl?
> >
> >
> > --
> > Thanks,
> > Juned Khan
> > iNextrix Technologies Pvt Ltd.
> > www.inextrix.com
> >
> >
> ------------------------------------------------------------------------------
> > Subversion Kills Productivity. Get off Subversion & Make the Move to
> > Perforce.
> > With Perforce, you get hassle-free workflows. Merge that actually works.
> > Faster operations. Version large binaries.  Built-in WAN optimization and
> > the
> > freedom to use Git, Perforce or both. Make the move to Perforce.
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> > _______________________________________________
> > Postgres-xc-general mailing list
> > Pos...@li...
> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
> >
>



-- 
Thanks,
Juned Khan
iNextrix Technologies Pvt Ltd.
www.inextrix.com

Re: [Postgres-xc-general] How to stop promoted GTM slave after failover and bring back orginal

[Koichi S. <koi...@gm...>]

You should connect restored GTM to the current master GTM as a slave,
then fail it over and reconnect GTM proxy to the new one.
Failed-over GTM has current cluster transaction status and the new
master has to restore its status from the current master GTM.

Regards;
---
Koichi Suzuki


2014-03-09 4:34 GMT+00:00 Juned Khan <jkh...@gm...>:
> Hi Koichi,
>
> Yeah failover GTM and reconnection to GTM proxies to new GTM just works fine
> but how to reconnect to master GTM when it comes up ?
>
>
> On Sat, Mar 8, 2014 at 8:24 PM, Koichi Suzuki <koi...@gm...> wrote:
>>
>> When you fail-over GTM, you should reconnect gym-proxies to the new
>> gtm.   This could have been done automatically but now you need to do
>> this annually using reconnect command of pgxc_ctl.   When you find gym
>> proxy is down, you can just restart it.
>>
>> Regards;
>> ---
>> Koichi Suzuki
>>
>>
>> 2014-03-07 13:55 GMT+00:00 Juned Khan <jkh...@gm...>:
>> > Hi All,
>> >
>> > I have been configured pgxc with four servers.
>> >>
>> >> PGXC monitor all
>> >> Running: gtm master
>> >> Running: gtm slave
>> >> Running: gtm proxy gtm_pxy1
>> >> Running: gtm proxy gtm_pxy2
>> >> Running: coordinator master coord1
>> >> Running: coordinator master coord2
>> >> Running: datanode master datanode1
>> >> Running: datanode master datanode2
>> >
>> >
>> > I have configured slave for GTM, when i killed master GTM and promoted
>> > slave
>> > as master
>> > that's also worked fine.
>> >
>> > But i want to know what is exact procedure to bring original master to
>> > back
>> > using pgxc_ctl
>> >
>> > Even i tried with that manul process but still i am not able to bring it
>> > back. i think i messed up
>> > because now gtm proxies are fails to start
>> >
>> >> PGXC monitor all
>> >> Running: gtm master
>> >> Running: gtm proxy gtm_pxy1
>> >> Running: gtm proxy gtm_pxy2
>> >> Not running: coordinator master coord1
>> >> Not running: coordinator master coord2
>> >> Running: datanode master datanode1
>> >> Running: datanode master datanode2
>> >
>> >
>> > And still i don't see GTM slave running
>> > Can anyone please suggest me how to do this using pgxc_ctl?
>> >
>> >
>> > --
>> > Thanks,
>> > Juned Khan
>> > iNextrix Technologies Pvt Ltd.
>> > www.inextrix.com
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Subversion Kills Productivity. Get off Subversion & Make the Move to
>> > Perforce.
>> > With Perforce, you get hassle-free workflows. Merge that actually works.
>> > Faster operations. Version large binaries.  Built-in WAN optimization
>> > and
>> > the
>> > freedom to use Git, Perforce or both. Make the move to Perforce.
>> >
>> > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>> > _______________________________________________
>> > Postgres-xc-general mailing list
>> > Pos...@li...
>> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>> >
>
>
>
>
> --
> Thanks,
> Juned Khan
> iNextrix Technologies Pvt Ltd.
> www.inextrix.com

Re: [Postgres-xc-general] How to stop promoted GTM slave after failover and bring back orginal

[Juned K. <jkh...@gm...>]

Hi Koichi,

what command i should use to connect restored GTM to the current master GTM
as a slave ?

it would be great if you provide me the link for all pgxc_ctl commands, so
i can refer it myself.

Regards
Juned Khan


On Sun, Mar 9, 2014 at 2:48 PM, Koichi Suzuki <koi...@gm...> wrote:

> You should connect restored GTM to the current master GTM as a slave,
> then fail it over and reconnect GTM proxy to the new one.
> Failed-over GTM has current cluster transaction status and the new
> master has to restore its status from the current master GTM.
>
> Regards;
> ---
> Koichi Suzuki
>
>
> 2014-03-09 4:34 GMT+00:00 Juned Khan <jkh...@gm...>:
> > Hi Koichi,
> >
> > Yeah failover GTM and reconnection to GTM proxies to new GTM just works
> fine
> > but how to reconnect to master GTM when it comes up ?
> >
> >
> > On Sat, Mar 8, 2014 at 8:24 PM, Koichi Suzuki <koi...@gm...>
> wrote:
> >>
> >> When you fail-over GTM, you should reconnect gym-proxies to the new
> >> gtm.   This could have been done automatically but now you need to do
> >> this annually using reconnect command of pgxc_ctl.   When you find gym
> >> proxy is down, you can just restart it.
> >>
> >> Regards;
> >> ---
> >> Koichi Suzuki
> >>
> >>
> >> 2014-03-07 13:55 GMT+00:00 Juned Khan <jkh...@gm...>:
> >> > Hi All,
> >> >
> >> > I have been configured pgxc with four servers.
> >> >>
> >> >> PGXC monitor all
> >> >> Running: gtm master
> >> >> Running: gtm slave
> >> >> Running: gtm proxy gtm_pxy1
> >> >> Running: gtm proxy gtm_pxy2
> >> >> Running: coordinator master coord1
> >> >> Running: coordinator master coord2
> >> >> Running: datanode master datanode1
> >> >> Running: datanode master datanode2
> >> >
> >> >
> >> > I have configured slave for GTM, when i killed master GTM and promoted
> >> > slave
> >> > as master
> >> > that's also worked fine.
> >> >
> >> > But i want to know what is exact procedure to bring original master to
> >> > back
> >> > using pgxc_ctl
> >> >
> >> > Even i tried with that manul process but still i am not able to bring
> it
> >> > back. i think i messed up
> >> > because now gtm proxies are fails to start
> >> >
> >> >> PGXC monitor all
> >> >> Running: gtm master
> >> >> Running: gtm proxy gtm_pxy1
> >> >> Running: gtm proxy gtm_pxy2
> >> >> Not running: coordinator master coord1
> >> >> Not running: coordinator master coord2
> >> >> Running: datanode master datanode1
> >> >> Running: datanode master datanode2
> >> >
> >> >
> >> > And still i don't see GTM slave running
> >> > Can anyone please suggest me how to do this using pgxc_ctl?
> >> >
> >> >
> >> > --
> >> > Thanks,
> >> > Juned Khan
> >> > iNextrix Technologies Pvt Ltd.
> >> > www.inextrix.com
> >> >
> >> >
> >> >
> ------------------------------------------------------------------------------
> >> > Subversion Kills Productivity. Get off Subversion & Make the Move to
> >> > Perforce.
> >> > With Perforce, you get hassle-free workflows. Merge that actually
> works.
> >> > Faster operations. Version large binaries.  Built-in WAN optimization
> >> > and
> >> > the
> >> > freedom to use Git, Perforce or both. Make the move to Perforce.
> >> >
> >> >
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> >> > _______________________________________________
> >> > Postgres-xc-general mailing list
> >> > Pos...@li...
> >> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
> >> >
> >
> >
> >
> >
> > --
> > Thanks,
> > Juned Khan
> > iNextrix Technologies Pvt Ltd.
> > www.inextrix.com
>



-- 
Thanks,
Juned Khan
iNextrix Technologies Pvt Ltd.
www.inextrix.com

Re: [Postgres-xc-general] How to stop promoted GTM slave after failover and bring back orginal

[Koichi S. <koi...@gm...>]

Please take a look at http://postgres-xc.sourceforge.net/docs/1_1/pgxc-ctl.html

Also, when you add restored GTM, you should initialize it as a slave,
then fail it over.

Regards;
---
Koichi Suzuki


2014-03-09 9:55 GMT+00:00 Juned Khan <jkh...@gm...>:
> Hi Koichi,
>
> what command i should use to connect restored GTM to the current master GTM
> as a slave ?
>
> it would be great if you provide me the link for all pgxc_ctl commands, so i
> can refer it myself.
>
> Regards
> Juned Khan
>
>
> On Sun, Mar 9, 2014 at 2:48 PM, Koichi Suzuki <koi...@gm...> wrote:
>>
>> You should connect restored GTM to the current master GTM as a slave,
>> then fail it over and reconnect GTM proxy to the new one.
>> Failed-over GTM has current cluster transaction status and the new
>> master has to restore its status from the current master GTM.
>>
>> Regards;
>> ---
>> Koichi Suzuki
>>
>>
>> 2014-03-09 4:34 GMT+00:00 Juned Khan <jkh...@gm...>:
>> > Hi Koichi,
>> >
>> > Yeah failover GTM and reconnection to GTM proxies to new GTM just works
>> > fine
>> > but how to reconnect to master GTM when it comes up ?
>> >
>> >
>> > On Sat, Mar 8, 2014 at 8:24 PM, Koichi Suzuki <koi...@gm...>
>> > wrote:
>> >>
>> >> When you fail-over GTM, you should reconnect gym-proxies to the new
>> >> gtm.   This could have been done automatically but now you need to do
>> >> this annually using reconnect command of pgxc_ctl.   When you find gym
>> >> proxy is down, you can just restart it.
>> >>
>> >> Regards;
>> >> ---
>> >> Koichi Suzuki
>> >>
>> >>
>> >> 2014-03-07 13:55 GMT+00:00 Juned Khan <jkh...@gm...>:
>> >> > Hi All,
>> >> >
>> >> > I have been configured pgxc with four servers.
>> >> >>
>> >> >> PGXC monitor all
>> >> >> Running: gtm master
>> >> >> Running: gtm slave
>> >> >> Running: gtm proxy gtm_pxy1
>> >> >> Running: gtm proxy gtm_pxy2
>> >> >> Running: coordinator master coord1
>> >> >> Running: coordinator master coord2
>> >> >> Running: datanode master datanode1
>> >> >> Running: datanode master datanode2
>> >> >
>> >> >
>> >> > I have configured slave for GTM, when i killed master GTM and
>> >> > promoted
>> >> > slave
>> >> > as master
>> >> > that's also worked fine.
>> >> >
>> >> > But i want to know what is exact procedure to bring original master
>> >> > to
>> >> > back
>> >> > using pgxc_ctl
>> >> >
>> >> > Even i tried with that manul process but still i am not able to bring
>> >> > it
>> >> > back. i think i messed up
>> >> > because now gtm proxies are fails to start
>> >> >
>> >> >> PGXC monitor all
>> >> >> Running: gtm master
>> >> >> Running: gtm proxy gtm_pxy1
>> >> >> Running: gtm proxy gtm_pxy2
>> >> >> Not running: coordinator master coord1
>> >> >> Not running: coordinator master coord2
>> >> >> Running: datanode master datanode1
>> >> >> Running: datanode master datanode2
>> >> >
>> >> >
>> >> > And still i don't see GTM slave running
>> >> > Can anyone please suggest me how to do this using pgxc_ctl?
>> >> >
>> >> >
>> >> > --
>> >> > Thanks,
>> >> > Juned Khan
>> >> > iNextrix Technologies Pvt Ltd.
>> >> > www.inextrix.com
>> >> >
>> >> >
>> >> >
>> >> > ------------------------------------------------------------------------------
>> >> > Subversion Kills Productivity. Get off Subversion & Make the Move to
>> >> > Perforce.
>> >> > With Perforce, you get hassle-free workflows. Merge that actually
>> >> > works.
>> >> > Faster operations. Version large binaries.  Built-in WAN optimization
>> >> > and
>> >> > the
>> >> > freedom to use Git, Perforce or both. Make the move to Perforce.
>> >> >
>> >> >
>> >> > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>> >> > _______________________________________________
>> >> > Postgres-xc-general mailing list
>> >> > Pos...@li...
>> >> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>> >> >
>> >
>> >
>> >
>> >
>> > --
>> > Thanks,
>> > Juned Khan
>> > iNextrix Technologies Pvt Ltd.
>> > www.inextrix.com
>
>
>
>
> --
> Thanks,
> Juned Khan
> iNextrix Technologies Pvt Ltd.
> www.inextrix.com