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

\"\"<\/p>\n

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

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

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

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 primario (postgres1).<\/p>\n

Estado previo del cluster:<\/p>\n

[postgres@postgres4 ~]$ repmgr cluster show<\/strong><\/code>
\nID | Name | Role | Status | Upstream | Location | Priority | Timeline | Connection string <\/code>
\n----+-------------------+---------+-----------+-----------+----------+----------+----------+----------------------------------------------<\/code>
\n1 | postgres1 | standby | running | postgres2 | default | 100 | 9 | host=192.168.0.101 user=repmgr dbname=repmgr<\/code>
\n2 | postgres2 | primary | * running | | default | 100 | 10 | host=192.168.0.102 user=repmgr dbname=repmgr<\/strong><\/code>
\n3 | postgres3 | standby | running | postgres2 | default | 100 | 10 | host=192.168.0.103 user=repmgr dbname=repmgr<\/code>
\n4 | postgres4-witness | witness | * running | postgres2 | default | 0 | n\/a | host=192.168.0.104 user=repmgr dbname=repmgr<\/code><\/p>\n

 <\/p>\n

Desde una conexi\u00f3n cliente nos conectamos para comprobar la ip a la que nos ha conectado el pgbouncer (y no cerraremos la conexi\u00f3n para ver el balanceo autom\u00e1tico tras el fallo del primary):<\/p>\n

[postgres@postgres4 ~]$ psql 'host=192.168.0.104 user=appdb port=6432'<\/code>
\npsql (13.1)<\/code>
\nType \"help\" for help.<\/code><\/p>\n

appdb=> select inet_server_addr(), inet_server_port();<\/code>
\ninet_server_addr | inet_server_port <\/code>
\n------------------+------------------<\/code>
\n192.168.0.102<\/strong> | 5432<\/code>
\n(1 row)<\/code><\/p>\n

 <\/p>\n

Desde el pgbouncer vemos las conexiones a las bases de datos y lo monitorizaremos cada 5 segundos:<\/p>\n

[postgres@postgres4 ~]$ psql --host=192.168.0.104 --username=postgres --port=6432 --dbname=pgbouncer<\/strong><\/code>
\npsql (13.1, server 1.15.0\/bouncer)<\/code>
\nType \"help\" for help.<\/code><\/p>\n

pgbouncer=# show databases;<\/strong><\/code>
\nname | host | port | database | force_user | pool_size | reserve_pool | pool_mode | max_connections | current_connections | paused | disabled <\/code>
\n-----------+-----------+------+-----------+------------+-----------+--------------+-----------+-----------------+---------------------+--------+----------<\/code>
\nappdb | postgres2 | 5432 | appdb | | 20 | 5 | | 0 | 5 | 0 | 0<\/strong><\/code>
\npgbouncer | | 6432 | pgbouncer | pgbouncer | 2 | 0 | statement | 0 | 0 | 0 | 0<\/code>
\n(2 rows)<\/code><\/p>\n

pgbouncer=# \\watch 5<\/strong>;<\/code><\/p>\n

 <\/p>\n

Provocamos el fallo (simulado) en el nodo primario (postgres2):<\/p>\n

[postgres@postgres2<\/strong> ~]$ sudo systemctl stop postgresql-13<\/strong><\/code><\/p>\n

 <\/p>\n

Vemos el estado del cluster:<\/p>\n

[postgres@postgres4 ~]$ repmgr cluster show<\/code>
\nID | Name | Role | Status | Upstream | Location | Priority | Timeline | Connection string <\/code>
\n----+-------------------+---------+-----------+-----------+----------+----------+----------+----------------------------------------------<\/code>
\n1 | postgres1 | primary | * running | | default | 100 | 11 | host=192.168.0.101 user=repmgr dbname=repmgr<\/code>
\n2 | postgres2 | primary | - failed | ? | default | 100 | | host=192.168.0.102 user=repmgr dbname=repmgr<\/strong><\/code>
\n3 | postgres3 | standby | running | postgres1 | default | 100 | 10 | host=192.168.0.103 user=repmgr dbname=repmgr<\/code>
\n4 | postgres4-witness | witness | * running | postgres1 | default | 0 | n\/a | host=192.168.0.104 user=repmgr dbname=repmgr<\/code><\/p>\n

WARNING: following issues were detected<\/code>
\n- unable to connect to node \"postgres2\" (ID: 2)<\/code><\/p>\n

HINT: execute with --verbose option to see connection error messages<\/code><\/p>\n

 <\/p>\n

Vemos la parada y arranque del pgbouncer en la select que ten\u00edamos ejecut\u00e1ndose cada 5 segundos:<\/p>\n

Sat 09 Jan 2021 06:31:05 PM CET (every 5s)<\/code><\/p>\n

name | host | port | database | force_user | pool_size | reserve_pool | pool_mode | max_connections | current_connections | paused<\/strong> | disabled <\/code>
\n-----------+-----------+------+-----------+------------+-----------+--------------+-----------+-----------------+---------------------+--------+----------<\/code>
\nappdb | postgres2 | 5432 | appdb | | 20 | 5 | | 0 | 0 | 1<\/strong> | 0<\/code>
\npgbouncer | | 6432 | pgbouncer | pgbouncer | 2 | 0 | statement | 0 | 0 | 0 | 0<\/code>
\n(2 rows)<\/code><\/p>\n

Sat 09 Jan 2021 06:31:10 PM CET (every 5s)<\/code><\/p>\n

name | host | port | database | force_user | pool_size | reserve_pool | pool_mode | max_connections | current_connections | paused<\/strong> | disabled <\/code>
\n-----------+-----------+------+-----------+------------+-----------+--------------+-----------+-----------------+---------------------+--------+----------<\/code>
\nappdb | postgres1 | 5432 | appdb | | 20 | 5 | | 0 | 0 | 0<\/strong> | 0<\/code>
\npgbouncer | | 6432 | pgbouncer | pgbouncer | 2 | 0 | statement | 0 | 0 | 0 | 0<\/code>
\n(2 rows)<\/code><\/p>\n

 <\/p>\n

Comprobamos tambi\u00e9n desde nuestra conexi\u00f3n cliente a la base de datos primary (postgres2) como ha cambiado a la nueva primary (postgres1):<\/p>\n

appdb=> select inet_server_addr(), inet_server_port();<\/code>
\ninet_server_addr | inet_server_port <\/code>
\n------------------+------------------<\/code>
\n192.168.0.101<\/strong> | 5432<\/code>
\n(1 row)<\/code><\/p>\n

 <\/p>\n

Una vez recuperado el fallo (provocado por nosotros) que hizo este failover autom\u00e1tico, si queremos unir el antiguo primary al cluster, ser\u00eda:<\/p>\n

[postgres@postgres2 ~]$ repmgr -d 'host=192.168.0.101 user=repmgr dbname=repmgr' node rejoin --force-rewind<\/strong><\/code>
\nNOTICE: executing pg_rewind<\/code>
\nDETAIL: pg_rewind command is \"\/usr\/pgsql-13\/bin\/pg_rewind -D '\/var\/lib\/pgsql\/13\/data' --source-server='host=192.168.0.101 user=repmgr dbname=repmgr'\"<\/code>
\nNOTICE: 0 files copied to \/var\/lib\/pgsql\/13\/data<\/code>
\nINFO: creating replication slot as user \"repmgr\"<\/code>
\nNOTICE: setting node 2's upstream to node 1<\/code>
\nWARNING: unable to ping \"host=192.168.0.102 user=repmgr dbname=repmgr\"<\/code>
\nDETAIL: PQping() returned \"PQPING_NO_RESPONSE\"<\/code>
\nNOTICE: starting server using \"sudo \/bin\/systemctl start postgresql-13\"<\/code>
\nWARNING: node \"postgres2\" attached in state \"startup\"<\/code>
\nINFO: waiting for node \"postgres2\" (ID: 2) to connect to new primary; 1 of max 60 attempts (parameter \"node_rejoin_timeout\")<\/code>
\nDETAIL: node \"postgres1\" (ID: 2) is currrently attached to its upstream node in state \"startup\"<\/code>
\nNOTICE: NODE REJOIN successful<\/code>
\nDETAIL: node 2 is now attached to node 1<\/code><\/p>\n

 <\/p>\n

