我的编程空间,编程开发者的网络收藏夹
学习永远不晚

PostgreSQL 数据库HAProxy和PgBouncer配置高可用架构

短信预约 -IT技能 免费直播动态提醒
省份

北京

  • 北京
  • 上海
  • 天津
  • 重庆
  • 河北
  • 山东
  • 辽宁
  • 黑龙江
  • 吉林
  • 甘肃
  • 青海
  • 河南
  • 江苏
  • 湖北
  • 湖南
  • 江西
  • 浙江
  • 广东
  • 云南
  • 福建
  • 海南
  • 山西
  • 四川
  • 陕西
  • 贵州
  • 安徽
  • 广西
  • 内蒙
  • 西藏
  • 新疆
  • 宁夏
  • 兵团
手机号立即预约

请填写图片验证码后获取短信验证码

看不清楚,换张图片

免费获取短信验证码

PostgreSQL 数据库HAProxy和PgBouncer配置高可用架构

一.OS Packages

CentOS 7.2 X64

pcre-devel

openssl-devel

zlib-devel 


二.编译安装haproxy

1.编译安装

haproxy-1.7.1.tar.gz


# make TARGET=linux2628 USE_PCRE=1 USE_OPENSSL=1 USE_ZLIB=1 PREFIX=/usr/local/haproxy

......

......

......

oto_http.o class="lazy" data-src/raw_sock.o class="lazy" data-src/backend.o class="lazy" data-src/tcp_rules.o class="lazy" data-src/lb_chash.o class="lazy" data-src/lb_fwlc.o class="lazy" data-src/lb_fwrr.o class="lazy" data-src/lb_map.o class="lazy" data-src/lb_fas.o class="lazy" data-src/stream_interface.o class="lazy" data-src/stats.o class="lazy" data-src/proto_tcp.o class="lazy" data-src/applet.o class="lazy" data-src/session.o class="lazy" data-src/stream.o class="lazy" data-src/hdr_idx.o class="lazy" data-src/ev_select.o class="lazy" data-src/signal.o class="lazy" data-src/acl.o class="lazy" data-src/sample.o class="lazy" data-src/memory.o class="lazy" data-src/freq_ctr.o class="lazy" data-src/auth.o class="lazy" data-src/proto_udp.o class="lazy" data-src/compression.o class="lazy" data-src/payload.o class="lazy" data-src/hash.o class="lazy" data-src/pattern.o class="lazy" data-src/map.o class="lazy" data-src/namespace.o class="lazy" data-src/mailers.o class="lazy" data-src/dns.o class="lazy" data-src/vars.o class="lazy" data-src/filters.o class="lazy" data-src/flt_http_comp.o class="lazy" data-src/flt_trace.o class="lazy" data-src/flt_spoe.o class="lazy" data-src/cli.o class="lazy" data-src/ev_poll.o class="lazy" data-src/ev_epoll.o class="lazy" data-src/ssl_sock.o class="lazy" data-src/shctx.o ebtree/ebtree.o ebtree/eb32tree.o ebtree/eb64tree.o ebtree/ebmbtree.o ebtree/ebsttree.o ebtree/ebimtree.o ebtree/ebistree.o   -lcrypt  -lz -ldl  -lssl -lcrypto -ldl -L/usr/lib -lpcreposix -lpcre 

gcc -Iinclude -Iebtree -Wall  -O2 -g -fno-strict-aliasing -Wdeclaration-after-statement       -DCONFIG_HAP_LINUX_SPLICE -DTPROXY -DCONFIG_HAP_LINUX_TPROXY -DCONFIG_HAP_CRYPT -DUSE_ZLIB  -DENABLE_POLL -DENABLE_EPOLL -DUSE_CPU_AFFINITY -DASSUME_SPLICE_WORKS -DUSE_ACCEPT4 -DNETFILTER -DUSE_GETSOCKNAME -DUSE_OPENSSL  -DUSE_SYSCALL_FUTEX -DUSE_PCRE -I/usr/include  -DCONFIG_HAPROXY_VERSION=\"1.7.1\" -DCONFIG_HAPROXY_DATE=\"2016/12/13\" \

      -DSBINDIR='"/usr/local/haproxy/sbin"' \

       -c -o class="lazy" data-src/haproxy-systemd-wrapper.o class="lazy" data-src/haproxy-systemd-wrapper.c

gcc  -g -o haproxy-systemd-wrapper class="lazy" data-src/haproxy-systemd-wrapper.o   -lcrypt  -lz -ldl  -lssl -lcrypto -ldl -L/usr/lib -lpcreposix -lpcre 

# make install PREFIX=/usr/local/haproxy

install -d "/usr/local/haproxy/sbin"

install haproxy  "/usr/local/haproxy/sbin"

install -d "/usr/local/haproxy/share/man"/man1

install -m 644 doc/haproxy.1 "/usr/local/haproxy/share/man"/man1

install -d "/usr/local/haproxy/doc/haproxy"

for x in configuration management architecture cookie-options lua WURFL-device-detection proxy-protocol linux-syn-cookies network-namespaces DeviceAtlas-device-detection 51Degrees-device-detection netscaler-client-ip-insertion-protocol close-options SPOE intro; do \

        install -m 644 doc/$x.txt "/usr/local/haproxy/doc/haproxy" ; \

done


2.配置文件


# pwd

/usr/local/haproxy

# mkdir etc

# vi ha_proxy.conf 

global

        log 127.0.0.1 local0 info

        maxconn 40960

        user haproxy

        group haproxy

        daemon

        nbproc 1

        chroot /usr/local/haproxy

        pidfile /usr/local/haproxy/haproxy.pid

defaults

        log global

        mode tcp

        option tcplog

        option dontlognull

        option redispatch

        retries 3

        maxconn 2000

        timeout connect 5s

        timeout client 360s

        timeout server 360s

frontend postgres-front

        bind 192.168.199.201:5432

        default_backend postgresql

backend postgresql 

        mode tcp

        option pgsql-check user haproxy

        balance roundrobin

        server postgresql_01 192.168.199.201:5430 weight 1 check inter 5s rise 2 fall 3

        server postgresql_02 192.168.199.201:5431 weight 1 check inter 5s rise 2 fall 3

listen admin-stats

        mode http

        option httplog

        bind 0.0.0.0:8888

        stats enable

        stats refresh 30s

        stats uri /dbs

        stats realm welcome login\ Haproxy

        stats auth admin:admin

        stats admin if TRUE

#


3.配置PATH变量

    

# vi /etc/profile


unset -f pathmunge

export PATH=/usr/local/haproxy/sbin:$PATH


三、安装pgbouncer

1.安装libevent

libevent-2.0.22-stable.tar.gz

# ./configure 

# make

# make install


ln -s /usr/local/lib/libevent-2.0.so.5 /usr/lib64/libevent-2.0.so.5



2.安装pgbouncer


# ./configure --prefix=/opt/pgbouncer/1.17.2

......

......


Results

  c-ares = no

  evdns = yes

  udns = no

  tls = yes

# make

# make install


# cd /opt/pgbouncer/1.17.2/

# mkdir etc log


配置文件

# cd /opt/pgbouncer/1.17.2/share/doc/pgbouncer

# cp pgbouncer.ini userlist.txt /opt/pgbouncer/1.17.2/etc/

# cd /opt/pgbouncer/1.17.2/etc/


vi pgbouncer.ini


[root@localhost etc]# more pgbouncer.ini 

;; database name = connect string

;;

;; connect string params:

;;   dbname= host= port= user= password=

;;   client_encoding= datestyle= timezone=

;;   pool_size= connect_query=

[databases]

;; * indicate testdb, haproxy

* = port=6432 dbname=testdb user=postgres password=111111


; foodb over unix socket

;foodb =


; redirect bardb to bazdb on localhost

;bardb = host=localhost dbname=bazdb


; access to dest database will go with single user

;forcedb = host=127.0.0.1 port=300 user=baz password=foo client_encoding=UNICODE datestyle=ISO connect_query='SELECT 1'


; use custom pool sizes

;nondefaultdb = pool_size=50 reserve_pool_size=10


; fallback connect string

;* = host=testserver


;; Configuration section

[pgbouncer]


;;;

;;; Administrative settings

;;;


logfile = /opt/pgbouncer/1.17.2/log/pgbouncer.log

pidfile = /opt/pgbouncer/1.17.2/bin/pgbouncer.pid


;;;

;;; Where to wait for clients

;;;


; ip address or * which means all ip-s

listen_addr = *

listen_port = 5430


; unix socket is also used for -R.

; On debian it should be /var/run/postgresql

;unix_socket_dir = /tmp

;unix_socket_mode = 0777

;unix_socket_group =


;;;

;;; TLS settings for accepring clients

;;;


;; disable, allow, require, verify-ca, verify-full

;client_tls_sslmode = disable


;; Path to file that contains trusted CA certs

;client_tls_ca_file = <system default>


;; Private key and cert to present to clients.

;; Required for accepting TLS connections from clients.

;client_tls_key_file =

;client_tls_cert_file =


;; fast, normal, secure, legacy, <ciphersuite string>

;client_tls_ciphers = fast


;; all, secure, tlsv1.0, tlsv1.1, tlsv1.2

;client_tls_protocols = all


;; none, auto, legacy

;client_tls_dheparams = auto


;; none, auto, <curve name>

;client_tls_ecdhcurve = auto


;;;

;;; TLS settings for connecting to backend databases

;;;


;; disable, allow, require, verify-ca, verify-full

;server_tls_sslmode = disable


;; Path to that contains trusted CA certs

;server_tls_ca_file = <system default>


;; Private key and cert to present to backend.

;; Needed only if backend server require client cert.

;server_tls_key_file =

;server_tls_cert_file =


;; all, secure, tlsv1.0, tlsv1.1, tlsv1.2

;server_tls_protocols = all


;; fast, normal, secure, legacy, <ciphersuite string>

;server_tls_ciphers = fast


;;;

;;; Authentication settings

;;;


; any, trust, plain, crypt, md5

auth_type = md5

;auth_file = /8.0/main/global/pg_auth

auth_file = /opt/pgbouncer/1.17.2/etc/userlist.txt


;; Path to HBA-style auth config

;auth_hba_file =


;; Query to use to fetch password from database.  Result

;; must have 2 columns - username and password hash.

;auth_query = SELECT usename, passwd FROM pg_shadow WHERE usename=$1


;;;

;;; Users allowed into database 'pgbouncer'

;;;


; comma-separated list of users, who are allowed to change settings

;admin_users = user2, someadmin, otheradmin

admin_users = pgbadmin


; comma-separated list of users who are just allowed to use SHOW command

;stats_users = stats, root


;;;

;;; Pooler personality questions

;;;


; When server connection is released back to pool:

;   session      - after client disconnects

;   transaction  - after transaction finishes

;   statement    - after statement finishes

pool_mode = transaction


;

; Query for cleaning connection immediately after releasing from client.

; No need to put ROLLBACK here, pgbouncer does not reuse connections

; where transaction is left open.

;

; Query for 8.3+:

;   DISCARD ALL;

;

; Older versions:

;   RESET ALL; SET SESSION AUTHORIZATION DEFAULT

;

; Empty if transaction pooling is in use.

;

server_reset_query = 



; Whether server_reset_query should run in all pooling modes.

; If it is off, server_reset_query is used only for session-pooling.

;server_reset_query_always = 0


;

; Comma-separated list of parameters to ignore when given

; in startup packet.  Newer JDBC versions require the

; extra_float_digits here.

;

;ignore_startup_parameters = extra_float_digits


;

; When taking idle server into use, this query is ran first.

;   SELECT 1

;

server_check_query = select 1


; If server was used more recently that this many seconds ago,

; skip the check query.  Value 0 may or may not run in immediately.

server_check_delay = 10


;; Use <appname - host> as application_name on server.

;application_name_add_host = 0


;;;

;;; Connection limits

;;;


; total number of clients that can connect

