pg.ddx.io  pgsql-cluster-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Sabino Mullane <greg@endpoint.com>
To: DEV_OPS <devops@ww-it.cn>
Cc: pgsql-cluster-hackers@postgresql.org
Subject: Re: Replication over RDMA with Infiniband or RoCE
Date: Tue, 21 Mar 2017 16:57:10 -0400
Message-ID: <20170321205710.GD14887@localhost.localdomain> (raw)
In-Reply-To: <c3bb9ff1-5bc3-bdce-8598-5ca36ca1fb67@ww-it.cn>
References: <e4588333-5faa-8acb-a74f-da37f82cfa8f@ww-it.cn>
	<20170319184748.GT14887@localhost.localdomain>
	<c3bb9ff1-5bc3-bdce-8598-5ca36ca1fb67@ww-it.cn>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-cluster-hackers>

> Yes, we are going to implement this over Postgres' streaming replication
> system,
> the usecase is DR, eg: the sync between two datacenter in same city,
> there had FC link, (Now FC could be used to extend IB network, so we are
> going to implement the native RDMA replication for low latency purpose
> for that case-- it is very import for some critical system, also, this
> replication is preferred base on Postgres' stream replication )

...

Well, I think the starting point should be, why is streaming replication 
not preferred? It's very fast and very robust.

> 2.) the IB based replication system will work with current IP based
> replication system, it mean that, in a replication system, maybe had IB
> replication, and also had IP replication, the case1 is: NodeA to NodeB
> to NodeC,  NodeA -IB->NodeB --IP-->NodeC ; means, NodeA to NodeB could
> be IB base replication, it provide low latency ;     and NodeB to NodeC
> it is based on IP, it's orig IP based replication system ;  the case2
> is: NodeA--IB-->NodeB, NodeA--IP-->NodeC ; means NodeA to NodeB is IB
> replication; and NodeA to NodeC is IP based replication,
> 
> 3.) it will support sync replication and async replication ; also
> support phy replication and logical replication .

...

Honestly, that sounds fairly complex, for not a lot of gain, but I don't 
know that I am competely understanding your proposal. This is a very 
low-activity mailing list - what I would recommend at this point is writing 
up a concise statement about why you need this and run it up the flagpole 
to pgsql-hackers@postgresql.org. I promise you will get more of a response 
there, for better or for worse. :)

-- 
Greg Sabino Mullane greg@endpoint.com
End Point Corporation
PGP Key: 2529 DF6A B8F7 9407 E944  45B4 BC9B 9067 1496 4AC8

Attachments:

  signature.asc (application/pgp-signature, 162B) download

view thread (8+ messages)  latest in thread

Message-ID: <20170321205710.GD14887@localhost.localdomain>
Permalink:  ../20170321205710.GD14887@localhost.localdomain/
Also on:    postgresql.org/message-id/20170321205710.GD14887@localhost.localdomain

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-cluster-hackers@postgresql.org
  Cc: greg@endpoint.com, devops@ww-it.cn
  Subject: Re: Replication over RDMA with Infiniband or RoCE
  In-Reply-To: <20170321205710.GD14887@localhost.localdomain>
  References: <e4588333-5faa-8acb-a74f-da37f82cfa8f@ww-it.cn> <20170319184748.GT14887@localhost.localdomain> <c3bb9ff1-5bc3-bdce-8598-5ca36ca1fb67@ww-it.cn> <20170321205710.GD14887@localhost.localdomain>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox