{"id":10097,"date":"2021-01-12T13:48:30","date_gmt":"2021-01-12T12:48:30","guid":{"rendered":"http:\/\/arumel.com\/?p=10097"},"modified":"2021-01-12T13:48:30","modified_gmt":"2021-01-12T12:48:30","slug":"failover-auto-pgbouncer-repmgr-postgresql-13-parte-1","status":"publish","type":"post","link":"https:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\/","title":{"rendered":"Failover auto – Pgbouncer + Repmgr + Postgresql 13 (parte 1)"},"content":{"rendered":"

\"\"<\/p>\n

Ver configuraci\u00f3n parte 1<\/a><\/p>\n

Ver configuraci\u00f3n parte 2<\/a><\/p>\n

Ver configuraci\u00f3n parte 1 daemon repmgr<\/a><\/p>\n

Instalamos el pgbouncer en el nodo \u00abtestigo\u00bb (postgres4):<\/p>\n

[root@postgres4 ~]# dnf install pgbouncer<\/strong><\/code><\/p>\n

 <\/p>\n

Para hacer las pruebas de conexi\u00f3n de clientes, vamos a crear una nueva base de datos en el cluster (appdb) a la que se conectar\u00e1n los clientes.<\/p>\n

A\u00f1adimos la siguiente entrada en el pg_hba.conf<\/strong> del resto de nodos (postgres1, postgres2, postgres3) y recargamos:<\/p>\n

host appdb appdb 192.168.0.0\/24 trust<\/code><\/p>\n

sudo systemctl reload postgresql-13<\/code><\/p>\n

 <\/p>\n

A\u00f1adimos las siguientes entradas al fichero \/etc\/pgbouncer\/pgbouncer.ini<\/strong>:<\/p>\n

[pgbouncer]<\/code><\/p>\n

logfile = \/var\/log\/pgbouncer\/pgbouncer.log<\/code>
\npidfile = \/var\/run\/pgbouncer\/pgbouncer.pid<\/code><\/p>\n

listen_addr = *<\/code>
\nlisten_port = 6432<\/strong><\/code>
\nunix_socket_dir = \/tmp<\/code><\/p>\n

auth_type = trust<\/code>
\nauth_file = \/etc\/pgbouncer\/userlist.txt<\/code>
\nauth_hba_file = \/etc\/pgbouncer\/pg_hba.conf<\/code><\/p>\n

admin_users = postgres<\/code>
\nstats_users = postgres<\/code><\/p>\n

pool_mode = transaction<\/code>
\nserver_reset_query = DISCARD ALL<\/code><\/p>\n

max_client_conn = 100<\/code>
\ndefault_pool_size = 20<\/code>
\nmin_pool_size = 5<\/code>
\nreserve_pool_size = 5<\/code>
\nreserve_pool_timeout = 3<\/code><\/p>\n

log_connections = 1<\/code>
\nlog_disconnections = 1<\/code>
\nlog_pooler_errors = 1<\/code><\/p>\n

%include \/etc\/pgbouncer\/pgbouncer.database.ini<\/code><\/p>\n

 <\/p>\n

El fichero \/etc\/pgbouncer\/pgbouncer.database.ini<\/strong> apunta al nodo primario del cluster (postgres2 en este caso):<\/p>\n

[root@postgres4 ~]# cat \/etc\/pgbouncer\/pgbouncer.database.ini<\/code>
\n[databases]<\/code>
\nappdb= host=postgres2<\/strong> dbname=appdb<\/code><\/p>\n

 <\/p>\n

Y creamos el fichero \/etc\/pgbouncer\/userlist.txt<\/strong> para el usuario y su password:<\/p>\n

[root@postgres4 ~]# cat \/etc\/pgbouncer\/userlist.txt<\/code>
\n\"appdb\" \"appdb\"<\/code><\/p>\n

 <\/p>\n

A\u00f1adimos un fichero pg_hba.conf<\/strong> para el pgbouncer (para poder parar y arrancar desde el resto de nodos el pool de conexiones en el failover):<\/p>\n

[root@postgres4 ~]# chown pgbouncer:pgbouncer \/etc\/pgbouncer\/pg_hba.conf<\/code><\/p>\n

[root@postgres4 ~]# cat \/etc\/pgbouncer\/pg_hba.conf<\/code><\/p>\n

# TYPE DATABASE USER ADDRESS METHOD<\/code>
\nhost pgbouncer pgbouncer 192.168.0.0\/24 trust<\/code><\/p>\n

 <\/p>\n

A\u00f1adimos al fichero \/etc\/sudoers<\/strong> las siguientes entradas, por comodidad:<\/p>\n

## Allow root to run any commands anywhere<\/code>
\nroot ALL=(ALL) ALL<\/code>
\npostgres ALL= NOPASSWD: \/bin\/systemctl stop postgresql-13, \\<\/code>
\n\/bin\/systemctl start postgresql-13, \\<\/code>
\n\/bin\/systemctl status postgresql-13, \\<\/code>
\n\/bin\/systemctl restart postgresql-13, \\<\/code>
\n\/bin\/systemctl reload postgresql-13, \\<\/code>
\n\/bin\/systemctl start repmgr13, \\<\/code>
\n\/bin\/systemctl status repmgr13, \\<\/code>
\n\/bin\/systemctl restart repmgr13, \\<\/code>
\n\/bin\/systemctl reload repmgr13, \\<\/code>
\n\/bin\/systemctl stop repmgr13, \\<\/code>
\n\/bin\/systemctl start pgbouncer, \\<\/code><\/strong>
\n\/bin\/systemctl restart pgbouncer, \\<\/code><\/strong>
\n\/bin\/systemctl reload pgbouncer, \\<\/code><\/strong>
\n\/bin\/systemctl stop pgbouncer<\/code><\/strong><\/p>\n

 <\/p>\n

Cambiamos permisos a los ficheros:<\/p>\n

[root@postgres4 ~]# chown postgres:postgres \/etc\/pgbouncer \/etc\/pgbouncer\/*.ini<\/strong><\/code><\/p>\n

[root@postgres4 pgbouncer]# ls -l<\/code>
\ntotal 24<\/code>
\n-rwx------. 1 root root 819 nov 24 11:03 mkauth.py<\/code>
\n-rw-r--r--. 1 postgres postgres 34 ene 9 09:31 pgbouncer.database.ini<\/code>
\n-rw-r--r--. 1 postgres postgres 9349 ene 9 08:54 pgbouncer.ini<\/code>
\n-rw-r--r--. 1 root root 16 ene 9 09:33 userlist.txt<\/code><\/p>\n

 <\/p>\n

Y reiniciamos pgbouncer:<\/p>\n

[root@postgres4 ~]# systemctl restart pgbouncer<\/code><\/p>\n

 <\/p>\n

Creamos la base de datos \u00abappdb\u00bb en el cluster (en el nodo primario postgres2) a la que se conectar\u00e1n los clientes:<\/p>\n

[local]:5432; postgres@postgres # create role appdb login;<\/strong><\/code>
\nCREATE ROLE<\/code><\/p>\n

[local]:5432; postgres@postgres # \\password appdb<\/strong><\/code>
\nEnter new password: <\/code>
\nEnter it again: <\/code>
\n********* QUERY **********<\/code>
\nALTER USER appdb PASSWORD 'SCRAM-SHA-256$4096:Hu2zNyVgzoEcZXrh1X4sKA==$XVOkHMvfcwPTf74abgWgS4tKtoC1lSz8rsBrbFwEHbs=:UMmvFFvb6FO8qta6y9cBMTZ9AzJ\/FGoV0DXpA7mJlDo='<\/code>
\n**************************<\/code><\/p>\n

[local]:5432; postgres@postgres # create database appdb owner appdb;<\/strong><\/code>
\nCREATE DATABASE<\/code><\/code><\/p>\n

 <\/p>\n

A\u00f1adimos en el firewall del nodo del pgbouncer:<\/p>\n

[root@postgres4 ~]# firewall-cmd --permanent --zone=public --add-rich-rule='rule family=ipv4 source address=192.168.0.0\/24 port port=6432 protocol=tcp accept'<\/code>
\n[root@postgres4 ~]# firewall-cmd --reload<\/code><\/p>\n

 <\/p>\n

Y hacemos pruebas de conexi\u00f3n desde el nodo cliente (postgres4) a la base de datos \u00abappdb\u00bb, del nodo postgres2 en modo r\/w, a trav\u00e9s del pgbouncer, y creamos una tabla de prueba:<\/p>\n

[postgres@postgres4 ~]$ psql 'host=192.168.0.104 user=appdb port=6432'<\/strong><\/code>
\n192.168.0.104:6432; appdb@appdb # create table prueba(columna char(20));<\/code>
\nCREATE TABLE<\/code><\/p>\n

[postgres@postgres4 ~]$ psql 'host=192.168.0.104 user=appdb port=6432'<\/strong><\/code>
\n192.168.0.104:6432; appdb@appdb # \\d prueba<\/code><\/p>\n

Table \"public.prueba\"<\/code>
\n+---------+---------------+-----------+----------+---------+<\/code>
\n| Column | Type | Collation | Nullable | Default |<\/code>
\n+---------+---------------+-----------+----------+---------+<\/code>
\n| columna | character(20) | | | |<\/code>
\n+---------+---------------+-----------+----------+---------+<\/code><\/p>\n

[postgres@postgres4 ~]$ psql --host=192.168.0.104 --username=appdb --port=6432<\/strong><\/code>
\n192.168.0.104:6432; appdb@appdb # select inet_server_addr(), inet_server_port();<\/code>
\n+------------------+------------------+<\/code>
\n| inet_server_addr | inet_server_port |<\/code>
\n+------------------+------------------+<\/code>
\n| 192.168.0.102 | 5432 |<\/code>
\n+------------------+------------------+<\/code>
\n(1 row)<\/code><\/p>\n

 <\/p>\n

Creamos un script para integrarlo con el repmgr y que provoque el failover entre los nodos, teniendo el control del pgbouncer y su pool de conexiones:<\/p>\n

[root@postgres1 ~]# mkdir -p \/var\/lib\/postgres\/repmgr\/<\/code>
\n[root@postgres1 ~]# chmod 700 \/var\/lib\/postgres\/repmgr\/promote.sh<\/code>
\n[root@postgres1 ~]# chown postgres:postgres \/var\/lib\/postgres\/repmgr\/promote.sh<\/code><\/p>\n

[postgres@postgres1 ~]$ cat \/var\/lib\/postgres\/repmgr\/promote.sh<\/strong><\/code>
\n#!\/bin\/bash<\/code>
\nset -u<\/code>
\nset -e<\/code><\/p>\n

# Configurable items<\/code>
\nPGBOUNCER_HOSTS=\"postgres4\"<\/code>
\nPGBOUNCER_DATABASE_INI=\"\/etc\/pgbouncer\/pgbouncer.database.ini\"<\/code>
\nPGBOUNCER_DATABASES=\"appdb\"<\/code>
\nPGBOUNCER_PORT=6432<\/code><\/p>\n

REPMGR_DB=\"repmgr\"<\/code>
\nREPMGR_USER=\"repmgr\"<\/code><\/p>\n

# 0.- Pause pgbouncer<\/code>
\nfor HOST in ${PGBOUNCER_HOSTS}<\/code>
\ndo<\/code>
\nfor DB in ${PGBOUNCER_DATABASES}<\/code>
\ndo<\/code>
\n\/usr\/pgsql-13\/bin\/psql -U postgres -h ${HOST} -p ${PGBOUNCER_PORT} pgbouncer -tc \"pause ${DB}\"<\/code>
\ndone<\/code>
\ndone<\/code><\/p>\n

# 1. Promote server<\/code>
\n\/usr\/pgsql-13\/bin\/repmgr standby promote -f \/etc\/repmgr\/13\/repmgr.conf --log-to-file<\/code><\/p>\n

# 2. Reconfigure pgbouncer instances<\/code><\/p>\n

PGBOUNCER_DATABASE_INI_NEW=\"\/tmp\/pgbouncer.database.ini\"<\/code><\/p>\n

for HOST in ${PGBOUNCER_HOSTS}<\/code>
\ndo<\/code>
\nfor DB in ${PGBOUNCER_DATABASES}<\/code>
\ndo<\/code>
\n# Recreate the pgbouncer config file<\/code>
\necho -e \"[databases]\" > ${PGBOUNCER_DATABASE_INI_NEW}<\/code>
\necho -e \"${DB}= host=$(hostname -f) dbname=${DB}\" >> ${PGBOUNCER_DATABASE_INI_NEW}<\/code>
\n# Copy new config file<\/code>
\nscp ${PGBOUNCER_DATABASE_INI_NEW} ${HOST}:${PGBOUNCER_DATABASE_INI}<\/code>
\n# Reload<\/code>
\n\/usr\/pgsql-13\/bin\/psql -U postgres -h ${HOST} -p ${PGBOUNCER_PORT} pgbouncer -tc \"reload\"<\/code>
\n# Resume<\/code>
\n\/usr\/pgsql-13\/bin\/psql -U postgres -h ${HOST} -p ${PGBOUNCER_PORT} pgbouncer -tc \"resume ${DB}\"<\/code>
\ndone<\/code>
\ndone<\/code><\/p>\n

# 3. Clean up generated file<\/code>
\nrm ${PGBOUNCER_DATABASE_INI_NEW}<\/code><\/p>\n

 <\/p>\n

Ahora, en el fichero \/etc\/repmgr\/13\/repmgr.conf<\/strong>, de los nodos del cluster, cambiamos la l\u00ednea del promote_command para indicarle nuestro script:<\/p>\n

promote_command='\/var\/lib\/postgres\/repmgr\/promote.sh'<\/code><\/p>\n

 <\/p>\n

Y reiniciamos el demonio en todos los nodos:<\/p>\n

sudo systemctl restart repmgr13<\/code><\/p>\n

 <\/p>\n

Ver parte 2<\/a><\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Ver configuraci\u00f3n parte 1 Ver configuraci\u00f3n parte 2 Ver configuraci\u00f3n parte 1 daemon repmgr Instalamos el pgbouncer en el nodo \u00abtestigo\u00bb (postgres4): [root@postgres4 ~]# dnf install pgbouncer   Para hacer las pruebas de conexi\u00f3n de clientes, vamos a crear una nueva base de datos en el cluster (appdb) a la que se conectar\u00e1n los clientes. […]<\/p>\n","protected":false},"author":11,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[27,65],"tags":[437,436,438,434,433],"class_list":["post-10097","post","type-post","status-publish","format-standard","hentry","category-portada-es","category-postgresql-es","tag-auto","tag-failover","tag-pgbouncer","tag-postgresql","tag-repmgr"],"yoast_head":"\nFailover auto - Pgbouncer + Repmgr + Postgresql 13 (parte 1) - Arumel<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\/\" \/>\n<meta property=\"og:locale\" content=\"es_ES\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Failover auto - Pgbouncer + Repmgr + Postgresql 13 (parte 1) - Arumel\" \/>\n<meta property=\"og:description\" content=\"Ver configuraci\u00f3n parte 1 Ver configuraci\u00f3n parte 2 Ver configuraci\u00f3n parte 1 daemon repmgr Instalamos el pgbouncer en el nodo \u00abtestigo\u00bb (postgres4): [root@postgres4 ~]# dnf install pgbouncer   Para hacer las pruebas de conexi\u00f3n de clientes, vamos a crear una nueva base de datos en el cluster (appdb) a la que se conectar\u00e1n los clientes. […]\" \/>\n<meta property=\"og:url\" content=\"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\/\" \/>\n<meta property=\"og:site_name\" content=\"Arumel\" \/>\n<meta property=\"article:published_time\" content=\"2021-01-12T12:48:30+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/arumel.com\/wp-content\/uploads\/2021\/01\/pgbouncer-repmgr-auto-285x300.png\" \/>\n<meta name=\"author\" content=\"sm\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Escrito por\" \/>\n\t<meta name=\"twitter:data1\" content=\"sm\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tiempo de lectura\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\\\/#article\",\"isPartOf\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\\\/\"},\"author\":{\"name\":\"sm\",\"@id\":\"http:\\\/\\\/arumel.com\\\/#\\\/schema\\\/person\\\/e270e777d900dcd47f8eb3895c076b64\"},\"headline\":\"Failover auto – Pgbouncer + Repmgr + Postgresql 13 (parte 1)\",\"datePublished\":\"2021-01-12T12:48:30+00:00\",\"mainEntityOfPage\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\\\/\"},\"wordCount\":307,\"commentCount\":0,\"image\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/arumel.com\\\/wp-content\\\/uploads\\\/2021\\\/01\\\/pgbouncer-repmgr-auto-285x300.png\",\"keywords\":[\"auto\",\"failover\",\"pgbouncer\",\"postgresql\",\"repmgr\"],\"articleSection\":[\"portada\",\"PostgreSQL\"],\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\\\/\",\"url\":\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\\\/\",\"name\":\"Failover auto - Pgbouncer + Repmgr + Postgresql 13 (parte 1) - Arumel\",\"isPartOf\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\\\/#primaryimage\"},\"image\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/arumel.com\\\/wp-content\\\/uploads\\\/2021\\\/01\\\/pgbouncer-repmgr-auto-285x300.png\",\"datePublished\":\"2021-01-12T12:48:30+00:00\",\"author\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/#\\\/schema\\\/person\\\/e270e777d900dcd47f8eb3895c076b64\"},\"breadcrumb\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\\\/#breadcrumb\"},\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\\\/#primaryimage\",\"url\":\"http:\\\/\\\/arumel.com\\\/wp-content\\\/uploads\\\/2021\\\/01\\\/pgbouncer-repmgr-auto-285x300.png\",\"contentUrl\":\"http:\\\/\\\/arumel.com\\\/wp-content\\\/uploads\\\/2021\\\/01\\\/pgbouncer-repmgr-auto-285x300.png\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Portada\",\"item\":\"https:\\\/\\\/arumel.com\\\/es\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Failover auto – Pgbouncer + Repmgr + Postgresql 13 (parte 1)\"}]},{\"@type\":\"WebSite\",\"@id\":\"http:\\\/\\\/arumel.com\\\/#website\",\"url\":\"http:\\\/\\\/arumel.com\\\/\",\"name\":\"Arumel\",\"description\":\"Outro sitio WordPress m\u00e1is\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"http:\\\/\\\/arumel.com\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"es\"},{\"@type\":\"Person\",\"@id\":\"http:\\\/\\\/arumel.com\\\/#\\\/schema\\\/person\\\/e270e777d900dcd47f8eb3895c076b64\",\"name\":\"sm\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6207cd8b9baaee6c4cff92251bb20e4b48ce165f93e926218da90832d9f334f9?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6207cd8b9baaee6c4cff92251bb20e4b48ce165f93e926218da90832d9f334f9?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6207cd8b9baaee6c4cff92251bb20e4b48ce165f93e926218da90832d9f334f9?s=96&d=mm&r=g\",\"caption\":\"sm\"},\"url\":\"https:\\\/\\\/arumel.com\\\/es\\\/author\\\/sergio\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Failover auto - Pgbouncer + Repmgr + Postgresql 13 (parte 1) - Arumel","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\/","og_locale":"es_ES","og_type":"article","og_title":"Failover auto - Pgbouncer + Repmgr + Postgresql 13 (parte 1) - Arumel","og_description":"Ver configuraci\u00f3n parte 1 Ver configuraci\u00f3n parte 2 Ver configuraci\u00f3n parte 1 daemon repmgr Instalamos el pgbouncer en el nodo \u00abtestigo\u00bb (postgres4): [root@postgres4 ~]# dnf install pgbouncer   Para hacer las pruebas de conexi\u00f3n de clientes, vamos a crear una nueva base de datos en el cluster (appdb) a la que se conectar\u00e1n los clientes. […]","og_url":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\/","og_site_name":"Arumel","article_published_time":"2021-01-12T12:48:30+00:00","og_image":[{"url":"http:\/\/arumel.com\/wp-content\/uploads\/2021\/01\/pgbouncer-repmgr-auto-285x300.png","type":"","width":"","height":""}],"author":"sm","twitter_card":"summary_large_image","twitter_misc":{"Escrito por":"sm","Tiempo de lectura":"5 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\/#article","isPartOf":{"@id":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\/"},"author":{"name":"sm","@id":"http:\/\/arumel.com\/#\/schema\/person\/e270e777d900dcd47f8eb3895c076b64"},"headline":"Failover auto – Pgbouncer + Repmgr + Postgresql 13 (parte 1)","datePublished":"2021-01-12T12:48:30+00:00","mainEntityOfPage":{"@id":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\/"},"wordCount":307,"commentCount":0,"image":{"@id":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\/#primaryimage"},"thumbnailUrl":"http:\/\/arumel.com\/wp-content\/uploads\/2021\/01\/pgbouncer-repmgr-auto-285x300.png","keywords":["auto","failover","pgbouncer","postgresql","repmgr"],"articleSection":["portada","PostgreSQL"],"inLanguage":"es","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\/#respond"]}]},{"@type":"WebPage","@id":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\/","url":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\/","name":"Failover auto - Pgbouncer + Repmgr + Postgresql 13 (parte 1) - Arumel","isPartOf":{"@id":"http:\/\/arumel.com\/#website"},"primaryImageOfPage":{"@id":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\/#primaryimage"},"image":{"@id":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\/#primaryimage"},"thumbnailUrl":"http:\/\/arumel.com\/wp-content\/uploads\/2021\/01\/pgbouncer-repmgr-auto-285x300.png","datePublished":"2021-01-12T12:48:30+00:00","author":{"@id":"http:\/\/arumel.com\/#\/schema\/person\/e270e777d900dcd47f8eb3895c076b64"},"breadcrumb":{"@id":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\/#breadcrumb"},"inLanguage":"es","potentialAction":[{"@type":"ReadAction","target":["http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\/"]}]},{"@type":"ImageObject","inLanguage":"es","@id":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\/#primaryimage","url":"http:\/\/arumel.com\/wp-content\/uploads\/2021\/01\/pgbouncer-repmgr-auto-285x300.png","contentUrl":"http:\/\/arumel.com\/wp-content\/uploads\/2021\/01\/pgbouncer-repmgr-auto-285x300.png"},{"@type":"BreadcrumbList","@id":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Portada","item":"https:\/\/arumel.com\/es\/"},{"@type":"ListItem","position":2,"name":"Failover auto – Pgbouncer + Repmgr + Postgresql 13 (parte 1)"}]},{"@type":"WebSite","@id":"http:\/\/arumel.com\/#website","url":"http:\/\/arumel.com\/","name":"Arumel","description":"Outro sitio WordPress m\u00e1is","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"http:\/\/arumel.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"es"},{"@type":"Person","@id":"http:\/\/arumel.com\/#\/schema\/person\/e270e777d900dcd47f8eb3895c076b64","name":"sm","image":{"@type":"ImageObject","inLanguage":"es","@id":"https:\/\/secure.gravatar.com\/avatar\/6207cd8b9baaee6c4cff92251bb20e4b48ce165f93e926218da90832d9f334f9?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/6207cd8b9baaee6c4cff92251bb20e4b48ce165f93e926218da90832d9f334f9?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/6207cd8b9baaee6c4cff92251bb20e4b48ce165f93e926218da90832d9f334f9?s=96&d=mm&r=g","caption":"sm"},"url":"https:\/\/arumel.com\/es\/author\/sergio\/"}]}},"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p9uvW6-2CR","jetpack_likes_enabled":true,"jetpack-related-posts":[{"id":10110,"url":"https:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-2\/","url_meta":{"origin":10097,"position":0},"title":"Failover auto – Pgbouncer + Repmgr + Postgresql 13 (parte 2)","author":"sm","date":"12 de enero de 2021","format":false,"excerpt":"Ver parte 1. Ahora vamos a probar como el pgbouncer puede dirigirnos nuestras sesiones al nodo r\/w (primary) o a los r\/o (secondary). En nuestro caso el primary es el nodo postgres2 y los secondary son el postgres1 y postgres3. Se pueden tener configuradas diferentes entradas en el fichero \/etc\/pgbouncer\/pgbouncer.database.ini\u2026","rel":"","context":"En "PostgreSQL"","block_context":{"text":"PostgreSQL","link":"https:\/\/arumel.com\/es\/postgresql-es\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/arumel.com\/wp-content\/uploads\/2021\/01\/pgbouncer-repmgr-auto-285x300.png?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":10119,"url":"https:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\/","url_meta":{"origin":10097,"position":1},"title":"Failover auto – Pgbouncer + Repmgr + Postgresql 13 (parte 4)","author":"sm","date":"12 de enero de 2021","format":false,"excerpt":"Ver parte 1 Ver parte 2 Ver parte 3 Vamos a hacer una prueba de balanceo autom\u00e1tico tras la p\u00e9rdida del nodo primario (postgres2) y como balancea el failover a un nodo secundario (postgres1), tras la parada de la conexiones en el pgbouncer, posterior reconfiguraci\u00f3n, y conexi\u00f3n posterior al nuevo\u2026","rel":"","context":"En "portada"","block_context":{"text":"portada","link":"https:\/\/arumel.com\/es\/portada-es\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/arumel.com\/wp-content\/uploads\/2021\/01\/pgbouncer-repmgr-auto-285x300.png?resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/arumel.com\/wp-content\/uploads\/2021\/01\/pgbouncer-repmgr-auto-285x300.png?resize=350%2C200 1x, https:\/\/i0.wp.com\/arumel.com\/wp-content\/uploads\/2021\/01\/pgbouncer-repmgr-auto-285x300.png?resize=525%2C300 1.5x"},"classes":[]},{"id":10115,"url":"https:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-3\/","url_meta":{"origin":10097,"position":2},"title":"Failover auto – Pgbouncer + Repmgr + Postgresql 13 (parte 3)","author":"sm","date":"12 de enero de 2021","format":false,"excerpt":"Ver parte 1 Ver parte 2 Vamos a ver las diferentes opciones que tenemos en el base de datos virtual de pgbouncer. [postgres@postgres4 ~]$ psql --host=192.168.0.104 --username=postgres --port=6432 --dbname=pgbouncer 192.168.0.104:6432; postgres@pgbouncer # SHOW HELP; NOTICE: Console usage DETAIL: SHOW HELP|CONFIG|DATABASES|POOLS|CLIENTS|SERVERS|USERS|VERSION SHOW FDS|SOCKETS|ACTIVE_SOCKETS|LISTS|MEM SHOW DNS_HOSTS|DNS_ZONES SHOW STATS|STATS_TOTALS|STATS_AVERAGES|TOTALS SET key = arg\u2026","rel":"","context":"En "PostgreSQL"","block_context":{"text":"PostgreSQL","link":"https:\/\/arumel.com\/es\/postgresql-es\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/arumel.com\/wp-content\/uploads\/2021\/01\/pgbouncer-repmgr-auto-285x300.png?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":10067,"url":"https:\/\/arumel.com\/es\/auto-failover-repmgr-y-postgresql-13-parte-1\/","url_meta":{"origin":10097,"position":3},"title":"Auto failover – Repmgr y Postgresql 13 (parte 1)","author":"sm","date":"12 de enero de 2021","format":false,"excerpt":"Si repasamos las entradas anteriores Parte1 y Parte2, vemos que tenemos configurado el repmgr pero no hemos activado el demonio para que haga el chequeo continuo. Para ello necesitamos activar el servicio a nivel de SO y cargar su librer\u00eda en postgresql. En el fichero de postgresql.conf a\u00f1adimos la siguiente\u2026","rel":"","context":"En "portada"","block_context":{"text":"portada","link":"https:\/\/arumel.com\/es\/portada-es\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/arumel.com\/wp-content\/uploads\/2021\/01\/repmgr-auto-284x300.png?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":10087,"url":"https:\/\/arumel.com\/es\/auto-failover-repmgr-y-postgresql-13-parte-2\/","url_meta":{"origin":10097,"position":4},"title":"Auto failover – Repmgr y Postgresql 13 (parte 2)","author":"sm","date":"12 de enero de 2021","format":false,"excerpt":"Ver configuraci\u00f3n de la parte 1. El estado previo del cluster es el siguiente: [postgres@postgres1 ~]$ repmgr cluster show ID | Name | Role | Status | Upstream | Location | Priority | Timeline | Connection string ----+-------------------+---------+-----------+-----------+----------+----------+----------+---------------------------------------------- 1 | postgres1 | primary | * running | | default |\u2026","rel":"","context":"En "portada"","block_context":{"text":"portada","link":"https:\/\/arumel.com\/es\/portada-es\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/arumel.com\/wp-content\/uploads\/2021\/01\/repmgr-auto-284x300.png?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":9995,"url":"https:\/\/arumel.com\/es\/preparacion-entorno-repmgr-y-postgresql-13-parte-1\/","url_meta":{"origin":10097,"position":5},"title":"Preparaci\u00f3n entorno – Repmgr y Postgresql 13 (parte 1)","author":"sm","date":"12 de enero de 2021","format":false,"excerpt":"\u00a0 Nos disponemos a preparar un entorno sobre el que realizar pruebas con repmgr 13 (versi\u00f3n 5.2) y postgresql versi\u00f3n 13. En nuestro caso se tratar\u00e1 de un OEL 8.3 (con kernel de redhat). Una vez creada la primera m\u00e1quina virtual procedemos a la instalaci\u00f3n de los repositorios y desactivar\u2026","rel":"","context":"En "PostgreSQL"","block_context":{"text":"PostgreSQL","link":"https:\/\/arumel.com\/es\/postgresql-es\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/arumel.com\/wp-content\/uploads\/2021\/01\/repmgr-manual.png?resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/arumel.com\/wp-content\/uploads\/2021\/01\/repmgr-manual.png?resize=350%2C200 1x, https:\/\/i0.wp.com\/arumel.com\/wp-content\/uploads\/2021\/01\/repmgr-manual.png?resize=525%2C300 1.5x"},"classes":[]}],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/arumel.com\/es\/wp-json\/wp\/v2\/posts\/10097","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/arumel.com\/es\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/arumel.com\/es\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/arumel.com\/es\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/arumel.com\/es\/wp-json\/wp\/v2\/comments?post=10097"}],"version-history":[{"count":23,"href":"https:\/\/arumel.com\/es\/wp-json\/wp\/v2\/posts\/10097\/revisions"}],"predecessor-version":[{"id":10208,"href":"https:\/\/arumel.com\/es\/wp-json\/wp\/v2\/posts\/10097\/revisions\/10208"}],"wp:attachment":[{"href":"https:\/\/arumel.com\/es\/wp-json\/wp\/v2\/media?parent=10097"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/arumel.com\/es\/wp-json\/wp\/v2\/categories?post=10097"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/arumel.com\/es\/wp-json\/wp\/v2\/tags?post=10097"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}