max_client_conn = 10240


; default pool size.  20 is good number when transaction pooling

; is in use, in session pooling it needs to be the number of

; max clients you want to handle at any moment

default_pool_size = 100


;; Minimum number of server connections to keep in pool.

min_pool_size = 80


; how many additional connection to allow in case of trouble

;reserve_pool_size = 5


; if a clients needs to wait more than this many seconds, use reserve pool

;reserve_pool_timeout = 3


; how many total connections to a single database to allow from all pools

;max_db_connections = 50

;max_user_connections = 50


; If off, then server connections are reused in LIFO manner

;server_round_robin = 0


;;;

;;; Logging

;;;


;; Syslog settings

;syslog = 0

;syslog_facility = daemon

;syslog_ident = pgbouncer


; log if client connects or server connection is made

;log_connections = 1


; log if and why connection was closed

;log_disconnections = 1


; log error messages pooler sends to clients

;log_pooler_errors = 1


;; Period for writing aggregated stats into log.

;stats_period = 60


;; Logging verbosity.  Same as -v switch on command line.

;verbose=0


;;;

;;; Timeouts

;;;


;; Close server connection if its been connected longer.

server_lifetime = 300


;; Close server connection if its not been used in this time.

;; Allows to clean unnecessary connections from pool after peak.

;server_idle_timeout = 60


;; Cancel connection attempt if server does not answer takes longer.

server_connect_timeout = 10


;; If server login failed (server_connect_timeout or auth failure)

;; then wait this many second.

server_login_retry = 3


;; Dangerous.  Server connection is closed if query does not return

;; in this time.  Should be used to survive network problems,

;; _not_ as statement_timeout. (default: 0)

;query_timeout = 0


;; Dangerous.  Client connection is closed if the query is not assigned

;; to a server in this time.  Should be used to limit the number of queued

;; queries in case of a database or network failure. (default: 120)

;query_wait_timeout = 120


;; Dangerous.  Client connection is closed if no activity in this time.

;; Should be used to survive network problems. (default: 0)

;client_idle_timeout = 0


;; Disconnect clients who have not managed to log in after connecting

;; in this many seconds.

;client_login_timeout = 60


;; Clean automatically created database entries (via "*") if they

;; stay unused in this many seconds.

; autodb_idle_timeout = 3600


;; How long SUSPEND/-R waits for buffer flush before closing connection.

;suspend_timeout = 10


;; Close connections which are in "IDLE in transaction" state longer than

;; this many seconds.

idle_transaction_timeout = 300


;;;

;;; Low-level tuning options

;;;


;; buffer for streaming packets

;pkt_buf = 4096


;; man 2 listen

listen_backlog = 2048


;; Max number pkt_buf to process in one event loop.

;sbuf_loopcnt = 5


;; Maximum Postgres protocol packet size.

;max_packet_size = 2147483647


;; networking options, for info: man 7 tcp


;; Linux: notify program about new connection only if there

;; is also data received.  (Seconds to wait.)

;; On Linux the default is 45, on other OS'es 0.

;tcp_defer_accept = 0


;; In-kernel buffer size (Linux default: 4096)

;tcp_socket_buffer = 0


;; whether tcp keepalive should be turned on (0/1)

;tcp_keepalive = 1


;; following options are Linux-specific.

;; they also require tcp_keepalive=1


;; count of keepaliva packets

;tcp_keepcnt = 0


;; how long the connection can be idle,

;; before sending keepalive packets

;tcp_keepidle = 0


;; The time between individual keepalive probes.

;tcp_keepintvl = 0


;; DNS lookup caching time

;dns_max_ttl = 15


;; DNS zone SOA lookup period

;dns_zone_check_period = 0


;; DNS negative result caching time

;dns_nxdomain_ttl = 15


;;;

;;; Random stuff

;;;


;; Hackish security feature.  Helps against SQL-injection - when PQexec is disabled,

;; multi-statement cannot be made.

;disable_pqexec=0


;; Config file to use for next RELOAD/SIGHUP.

;; By default contains config file from command line.

;conffile