El estado final del cluster ser\u00eda:<\/p>\n

[postgres@postgres4 ~]$ repmgr cluster show<\/code>
\nID | Name | Role | Status | Upstream | Location | Priority | Timeline | Connection string <\/code>
\n----+-------------------+---------+-----------+-----------+----------+----------+----------+----------------------------------------------<\/code>
\n1 | postgres1 | primary | * running | | default | 100 | 11 | host=192.168.0.101 user=repmgr dbname=repmgr<\/code>
\n2 | postgres2 | standby | running | postgres1 | default | 100 | 10 | host=192.168.0.102 user=repmgr dbname=repmgr<\/code>
\n3 | postgres3 | standby | running | postgres1 | default | 100 | 10 | host=192.168.0.103 user=repmgr dbname=repmgr<\/code>
\n4 | postgres4-witness | witness | * running | postgres1 | default | 0 | n\/a | host=192.168.0.104 user=repmgr dbname=repmgr<\/code><\/p>\n

 <\/p>\n

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

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 primario (postgres1). Estado previo del […]<\/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-10119","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 4) - 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-4\/\" \/>\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 4) - Arumel\" \/>\n<meta property=\"og:description\" content=\"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 primario (postgres1). Estado previo del […]\" \/>\n<meta property=\"og:url\" content=\"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\/\" \/>\n<meta property=\"og:site_name\" content=\"Arumel\" \/>\n<meta property=\"article:published_time\" content=\"2021-01-12T13:05:24+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=\"4 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-4\\\/#article\",\"isPartOf\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\\\/\"},\"author\":{\"name\":\"sm\",\"@id\":\"http:\\\/\\\/arumel.com\\\/#\\\/schema\\\/person\\\/e270e777d900dcd47f8eb3895c076b64\"},\"headline\":\"Failover auto – Pgbouncer + Repmgr + Postgresql 13 (parte 4)\",\"datePublished\":\"2021-01-12T13:05:24+00:00\",\"mainEntityOfPage\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\\\/\"},\"wordCount\":211,\"commentCount\":0,\"image\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\\\/#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-4\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\\\/\",\"url\":\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\\\/\",\"name\":\"Failover auto - Pgbouncer + Repmgr + Postgresql 13 (parte 4) - Arumel\",\"isPartOf\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\\\/#primaryimage\"},\"image\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/arumel.com\\\/wp-content\\\/uploads\\\/2021\\\/01\\\/pgbouncer-repmgr-auto-285x300.png\",\"datePublished\":\"2021-01-12T13:05:24+00:00\",\"author\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/#\\\/schema\\\/person\\\/e270e777d900dcd47f8eb3895c076b64\"},\"breadcrumb\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\\\/#breadcrumb\"},\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\\\/#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-4\\\/#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 4)\"}]},{\"@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 4) - 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-4\/","og_locale":"es_ES","og_type":"article","og_title":"Failover auto - Pgbouncer + Repmgr + Postgresql 13 (parte 4) - Arumel","og_description":"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 primario (postgres1). Estado previo del […]","og_url":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\/","og_site_name":"Arumel","article_published_time":"2021-01-12T13:05:24+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":"4 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\/#article","isPartOf":{"@id":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\/"},"author":{"name":"sm","@id":"http:\/\/arumel.com\/#\/schema\/person\/e270e777d900dcd47f8eb3895c076b64"},"headline":"Failover auto – Pgbouncer + Repmgr + Postgresql 13 (parte 4)","datePublished":"2021-01-12T13:05:24+00:00","mainEntityOfPage":{"@id":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\/"},"wordCount":211,"commentCount":0,"image":{"@id":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\/#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-4\/#respond"]}]},{"@type":"WebPage","@id":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\/","url":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\/","name":"Failover auto - Pgbouncer + Repmgr + Postgresql 13 (parte 4) - Arumel","isPartOf":{"@id":"http:\/\/arumel.com\/#website"},"primaryImageOfPage":{"@id":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\/#primaryimage"},"image":{"@id":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\/#primaryimage"},"thumbnailUrl":"http:\/\/arumel.com\/wp-content\/uploads\/2021\/01\/pgbouncer-repmgr-auto-285x300.png","datePublished":"2021-01-12T13:05:24+00:00","author":{"@id":"http:\/\/arumel.com\/#\/schema\/person\/e270e777d900dcd47f8eb3895c076b64"},"breadcrumb":{"@id":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\/#breadcrumb"},"inLanguage":"es","potentialAction":[{"@type":"ReadAction","target":["http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\/"]}]},{"@type":"ImageObject","inLanguage":"es","@id":"http:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\/#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-4\/#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 4)"}]},{"@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-2Dd","jetpack_likes_enabled":true,"jetpack-related-posts":[{"id":10097,"url":"https:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-1\/","url_meta":{"origin":10119,"position":0},"title":"Failover auto – Pgbouncer + Repmgr + Postgresql 13 (parte 1)","author":"sm","date":"12 de enero de 2021","format":false,"excerpt":"Ver configuraci\u00f3n parte 1 Ver configuraci\u00f3n parte 2 Ver configuraci\u00f3n parte 1 daemon repmgr Instalamos el pgbouncer en el nodo \"testigo\" (postgres4): [root@postgres4 ~]# dnf install pgbouncer \u00a0 Para hacer las pruebas de conexi\u00f3n de clientes, vamos a crear una nueva base de datos en el cluster (appdb) a la\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},"classes":[]},{"id":10110,"url":"https:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-2\/","url_meta":{"origin":10119,"position":1},"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":10087,"url":"https:\/\/arumel.com\/es\/auto-failover-repmgr-y-postgresql-13-parte-2\/","url_meta":{"origin":10119,"position":2},"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":10067,"url":"https:\/\/arumel.com\/es\/auto-failover-repmgr-y-postgresql-13-parte-1\/","url_meta":{"origin":10119,"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":10063,"url":"https:\/\/arumel.com\/es\/manual-failover-repmgr-y-postgresql-13\/","url_meta":{"origin":10119,"position":4},"title":"Manual failover – Repmgr y Postgresql 13","author":"sm","date":"12 de enero de 2021","format":false,"excerpt":"Ver configuraci\u00f3n parte 1. Ver configuraci\u00f3n parte 2. Ver switchover manual. Estado previo del cluster: [postgres@postgres1 ~]$ repmgr cluster show ID | Name | Role | Status | Upstream | Location | Priority | Timeline | Connection string ----+-----------+---------+-----------+-----------+----------+----------+----------+---------------------------------------------- 1 | postgres1 | standby | running | postgres2 | 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-manual-300x183.png?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":10040,"url":"https:\/\/arumel.com\/es\/preparacion-entorno-repmgr-y-postgresql-13-parte-2\/","url_meta":{"origin":10119,"position":5},"title":"Preparaci\u00f3n entorno – Repmgr y Postgresql 13 (parte 2)","author":"sm","date":"12 de enero de 2021","format":false,"excerpt":"Ver configuraci\u00f3n parte1 Registramos el primer nodo en el cluster: [postgres@postgres1 ~]$ repmgr primary register INFO: connecting to primary database... NOTICE: attempting to install extension \"repmgr\" NOTICE: \"repmgr\" extension successfully installed NOTICE: primary node record (ID: 1) registered \u00a0 Mostramos el estado del cluster: [postgres@postgres1 ~]$ repmgr cluster show ID\u2026","rel":"","context":"En "PostgreSQL"","block_context":{"text":"PostgreSQL","link":"https:\/\/arumel.com\/es\/postgresql-es\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/arumel.com\/es\/wp-json\/wp\/v2\/posts\/10119","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=10119"}],"version-history":[{"count":7,"href":"https:\/\/arumel.com\/es\/wp-json\/wp\/v2\/posts\/10119\/revisions"}],"predecessor-version":[{"id":10216,"href":"https:\/\/arumel.com\/es\/wp-json\/wp\/v2\/posts\/10119\/revisions\/10216"}],"wp:attachment":[{"href":"https:\/\/arumel.com\/es\/wp-json\/wp\/v2\/media?parent=10119"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/arumel.com\/es\/wp-json\/wp\/v2\/categories?post=10119"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/arumel.com\/es\/wp-json\/wp\/v2\/tags?post=10119"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}