Menu
▾
▴
postgres-xc-developers
|
From: Koichi S. <koi...@gm...> - 2012-07-23 03:18:09
|
Hi, I had a chance to meet people from Linux-HA Japan an discussed how to provide Pacemaker RA (resource agent) for coordinator/datanode. I found present PostgreSQL RA (for 9.1) uses the following queries to the hot standby node. 1. select pg_is_in_recovery(); works fine. 2. select application_name,upper(state),upper(sync_state) from pg_stat_replication; This does not work. pg_stat_replication has zero row. 3. select pg_last_xlog_replay_location(),pg_last_xlog_receive_location(); works fine. 4. select now(); works fine. Because this is datanode slave, we don't have GTM connection or snapshot. This might be a cause of the problem 2, or we might have blocked to update pg_stat_replication system catalog. Any suggestions? ---------- Koichi Suzuki |
|
From: Michael P. <mic...@gm...> - 2012-07-23 03:53:57
|
> 2. select application_name,upper(state),upper(sync_state) from > pg_stat_replication; > > This does not work. pg_stat_replication has zero row. > Because this is datanode slave, we don't have GTM connection or > snapshot. This might be a cause of the problem 2, or we might have > blocked to update pg_stat_replication system catalog. > pg_stat_replication has by definition one row per wal sender process: http://www.postgresql.org/docs/9.1/static/monitoring-stats.html#MONITORING-STATS-VIEWS-TABLE AFAIK, slave has no wal sender processes running, so it is normal to see nothing on the slave side, all the data is on the master side. The data is only available on master, Am I missing smth? You might be able to see rows in pg_stat_replication on a slave if you use cascading replication however, but this feature is only available in 9.2. Also, in the case of XC, you can use EXECUTE DIRECT to get the information of pg_stat_replication from remote nodes, Coordinators and Datanodes included. -- Michael Paquier http://michael.otacoo.com |
|
From: Koichi S. <ko...@in...> - 2012-07-23 04:05:37
|
Thanks. I found the latter works for the master. --- Koichi On Mon, 23 Jul 2012 12:53:50 +0900 Michael Paquier <mic...@gm...> wrote: > > 2. select application_name,upper(state),upper(sync_state) from > > pg_stat_replication; > > > > This does not work. pg_stat_replication has zero row. > > > Because this is datanode slave, we don't have GTM connection or > > snapshot. This might be a cause of the problem 2, or we might have > > blocked to update pg_stat_replication system catalog. > > > pg_stat_replication has by definition one row per wal sender process: > http://www.postgresql.org/docs/9.1/static/monitoring-stats.html#MONITORING-STATS-VIEWS-TABLE > AFAIK, slave has no wal sender processes running, so it is normal to see > nothing on the slave side, all the data is on the master side. The data is > only available on master, Am I missing smth? > You might be able to see rows in pg_stat_replication on a slave if you use > cascading replication however, but this feature is only available in 9.2. > Also, in the case of XC, you can use EXECUTE DIRECT to get the information > of pg_stat_replication from remote nodes, Coordinators and Datanodes > included. > -- > Michael Paquier > http://michael.otacoo.com |
|
From: Nikhil S. <ni...@st...> - 2012-07-24 14:16:02
|
Hi, So what's the latest status of these HA activities for PGXC? Like the coordinator/datanode agents being discussed here, do we have agents for GTM for example? Also is this happening in some open source group where we can participate and see the latest and greatest source changes? Regards, Nikhils On Mon, Jul 23, 2012 at 12:06 AM, Koichi Suzuki <ko...@in...> wrote: > Thanks. I found the latter works for the master. > --- > Koichi > > On Mon, 23 Jul 2012 12:53:50 +0900 > Michael Paquier <mic...@gm...> wrote: > >> > 2. select application_name,upper(state),upper(sync_state) from >> > pg_stat_replication; >> > >> > This does not work. pg_stat_replication has zero row. >> > >> Because this is datanode slave, we don't have GTM connection or >> > snapshot. This might be a cause of the problem 2, or we might have >> > blocked to update pg_stat_replication system catalog. >> > >> pg_stat_replication has by definition one row per wal sender process: >> http://www.postgresql.org/docs/9.1/static/monitoring-stats.html#MONITORING-STATS-VIEWS-TABLE >> AFAIK, slave has no wal sender processes running, so it is normal to see >> nothing on the slave side, all the data is on the master side. The data is >> only available on master, Am I missing smth? >> You might be able to see rows in pg_stat_replication on a slave if you use >> cascading replication however, but this feature is only available in 9.2. >> Also, in the case of XC, you can use EXECUTE DIRECT to get the information >> of pg_stat_replication from remote nodes, Coordinators and Datanodes >> included. >> -- >> Michael Paquier >> http://michael.otacoo.com > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers -- StormDB - http://www.stormdb.com The Database Cloud |
|
From: Koichi S. <koi...@gm...> - 2012-07-27 00:20:10
|
I've heard another group is working together with Linux HA Japan to provide XC RA's. Sakata-san, could you provide related info if available? Regards; ---------- Koichi Suzuki 2012/7/24 Nikhil Sontakke <ni...@st...>: > Hi, > > So what's the latest status of these HA activities for PGXC? > > Like the coordinator/datanode agents being discussed here, do we have > agents for GTM for example? Also is this happening in some open source > group where we can participate and see the latest and greatest source > changes? > > Regards, > Nikhils > > On Mon, Jul 23, 2012 at 12:06 AM, Koichi Suzuki > <ko...@in...> wrote: >> Thanks. I found the latter works for the master. >> --- >> Koichi >> >> On Mon, 23 Jul 2012 12:53:50 +0900 >> Michael Paquier <mic...@gm...> wrote: >> >>> > 2. select application_name,upper(state),upper(sync_state) from >>> > pg_stat_replication; >>> > >>> > This does not work. pg_stat_replication has zero row. >>> > >>> Because this is datanode slave, we don't have GTM connection or >>> > snapshot. This might be a cause of the problem 2, or we might have >>> > blocked to update pg_stat_replication system catalog. >>> > >>> pg_stat_replication has by definition one row per wal sender process: >>> http://www.postgresql.org/docs/9.1/static/monitoring-stats.html#MONITORING-STATS-VIEWS-TABLE >>> AFAIK, slave has no wal sender processes running, so it is normal to see >>> nothing on the slave side, all the data is on the master side. The data is >>> only available on master, Am I missing smth? >>> You might be able to see rows in pg_stat_replication on a slave if you use >>> cascading replication however, but this feature is only available in 9.2. >>> Also, in the case of XC, you can use EXECUTE DIRECT to get the information >>> of pg_stat_replication from remote nodes, Coordinators and Datanodes >>> included. >>> -- >>> Michael Paquier >>> http://michael.otacoo.com >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Postgres-xc-developers mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > > > > -- > StormDB - http://www.stormdb.com > The Database Cloud > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers |
|
From: 坂田 哲夫 <sak...@la...> - 2012-08-10 09:32:49
|
Dear folks, I'm involved in HA facility implementation for Postgres-XC. This work began lecenty by a separate team from Postgres-XC core, say, XC HA team. We're planning to release this facility as an open source software by the end of this calendar year. The Postgres-XC HA facility will be developed in two phases: Phase1: Furnish fundamental functionality to give 1) redundancy to XC core component based on streaming replication which makes transactional data in datanode durable, and 2) backup GTM with GTM stand-by to handle GTM failure. Basic feature of 1) will be taken from PostgreSQL work and 2) will be taken from Postgres-XC core feature respectively. Phase2: Integrate Postgres-XC and Linux-HA. When one of the Postgres-XC components fails, it will be failed over automatically to continue Postgres-XC operation. For this purpose, XC HA team is developing RAs (Resource Agents). RA for coordinator and datanode will be implemented first, and then for GTM. XC HA team will be involved in them too. So far, XC HA team has not released any of the code, documentation or other materials. Please understand that (mainly because of administrative reasons) we're not planning to open XC HA team activities to public except for requirements to Postgres-XC core, which might have some influence to Postgres-XC design, performance and operations etc. The XC HA team is planning to make its activities open to public when the first Postgres-XC HA facility is released. Best Regards; --- Tetsuo Sakata (2012/07/27 9:20), Koichi Suzuki wrote: > I've heard another group is working together with Linux HA Japan to > provide XC RA's. > > Sakata-san, could you provide related info if available? > > Regards; > ---------- > Koichi Suzuki > > > 2012/7/24 Nikhil Sontakke <ni...@st...>: >> Hi, >> >> So what's the latest status of these HA activities for PGXC? >> >> Like the coordinator/datanode agents being discussed here, do we have >> agents for GTM for example? Also is this happening in some open source >> group where we can participate and see the latest and greatest source >> changes? >> >> Regards, >> Nikhils -- sakata.tetsuo _at_ lab.ntt.co.jp SAKATA, Tetsuo. Shinagawa Tokyo JAPAN. |
|
From: Aris S. <ari...@gm...> - 2012-08-10 10:37:15
|
> Please understand that (mainly because of administrative reasons) What kind of administrative reasons, did you mean here? If public unable to join the development process, then this HA/RA will be easily to be commercial product after it begin stable by community testing. Eg: Bizgres, C-Store. They end to be "dead" opensource projects. I think we should develop our own HA, which every one can participate into. Thus, we can have an "HA" of development process. On 8/10/12, 坂田 哲夫 <sak...@la...> wrote: > Dear folks, > > I'm involved in HA facility implementation for Postgres-XC. This work > began lecenty by a separate team from Postgres-XC core, say, XC HA team. > We're planning to release this facility as an open source software by > the end of this calendar year. > > The Postgres-XC HA facility will be developed in two phases: > > Phase1: Furnish fundamental functionality to give 1) redundancy to XC > core component based on streaming replication which makes transactional > data in datanode durable, and 2) backup GTM with GTM stand-by to handle > GTM failure. Basic feature of 1) will be taken from PostgreSQL work > and 2) will be taken from Postgres-XC core feature respectively. > > Phase2: Integrate Postgres-XC and Linux-HA. When one of the > Postgres-XC components fails, it will be failed over automatically to > continue Postgres-XC operation. For this purpose, XC HA team is > developing RAs (Resource Agents). RA for coordinator and datanode > will be implemented first, and then for GTM. XC HA team will be > involved in them too. > > So far, XC HA team has not released any of the code, documentation or > other materials. Please understand that (mainly because of > administrative reasons) we're not planning to open XC HA team activities > to public except for requirements to Postgres-XC core, which might have > some influence to Postgres-XC design, performance and operations etc. > > The XC HA team is planning to make its activities open to public when > the first Postgres-XC HA facility is released. > > Best Regards; > --- > Tetsuo Sakata > > > (2012/07/27 9:20), Koichi Suzuki wrote: >> I've heard another group is working together with Linux HA Japan to >> provide XC RA's. >> >> Sakata-san, could you provide related info if available? >> >> Regards; >> ---------- >> Koichi Suzuki >> >> >> 2012/7/24 Nikhil Sontakke <ni...@st...>: >>> Hi, >>> >>> So what's the latest status of these HA activities for PGXC? >>> >>> Like the coordinator/datanode agents being discussed here, do we have >>> agents for GTM for example? Also is this happening in some open source >>> group where we can participate and see the latest and greatest source >>> changes? >>> >>> Regards, >>> Nikhils > > -- > sakata.tetsuo _at_ lab.ntt.co.jp > SAKATA, Tetsuo. Shinagawa Tokyo JAPAN. > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > |
|
From: Michael P. <mic...@gm...> - 2012-08-10 11:40:30
|
On Fri, Aug 10, 2012 at 7:37 PM, Aris Setyawan <ari...@gm...> wrote: > > Please understand that (mainly because of administrative reasons) > > What kind of administrative reasons, did you mean here? > Company policy. Sakata-san is working for NTT research laboratory, and they are doing some internal research work. Because of company policy, they can only disclose partially information about their work. > > If public unable to join the development process, then this HA/RA will > be easily to be commercial product after it begin stable by community > testing. > > Eg: Bizgres, C-Store. They end to be "dead" opensource projects. > > I think we should develop our own HA, which every one can participate > into. Thus, we can have an "HA" of development process. > Yes it is important to have such discussions and I think it will be very helpful for everybody. However, I am not sure that the core team can be really involved in creating packaging solutions involving Pacemaker or whatever, but we will of course provide support and add the core features necessary to build a wonderful HA world. Btw, as it is useful to discuss about that on this thread. You guys have to know that the HA team needs some support. There are a couple of issues that need to be fixed quickly as it impacts not only NTT team, but also They are not directly related to the core work, but some limitations currently in XC code make HA management harder than it should be. I basically spotted 3 issues I am going to work on and hopefully fix next week that will help HA work: 1) It is not possible to launch a query on a slave Coordinator, making impossible to check if a slave Coordinator is alive or not, it is also not possible to do a pg_dump on it even if hot-standby is on. What happens is that we try to get a transaction ID in a code path specific to XC, when session tries to fetch a new snapshot but we should get that from WAL directly I think. 2) When connecting to a master Datanode, we do not get snapshot from GTM as we should. Hence, a WARNING is sent back to client and we use incorrect local snapshot for operation. I already blocked write operations on Datanodes when an application connects directly to it. 3) Incorrect snapshot data is taken on slave nodes, either Datanode or Coordinator. I believe that snapshot needs to be taken directly from WAL data. Please note that issues 1 and 3 are related. Those things are not complicated, but they need to be taken care of. Regards, -- Michael Paquier http://michael.otacoo.com |
|
From: 坂田 哲夫 <sak...@la...> - 2012-08-13 02:25:40
|
Dear folks, (2012/08/10 19:37), Aris Setyawan wrote: >> Please understand that (mainly because of administrative reasons) > > What kind of administrative reasons, did you mean here? I meant that it would simply take time to get internal approval for us to release HA code in an open source; It will be released by the end of this calendar year. However, once the HA code is released, we can make HA teams activities open to public, as I mentioned before. Best Regards; --- Tetsuo Sakata. > > If public unable to join the development process, then this HA/RA will > be easily to be commercial product after it begin stable by community > testing. > > Eg: Bizgres, C-Store. They end to be "dead" opensource projects. > > I think we should develop our own HA, which every one can participate > into. Thus, we can have an "HA" of development process. > > On 8/10/12, 坂田 哲夫 <sak...@la...> wrote: >> Dear folks, >> >> I'm involved in HA facility implementation for Postgres-XC. This work >> began lecenty by a separate team from Postgres-XC core, say, XC HA team. >> We're planning to release this facility as an open source software by >> the end of this calendar year. >> >> The Postgres-XC HA facility will be developed in two phases: >> >> Phase1: Furnish fundamental functionality to give 1) redundancy to XC >> core component based on streaming replication which makes transactional >> data in datanode durable, and 2) backup GTM with GTM stand-by to handle >> GTM failure. Basic feature of 1) will be taken from PostgreSQL work >> and 2) will be taken from Postgres-XC core feature respectively. >> >> Phase2: Integrate Postgres-XC and Linux-HA. When one of the >> Postgres-XC components fails, it will be failed over automatically to >> continue Postgres-XC operation. For this purpose, XC HA team is >> developing RAs (Resource Agents). RA for coordinator and datanode >> will be implemented first, and then for GTM. XC HA team will be >> involved in them too. >> >> So far, XC HA team has not released any of the code, documentation or >> other materials. Please understand that (mainly because of >> administrative reasons) we're not planning to open XC HA team activities >> to public except for requirements to Postgres-XC core, which might have >> some influence to Postgres-XC design, performance and operations etc. >> >> The XC HA team is planning to make its activities open to public when >> the first Postgres-XC HA facility is released. >> >> Best Regards; >> --- >> Tetsuo Sakata >> >> >> (2012/07/27 9:20), Koichi Suzuki wrote: >>> I've heard another group is working together with Linux HA Japan to >>> provide XC RA's. >>> >>> Sakata-san, could you provide related info if available? >>> >>> Regards; >>> ---------- >>> Koichi Suzuki >>> >>> >>> 2012/7/24 Nikhil Sontakke <ni...@st...>: >>>> Hi, >>>> >>>> So what's the latest status of these HA activities for PGXC? >>>> >>>> Like the coordinator/datanode agents being discussed here, do we have >>>> agents for GTM for example? Also is this happening in some open source >>>> group where we can participate and see the latest and greatest source >>>> changes? >>>> >>>> Regards, >>>> Nikhils >> >> -- >> sakata.tetsuo _at_ lab.ntt.co.jp >> SAKATA, Tetsuo. Shinagawa Tokyo JAPAN. >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Postgres-xc-developers mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers >> > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > -- sakata.tetsuo _at_ lab.ntt.co.jp SAKATA, Tetsuo. Shinagawa Tokyo JAPAN. |
|
From: Ashutosh B. <ash...@en...> - 2012-08-13 04:15:31
|
That's a really big mile stone for Postgres-XC. Many people have expressed concerns about high possibilitiy of SPOF in XC. This solution would prove beneficial. On Fri, Aug 10, 2012 at 3:02 PM, 坂田 哲夫 <sak...@la...> wrote: > Dear folks, > > I'm involved in HA facility implementation for Postgres-XC. This work > began lecenty by a separate team from Postgres-XC core, say, XC HA team. > We're planning to release this facility as an open source software by > the end of this calendar year. > > The Postgres-XC HA facility will be developed in two phases: > > Phase1: Furnish fundamental functionality to give 1) redundancy to XC > core component based on streaming replication which makes transactional > data in datanode durable, and 2) backup GTM with GTM stand-by to handle > GTM failure. Basic feature of 1) will be taken from PostgreSQL work > and 2) will be taken from Postgres-XC core feature respectively. > > Phase2: Integrate Postgres-XC and Linux-HA. When one of the > Postgres-XC components fails, it will be failed over automatically to > continue Postgres-XC operation. For this purpose, XC HA team is > developing RAs (Resource Agents). RA for coordinator and datanode > will be implemented first, and then for GTM. XC HA team will be > involved in them too. > > So far, XC HA team has not released any of the code, documentation or > other materials. Please understand that (mainly because of > administrative reasons) we're not planning to open XC HA team activities > to public except for requirements to Postgres-XC core, which might have > some influence to Postgres-XC design, performance and operations etc. > > The XC HA team is planning to make its activities open to public when > the first Postgres-XC HA facility is released. > > Best Regards; > --- > Tetsuo Sakata > > > (2012/07/27 9:20), Koichi Suzuki wrote: > > I've heard another group is working together with Linux HA Japan to > > provide XC RA's. > > > > Sakata-san, could you provide related info if available? > > > > Regards; > > ---------- > > Koichi Suzuki > > > > > > 2012/7/24 Nikhil Sontakke <ni...@st...>: > >> Hi, > >> > >> So what's the latest status of these HA activities for PGXC? > >> > >> Like the coordinator/datanode agents being discussed here, do we have > >> agents for GTM for example? Also is this happening in some open source > >> group where we can participate and see the latest and greatest source > >> changes? > >> > >> Regards, > >> Nikhils > > -- > sakata.tetsuo _at_ lab.ntt.co.jp > SAKATA, Tetsuo. Shinagawa Tokyo JAPAN. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > -- Best Wishes, Ashutosh Bapat EntepriseDB Corporation The Enterprise Postgres Company |
|
From: Koichi S. <koi...@gm...> - 2012-08-13 05:11:28
|
It really is. I do hope that requirement to XC core is made open as early as possible and XC HA team listens to requirements from the community. So far, I talked with XC HA team member personally. Fortunately, PostgreSQL RA for Pacemaker/Heartbeat is now open to public. I tested all the PostgreSQL scripts for datanode/coordinator and found they work fine. I understand it is a great challenge to establish HA architecture for complexed systems like XC. ---------- Koichi Suzuki 2012/8/13 Ashutosh Bapat <ash...@en...>: > That's a really big mile stone for Postgres-XC. Many people have expressed > concerns about high possibilitiy of SPOF in XC. This solution would prove > beneficial. > > > On Fri, Aug 10, 2012 at 3:02 PM, 坂田 哲夫 <sak...@la...> wrote: >> >> Dear folks, >> >> I'm involved in HA facility implementation for Postgres-XC. This work >> began lecenty by a separate team from Postgres-XC core, say, XC HA team. >> We're planning to release this facility as an open source software by >> the end of this calendar year. >> >> The Postgres-XC HA facility will be developed in two phases: >> >> Phase1: Furnish fundamental functionality to give 1) redundancy to XC >> core component based on streaming replication which makes transactional >> data in datanode durable, and 2) backup GTM with GTM stand-by to handle >> GTM failure. Basic feature of 1) will be taken from PostgreSQL work >> and 2) will be taken from Postgres-XC core feature respectively. >> >> Phase2: Integrate Postgres-XC and Linux-HA. When one of the >> Postgres-XC components fails, it will be failed over automatically to >> continue Postgres-XC operation. For this purpose, XC HA team is >> developing RAs (Resource Agents). RA for coordinator and datanode >> will be implemented first, and then for GTM. XC HA team will be >> involved in them too. >> >> So far, XC HA team has not released any of the code, documentation or >> other materials. Please understand that (mainly because of >> administrative reasons) we're not planning to open XC HA team activities >> to public except for requirements to Postgres-XC core, which might have >> some influence to Postgres-XC design, performance and operations etc. >> >> The XC HA team is planning to make its activities open to public when >> the first Postgres-XC HA facility is released. >> >> Best Regards; >> --- >> Tetsuo Sakata >> >> >> (2012/07/27 9:20), Koichi Suzuki wrote: >> > I've heard another group is working together with Linux HA Japan to >> > provide XC RA's. >> > >> > Sakata-san, could you provide related info if available? >> > >> > Regards; >> > ---------- >> > Koichi Suzuki >> > >> > >> > 2012/7/24 Nikhil Sontakke <ni...@st...>: >> >> Hi, >> >> >> >> So what's the latest status of these HA activities for PGXC? >> >> >> >> Like the coordinator/datanode agents being discussed here, do we have >> >> agents for GTM for example? Also is this happening in some open source >> >> group where we can participate and see the latest and greatest source >> >> changes? >> >> >> >> Regards, >> >> Nikhils >> >> -- >> sakata.tetsuo _at_ lab.ntt.co.jp >> SAKATA, Tetsuo. Shinagawa Tokyo JAPAN. >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Postgres-xc-developers mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > > > > > -- > Best Wishes, > Ashutosh Bapat > EntepriseDB Corporation > The Enterprise Postgres Company > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > |
|
From: 坂田 哲夫 <sak...@la...> - 2013-03-26 02:23:41
|
Hi folks, We are now developing HA facility for XC with another team rather than XC core development. Say them XC HA team. The facility will be released as open source software by the end of this year. The HA facility will be developed through two phases as follow. 1. furnish fundamental function giving redundancy to XC core like as streaming replication to make transactional data in data nodes durable, GTM protecting XIDs with GTM stand-by against failures. These functions are mainly developed by PostgreSQL and PG XC core development teams respectively. 2. integrate PG XC and Linux-HA. When a component occurs failure, we would like to fail over automatically. To realize this, XC HA team is going to develop RAs (resource agents) for data node and coordinator for Linux-HA (pacemaker) at first, then RA for GTM and GTM standby. This integration (in other words, developing RAs) is done by XC HA team. So far, XC HA team does not provide its products including source codes, documentation as open source. And its activities are not opened either except some requirement to XC core which might have influence on XC design, performance, operations and so on. XC HA team's activities will be opened after we release our first HA facility as I mentioned. best regards, Tetsuo Sakata. (2012/07/27 9:20), Koichi Suzuki wrote: > I've heard another group is working together with Linux HA Japan to > provide XC RA's. > > Sakata-san, could you provide related info if available? > > Regards; > ---------- > Koichi Suzuki > > > 2012/7/24 Nikhil Sontakke <ni...@st...>: >> Hi, >> >> So what's the latest status of these HA activities for PGXC? >> >> Like the coordinator/datanode agents being discussed here, do we have >> agents for GTM for example? Also is this happening in some open source >> group where we can participate and see the latest and greatest source >> changes? >> >> Regards, >> Nikhils -- sakata.tetsuo _at_ lab.ntt.co.jp SAKATA, Tetsuo. Shinagawa Tokyo JAPAN. |
|
From: Michael P. <mic...@gm...> - 2013-03-26 03:02:23
|
On Thu, Aug 9, 2012 at 2:50 PM, 坂田 哲夫 <sak...@la...> wrote: > Hi folks, > > We are now developing HA facility for XC with another team rather than > XC core development. Say them XC HA team. The facility will be released > as open source software by the end of this year. > > The HA facility will be developed through two phases as follow. > > 1. furnish fundamental function giving redundancy to XC core like as > streaming replication to make transactional data in data nodes durable, > GTM protecting XIDs with GTM stand-by against failures. These functions > are mainly developed by PostgreSQL and PG XC core development teams > respectively. > > 2. integrate PG XC and Linux-HA. When a component occurs failure, we > would like to fail over automatically. To realize this, XC HA team is > going to develop RAs (resource agents) for data node and coordinator > for Linux-HA (pacemaker) at first, then RA for GTM and GTM standby. > This integration (in other words, developing RAs) is done by XC HA team. > > So far, XC HA team does not provide its products including source codes, > documentation as open source. And its activities are not opened either > except some requirement to XC core which might have influence on XC > design, performance, operations and so on. XC HA team's activities will > be opened after we release our first HA facility as I mentioned. > In short, +1. ;) -- Michael |
|
From: Koichi S. <koi...@gm...> - 2013-03-26 04:38:35
|
I think it's a good idea to disclose what assumption is the HA feature assumes, especially configuration, master slave connection for coordinator/datanode, use of VIP, interface to applications, etc. This will help people to be prepared. I'm also interested if it runs together with Pacemaker/Corosync. Thanks. ---------- Koichi Suzuki # I'm now writing a book on PostgreSQL HA. Do you think I can include this topic to the book? 2012/8/9 坂田 哲夫 <sak...@la...>: > Hi folks, > > We are now developing HA facility for XC with another team rather than XC > core development. Say them XC HA team. The facility will be released as open > source software by the end of this year. > > The HA facility will be developed through two phases as follow. > > 1. furnish fundamental function giving redundancy to XC core like as > streaming replication to make transactional data in data nodes durable, GTM > protecting XIDs with GTM stand-by against failures. These functions are > mainly developed by PostgreSQL and PG XC core development teams > respectively. > > 2. integrate PG XC and Linux-HA. When a component occurs failure, we would > like to fail over automatically. To realize this, XC HA team is going to > develop RAs (resource agents) for data node and coordinator for Linux-HA > (pacemaker) at first, then RA for GTM and GTM standby. > This integration (in other words, developing RAs) is done by XC HA team. > > So far, XC HA team does not provide its products including source codes, > documentation as open source. And its activities are not opened either > except some requirement to XC core which might have influence on XC design, > performance, operations and so on. XC HA team's activities will be opened > after we release our first HA facility as I mentioned. > > best regards, > Tetsuo Sakata. > > > > (2012/07/27 9:20), Koichi Suzuki wrote: >> >> I've heard another group is working together with Linux HA Japan to >> provide XC RA's. >> >> Sakata-san, could you provide related info if available? >> >> Regards; >> ---------- >> Koichi Suzuki >> >> >> 2012/7/24 Nikhil Sontakke <ni...@st...>: >>> >>> Hi, >>> >>> So what's the latest status of these HA activities for PGXC? >>> >>> Like the coordinator/datanode agents being discussed here, do we have >>> agents for GTM for example? Also is this happening in some open source >>> group where we can participate and see the latest and greatest source >>> changes? >>> >>> Regards, >>> Nikhils > > > -- > sakata.tetsuo _at_ lab.ntt.co.jp > SAKATA, Tetsuo. Shinagawa Tokyo JAPAN. |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X