;; Win32 service name to register as.  job_name is alias for service_name,

;; used by some Skytools scripts.

;service_name = pgbouncer

;job_name = pgbouncer


;; Read additional config from the /etc/pgbouncer/pgbouncer-other.ini file

;%include /etc/pgbouncer/pgbouncer-other.ini


# vi userlist.txt 

"pgbadmin" "pgbouncer123"

"haproxy" "haproxy"

#


3.修改数据库访问端口'6432'


# netstat -ltnp

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      844/sshd            

tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      1572/master         

tcp        0      0 0.0.0.0:6432            0.0.0.0:*               LISTEN      14974/postmaster      



设置PATH

# vi /etc/profile

export PATH=/opt/pgbouncer/1.17.2/bin:/usr/local/haproxy/sbin:$PATH


4.初始化数据库


建立数据库role haproxy


postgres=# CREATE ROLE haproxy LOGIN

  ENCRYPTED PASSWORD 'md53b4da8c0b2ce93c288203e3d363895a6'

  SUPERUSER INHERIT CREATEDB CREATEROLE REPLICATION;

  

建立数据库

postgres=# \c postgres haproxy;

postgres=# create database testdb;


建立表

testdb=# create table t1(id int, name varchar(20));

CREATE TABLE

testdb=# 


数据库访问控制


# vi pg_hba.conf


host    all             all             192.168.199.0/24            trust



5.启动pgbouncer


# chown postgres.postgres -R /opt/pgbouncer/

# su - postgres


1)pgbouncer01


$ pgbouncer -d /opt/pgbouncer/1.17.2/etc/pgbouncer.ini 

2016-12-20 15:09:52.182 15013 LOG File descriptor limit: 1024 (H:4096), max_client_conn: 10240, max fds possible: 10350


2) pgbouncer02


配置文件

; ip address or * which means all ip-s

listen_addr = *

listen_port = 5431

;;;

;;; Administrative settings

;;;


logfile = /opt/pgbouncer/1.17.2/log/pgbouncer02.log

pidfile = /opt/pgbouncer/1.17.2/bin/pgbouncer02.pid



$ pgbouncer -d /opt/pgbouncer/1.17.2/etc/pgbouncer02.ini 

2016-12-20 15:12:06.964 15020 LOG File descriptor limit: 1024 (H:4096), max_client_conn: 10240, max fds possible: 10350


启动ha-proxy

# haproxy -f /usr/local/haproxy/etc/ha_proxy.conf


# netstat -lntp

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    

tcp        0      0 0.0.0.0:5430            0.0.0.0:*               LISTEN      16497/pgbouncer     

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      844/sshd            

tcp        0      0 0.0.0.0:5431            0.0.0.0:*               LISTEN      16500/pgbouncer     

tcp        0      0 0.0.0.0:8888            0.0.0.0:*               LISTEN      16510/haproxy       

tcp        0      0 192.168.199.201:5432    0.0.0.0:*               LISTEN      16510/haproxy       

tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      1572/master         

tcp        0      0 0.0.0.0:6432            0.0.0.0:*               LISTEN      14974/postmaster    

tcp6       0      0 :::5430                 :::*                    LISTEN      16497/pgbouncer     

tcp6       0      0 :::22                   :::*                    LISTEN      844/sshd            

tcp6       0      0 :::5431                 :::*                    LISTEN      16500/pgbouncer     

tcp6       0      0 ::1:25                  :::*                    LISTEN      1572/master         

tcp6       0      0 :::6432                 :::*                    LISTEN      14974/postmaster    



使用pgadmin客户端访问DB:testdb, user:haproxy, password:haproxy,IP:192.168.199.201, port:5432



测试连接


insert into t1 select generate_series(1,10000),'name';


$ more test.conf 

SELECT id FROM t1 WHERE id = 50;


pgbench -h 192.168.199.201 -U haproxy -c 25 -j 25 -M prepared -n -s 500 -T 60 testdb  -f ./test.conf


免责声明:

