From: Pavan D. <pav...@gm...> - 2014-07-24 12:08:54
|
I noticed that we can't specify port number for datanode slave nodes that are different from the master nodes. Is it that way for a good reason? I'm asking before if I need to test this feature on a single node, I would like to run master and slave on the same machine. But since they use the same port number, its not possible to do that. Should we consider supporting different ports for datanode (and coordinator slaves) just like we do for GTM slave? Thanks, Pavan -- Pavan Deolasee http://www.linkedin.com/in/pavandeolasee |
From: 鈴木 幸市 <ko...@in...> - 2014-07-25 01:38:19
|
Background is to make configuration as simple as possible and to make promotion simpler. XC primitive nodes support different port for master and slave, as in vanilla PG. When promoting slave with the same port number, VIP will help to connect to the node without change in the target port/host. VIP cannot do this if port number is different. I understand this helps only for coordinator. I think it’s also better to make coordinator/datanode configuration as same as possible. Regards; --- Koichi Suzuki 2014/07/24 21:08、Pavan Deolasee <pav...@gm...<mailto:pav...@gm...>> のメール: I noticed that we can't specify port number for datanode slave nodes that are different from the master nodes. Is it that way for a good reason? I'm asking before if I need to test this feature on a single node, I would like to run master and slave on the same machine. But since they use the same port number, its not possible to do that. Should we consider supporting different ports for datanode (and coordinator slaves) just like we do for GTM slave? Thanks, Pavan -- Pavan Deolasee http://www.linkedin.com/in/pavandeolasee ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds_______________________________________________ Postgres-xc-developers mailing list Pos...@li... https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers |
From: Mason S. <ms...@tr...> - 2014-07-25 13:36:45
|
On Thu, Jul 24, 2014 at 9:38 PM, 鈴木 幸市 <ko...@in...> wrote: > Background is to make configuration as simple as possible and to make > promotion simpler. XC primitive nodes support different port for master > and slave, as in vanilla PG. > > When promoting slave with the same port number, VIP will help to connect > to the node without change in the target port/host. VIP cannot do this if > port number is different. I understand this helps only for coordinator. > I think it’s also better to make coordinator/datanode configuration as same > as possible. > I had assumed this to be the reason. It makes sense to do as the default. I think it would be a nice option to be able to configure differently for development and debugging. I added this to Postgres-XL as a ticket with a low priority, since I would like to see it at least get in there eventually, to optionally override. https://sourceforge.net/p/postgres-xl/tickets/25/ > > Regards; > --- > Koichi Suzuki > > 2014/07/24 21:08、Pavan Deolasee <pav...@gm...> のメール: > > I noticed that we can't specify port number for datanode slave nodes > that are different from the master nodes. Is it that way for a good reason? > I'm asking before if I need to test this feature on a single node, I would > like to run master and slave on the same machine. But since they use the > same port number, its not possible to do that. Should we consider > supporting different ports for datanode (and coordinator slaves) just like > we do for GTM slave? > > Thanks, > Pavan > > -- > Pavan Deolasee > http://www.linkedin.com/in/pavandeolasee > > ------------------------------------------------------------------------------ > Want fast and easy access to all the code in your enterprise? Index and > search up to 200,000 lines of code with a free copy of Black Duck > Code Sight - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds_______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > > > > > ------------------------------------------------------------------------------ > Want fast and easy access to all the code in your enterprise? Index and > search up to 200,000 lines of code with a free copy of Black Duck > Code Sight - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > > -- Mason Sharp TransLattice - http://www.translattice.com Distributed and Clustered Database Solutions |