Re: Throttling Streamming Replication

Rodrigo Pereira da Silva <rodrigo@xxxxxxxxxxxxxxxx> · Fri, 25 Jan 2013 13:08:03 -0200



    That's a good idea, but we are using
      windows copy command, not sure if it has something similar.
      Anyway, we just talked to infrastructure provider and they figured
      out it was a problem with their monitoring system, so we are not
      reaching 30k packages actually.

      
      Thanks a lot for the replies,

      
      Em 25/01/2013 12:18, Cliff de Carteret escreveu:

    
      Can you not change your method of streaming
        replication. What is your archive command, are you using rsync
        as you can control the bandwidth limit?
        

        We use: archive_command = 'test ! -f
          /opt/postgres/remote_pgsql/wal_archive/%f && rsync -az
          %p /opt/postgres/remote_pgsql/wal_archive/%f'
        
          
          According to the link below you can add
            --bwlimit=1000 to the rsync arguments
          

          http://scratching.psybermonkey.net/2009/03/rsync-transfer-rate-limit-aka-it-down.html

          
        On 25 January 2013 12:59, Magnus
          Hagander <magnus@xxxxxxxxxxxx>
          wrote:

          
            On Fri, Jan 25, 2013 at 1:59 PM, Rodrigo
              Pereira da Silva

              <rodrigo@xxxxxxxxxxxxxxxx>
              wrote:

              > Hi Guys,

              >

              > We are having a problem with our infrastructure
              provider because the network

              > traffic between master and slave server is reaching
              more than 30k packages

              > per second(SLA says 20k/second).

              > Is there any way to throttle the streamming
              replication? I meant, any

              > parameter that I set the max number of megabytes sent
              to standby server per

              > second?

              > I didn't have any luck looking at the postgresql
              streamming replication

              > documentation. There is the wal_sender_delay, but I
              suppose that if I set

              > more than 1 second, it could accumulate a bunch of
              wal files and send it at

              > once. So, it wouldn't work.

              
            No, there is no such parameter. You might be able to send it
            through

            some proxy that slows it down, but there is no builtin
            support to do

            that.

            
            --

             Magnus Hagander

             Me: http://www.hagander.net/

             Work: http://www.redpill-linpro.com/

            
                --

                Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)

                To make changes to your subscription:

                http://www.postgresql.org/mailpref/pgsql-general

              
    -- 
Rodrigo Pereira da Silva
rodrigo@xxxxxxxxxxxxxxxx
http://www.paripassu.com.br
Rua Coronel Luis Caldeira, nº 67, Bloco 1, Sala 3A
88034-110 • Florianópolis • SC
Tel. (48) 3207-5755