① 本站未注明“稿件来源”的信息均来自网络整理。其文字、图片和音视频稿件的所属权归原作者所有。本站收集整理出于非商业性的教育和科研之目的,并不意味着本站赞同其观点或证实其内容的真实性。仅作为临时的测试数据,供内部测试之用。本站并未授权任何人以任何方式主动获取本站任何信息。

② 本站未注明“稿件来源”的临时测试数据将在测试完成后最终做删除处理。有问题或投稿请发送至: 邮箱/279061341@qq.com QQ/279061341

PostgreSQL 数据库HAProxy和PgBouncer配置高可用架构

下载Word文档到电脑,方便收藏和打印~

下载Word文档

猜你喜欢

MySQL INSERT锁与数据库高可用架构的选择

在MySQL中,INSERT锁是一种排他锁,用于阻止其他事务在插入数据时对同一行数据进行修改。这种锁在插入数据时会自动被获取,确保数据的一致性和完整性。当涉及到数据库高可用架构的选择时,应该考虑以下几点:主从复制:主从复制是最常见的高可用
MySQL INSERT锁与数据库高可用架构的选择
2024-08-14

数据库学习之十三:mysql高可用配置

十三、mysql高可用1、普通主从复制架构存在的不足高可用?业务不间断的工作。用户的体验不出来业务断点。普通主从环境,存在的问题:1、监控的问题:APP应用程序,并不具备监控数据库的功能,没有责任监控数据库是否能连接。2、选主的问题:3、failover:VI
数据库学习之十三:mysql高可用配置
2019-12-19

数据库管理与高可用----MHA高可用配置及故障切换

原文:https://blog.51cto.com/14625831/2547984
数据库管理与高可用----MHA高可用配置及故障切换
2017-04-19

基于keepalived配置数据库主从实现高可用

基于keepalived配置数据库主从实现高可用使用keepalived来监听端口,实现数据库的高可用。实现效果,其中一台数据库服务器突然出故障或关机时,应该不影响应用正常运行,等待服务器启动之后,数据能够自动同步,保持数据一致性。主从配置架构图及原理主从状态
基于keepalived配置数据库主从实现高可用
2021-08-06

如何在MySQL数据库中实现MHA高可用配置

本篇文章给大家分享的是有关如何在MySQL数据库中实现MHA高可用配置,小编觉得挺实用的,因此分享给大家学习,希望大家阅读完这篇文章后可以有所收获,话不多说,跟着小编一起来看看吧。一、MHA介绍(一)、什么是MHAMHA(MasterHig
2023-06-06

SQL Server与MySQL对比:哪个数据库更适合高可用性架构?

SQL Server与MySQL对比:哪个数据库更适合高可用性架构?在当今的数据驱动世界中,高可用性是构建可靠和稳定系统的必要条件之一。数据库作为数据存储和管理的核心组件,其高可用性对于企业的业务运转至关重要。在众多的数据库中,SQL Se
2023-10-22

如何理解配置数据库高可用性中的SEGMENT镜像

本篇文章为大家展示了如何理解配置数据库高可用性中的SEGMENT镜像,内容简明扼要并且容易理解,绝对能使你眼前一亮,通过这篇文章的详细介绍希望你能有所收获。 前面介绍过了GREENPLUM数据库的备份和恢复。这部分主要介绍GR
2023-06-06

Linux数据库系统的高可用与负载均衡怎么配置

在Linux数据库系统中,高可用性和负载均衡通常通过使用集群和复制技术来实现。下面是一些常见的配置方法:数据库集群:使用数据库集群可以将数据库服务器组织成一个集群,提供高可用性和负载均衡。常见的数据库集群如MySQL Cluster、Pos
Linux数据库系统的高可用与负载均衡怎么配置
2024-05-06

Golang与RabbitMQ实现消息持久化、数据安全和高可用的架构设计和实现

要实现消息持久化、数据安全和高可用的架构设计和实现,可以使用Golang和RabbitMQ的组合。下面是一个简单的架构设计和实现示例:1. 架构设计:- 使用RabbitMQ作为消息中间件,负责消息的传递和存储。- 使用Golang编写消费
2023-10-20

编程热搜

目录