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

Si repasamos las entradas anteriores Parte1<\/a> y Parte2<\/a>, vemos que tenemos configurado el repmgr pero no hemos activado el demonio para que haga el chequeo continuo.<\/p>\n

Para ello necesitamos activar el servicio a nivel de SO y cargar su librer\u00eda en postgresql.<\/p>\n

En el fichero de postgresql.conf<\/strong> a\u00f1adimos la siguiente entrada, en todos los nodos, y lo reiniciamos:<\/p>\n

shared_preload_libraries = 'repmgr'<\/code><\/strong><\/p>\n

[postgres@postgres1 ~]$ pg_ctl -D \/var\/lib\/pgsql\/13\/data reload<\/code>
\nserver signaled<\/code><\/p>\n

 <\/p>\n

Adem\u00e1s, en este ejemplo, vamos a configurar un testigo ajeno a los propios servidores que dirigir\u00e1 las operaciones.<\/p>\n

\"\"<\/p>\n

Activamos el demonio del repmgr en el SO de todos los nodos:<\/p>\n

[root@postgres1 ~]# systemctl enable repmgr13<\/strong><\/code>
\nCreated symlink \/etc\/systemd\/system\/multi-user.target.wants\/repmgr13.service \u2192 \/usr\/lib\/systemd\/system\/repmgr13.service.<\/code><\/p>\n

[root@postgres1 ~]# systemctl start repmgr13<\/strong><\/code><\/p>\n

[root@postgres1 ~]# systemctl status repmgr13<\/strong><\/code>
\n\u25cf repmgr13.service - A replication manager, and failover management tool for PostgreSQL<\/code>
\nLoaded: loaded (\/usr\/lib\/systemd\/system\/repmgr13.service; enabled; vendor preset: disabled)<\/code>
\nActive: active (running) since Fri 2021-01-08 13:21:28 CET; 4s ago<\/code>
\nProcess: 1541 ExecStart=\/usr\/pgsql-13\/bin\/repmgrd -f ${REPMGRDCONF} -p ${PIDFILE} -d --verbose (code=exited, status=0\/SUCCESS)<\/code>
\nMain PID: 1547 (repmgrd)<\/code>
\nTasks: 1 (limit: 5967)<\/code>
\nMemory: 1.5M<\/code>
\nCGroup: \/system.slice\/repmgr13.service<\/code>
\n\u2514\u25001547 \/usr\/pgsql-13\/bin\/repmgrd -f \/etc\/repmgr\/13\/repmgr.conf -p \/var\/run\/repmgr\/repmgrd-13.pid -d --verbose<\/code><\/p>\n

ene 08 13:21:28 postgres1 systemd[1]: Starting A replication manager, and failover management tool for PostgreSQL...<\/code>
\nene 08 13:21:28 postgres1 repmgrd[1541]: [2021-01-08 13:21:28] [NOTICE] using provided configuration file \"\/etc\/repmgr\/13\/repmgr.conf\"<\/code>
\nene 08 13:21:28 postgres1 repmgrd[1541]: [2021-01-08 13:21:28] [NOTICE] redirecting logging output to \"\/var\/lib\/pgsql\/13\/repmgr.log\"<\/code>
\nene 08 13:21:28 postgres1 systemd[1]: repmgr13.service: Can't open PID file \/var\/run\/repmgr\/repmgrd-13.pid (yet?) after start: No such file or directory<\/code>
\nene 08 13:21:28 postgres1 systemd[1]: Started A replication manager, and failover management tool for PostgreSQL.<\/code><\/p>\n

[postgres@postgres1 ~]$ repmgr daemon status<\/strong><\/code>
\nID | Name | Role | Status | Upstream | repmgrd | PID | Paused? | Upstream last seen<\/code>
\n----+-----------+---------+-----------+-----------+-------------+------+---------+--------------------<\/code>
\n1 | postgres1 | primary | * running | | running | 1547 | no | n\/a <\/code>
\n2 | postgres2 | standby | running | postgres1 | not running | n\/a | n\/a | n\/a <\/code>
\n3 | postgres3 | standby | running | postgres1 | not running | n\/a | n\/a | n\/a<\/code><\/p>\n

 <\/p>\n

Se podr\u00eda cambiar la prioridad de cada servidor en el fichero \/etc\/repmgr\/13\/repmgr.conf y as\u00ed prevalecer unos servidores ante otros, en caso de failover (server1–>priority=80, server2–>priority=60, server3–>priority=40).<\/p>\n

A\u00f1adimos las siguientes entradas al fichero \/etc\/repmgr\/13\/repmgr.conf<\/strong>:<\/p>\n

failover='automatic'<\/code>
\nrepmgrd_service_start_command='sudo \/bin\/systemctl start repmgr13'<\/code>
\nrepmgrd_service_stop_command='sudo \/bin\/systemctl stop repmgr13'<\/code>
\nstandby_disconnect_on_failover=true<\/code>
\nmonitoring_history=yes<\/code>
\nlog_status_interval=60<\/code><\/p>\n

 <\/p>\n

Reiniciamos el demonio del repmgr en todos los nodos:<\/p>\n

[postgres@postgres1 ~]$ repmgr daemon stop<\/strong><\/code>
\nNOTICE: executing: \"sudo \/bin\/systemctl stop repmgr13\"<\/code>
\nNOTICE: repmgrd was successfully stopped<\/code>
\n[postgres@postgres1 ~]$ repmgr daemon start<\/strong><\/code>
\nNOTICE: executing: \"sudo \/bin\/systemctl start repmgr13\"<\/code>
\nNOTICE: repmgrd was successfully started<\/code><\/p>\n

 <\/p>\n

Y comprobamos su estado:<\/p>\n

[postgres@postgres1 ~]$ repmgr service status<\/strong><\/code>
\nID | Name | Role | Status | Upstream | repmgrd | PID | Paused? | Upstream last seen<\/code>
\n----+-----------+---------+-----------+-----------+---------+------+---------+--------------------<\/code>
\n1 | postgres1 | primary | * running | | running | 3321 | no | n\/a <\/code>
\n2 | postgres2 | standby | running | postgres1 | running | 2241 | no | 0 second(s) ago <\/code>
\n3 | postgres3 | standby | running | postgres1 | running | 2050 | no | 1 second(s) ago<\/code><\/p>\n

 <\/p>\n

En el nodo \u00abtestigo\u00bb (postgres4), inicializamos postgres y creamos su base de datos para repmgr:<\/p>\n

[root@postgres4 ~]# \/usr\/pgsql-13\/bin\/postgresql-13-setup initdb<\/strong><\/code>
\nInitializing database ... OK<\/code><\/p>\n

[root@postgres4 ~]# systemctl start postgresql-13<\/strong><\/code><\/p>\n

[postgres@postgres4 ~]$ psql -c 'CREATE USER repmgr WITH REPLICATION SUPERUSER LOGIN';<\/strong><\/code>
\nCREATE ROLE<\/code>
\n[postgres@postgres4 ~]$ psql -c 'CREATE DATABASE repmgr OWNER repmgr';<\/strong><\/code>
\nCREATE DATABASE<\/code>
\n[postgres@postgres4 ~]$ psql -c 'ALTER USER repmgr SET search_path TO repmgr, \"$user\", public';<\/strong><\/code>
\nALTER ROLE<\/code><\/p>\n

 <\/p>\n

Registramos el nodo \u00abtestigo\u00bb en el cluster contra el primary (postgres1):<\/p>\n

[postgres@postgres4 ~]$ repmgr witness register -h 192.168.0.101<\/strong><\/code>
\nINFO: connecting to witness node \"postgres4-witness\" (ID: 4)<\/code>
\nINFO: connecting to primary node<\/code>
\nNOTICE: attempting to install extension \"repmgr\"<\/code>
\nNOTICE: \"repmgr\" extension successfully installed<\/code>
\nINFO: witness registration complete<\/code>
\nNOTICE: witness node \"postgres4-witness\" (ID: 4) successfully registered<\/code><\/p>\n

 <\/p>\n

Y el cluster queda de la siguiente manera:<\/p>\n

[postgres@postgres1 ~]$ repmgr cluster show<\/strong><\/code>
\nID | Name | Role | Status | Upstream | Location | Priority | Timeline | Connection string <\/code>
\n----+-------------------+---------+-----------+-----------+----------+----------+----------+----------------------------------------------<\/code>
\n1 | postgres1 | primary | * running | | default | 100 | 3 | host=192.168.0.101 user=repmgr dbname=repmgr<\/code>
\n2 | postgres2 | standby | running | postgres1 | default | 100 | 3 | host=192.168.0.102 user=repmgr dbname=repmgr<\/code>
\n3 | postgres3 | standby | running | postgres1 | default | 100 | 3 | 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<\/strong><\/code><\/p>\n

 <\/p>\n

Ahora vamos a la parte 2…<\/p>\n

 <\/p>\n

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

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 entrada, en todos los nodos, […]<\/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,434,433],"class_list":["post-10067","post","type-post","status-publish","format-standard","hentry","category-portada-es","category-postgresql-es","tag-auto","tag-failover","tag-postgresql","tag-repmgr"],"yoast_head":"\nAuto failover - Repmgr y 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\/auto-failover-repmgr-y-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=\"Auto failover - Repmgr y Postgresql 13 (parte 1) - Arumel\" \/>\n<meta property=\"og:description\" content=\"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 entrada, en todos los nodos, […]\" \/>\n<meta property=\"og:url\" content=\"http:\/\/arumel.com\/es\/auto-failover-repmgr-y-postgresql-13-parte-1\/\" \/>\n<meta property=\"og:site_name\" content=\"Arumel\" \/>\n<meta property=\"article:published_time\" content=\"2021-01-12T12:31:42+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/arumel.com\/wp-content\/uploads\/2021\/01\/repmgr-auto-284x300.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\\\/auto-failover-repmgr-y-postgresql-13-parte-1\\\/#article\",\"isPartOf\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/auto-failover-repmgr-y-postgresql-13-parte-1\\\/\"},\"author\":{\"name\":\"sm\",\"@id\":\"http:\\\/\\\/arumel.com\\\/#\\\/schema\\\/person\\\/e270e777d900dcd47f8eb3895c076b64\"},\"headline\":\"Auto failover – Repmgr y Postgresql 13 (parte 1)\",\"datePublished\":\"2021-01-12T12:31:42+00:00\",\"mainEntityOfPage\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/auto-failover-repmgr-y-postgresql-13-parte-1\\\/\"},\"wordCount\":211,\"commentCount\":0,\"image\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/auto-failover-repmgr-y-postgresql-13-parte-1\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/arumel.com\\\/wp-content\\\/uploads\\\/2021\\\/01\\\/repmgr-auto-284x300.png\",\"keywords\":[\"auto\",\"failover\",\"postgresql\",\"repmgr\"],\"articleSection\":[\"portada\",\"PostgreSQL\"],\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"http:\\\/\\\/arumel.com\\\/es\\\/auto-failover-repmgr-y-postgresql-13-parte-1\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/auto-failover-repmgr-y-postgresql-13-parte-1\\\/\",\"url\":\"http:\\\/\\\/arumel.com\\\/es\\\/auto-failover-repmgr-y-postgresql-13-parte-1\\\/\",\"name\":\"Auto failover - Repmgr y Postgresql 13 (parte 1) - Arumel\",\"isPartOf\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/auto-failover-repmgr-y-postgresql-13-parte-1\\\/#primaryimage\"},\"image\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/auto-failover-repmgr-y-postgresql-13-parte-1\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/arumel.com\\\/wp-content\\\/uploads\\\/2021\\\/01\\\/repmgr-auto-284x300.png\",\"datePublished\":\"2021-01-12T12:31:42+00:00\",\"author\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/#\\\/schema\\\/person\\\/e270e777d900dcd47f8eb3895c076b64\"},\"breadcrumb\":{\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/auto-failover-repmgr-y-postgresql-13-parte-1\\\/#breadcrumb\"},\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"http:\\\/\\\/arumel.com\\\/es\\\/auto-failover-repmgr-y-postgresql-13-parte-1\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/auto-failover-repmgr-y-postgresql-13-parte-1\\\/#primaryimage\",\"url\":\"http:\\\/\\\/arumel.com\\\/wp-content\\\/uploads\\\/2021\\\/01\\\/repmgr-auto-284x300.png\",\"contentUrl\":\"http:\\\/\\\/arumel.com\\\/wp-content\\\/uploads\\\/2021\\\/01\\\/repmgr-auto-284x300.png\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"http:\\\/\\\/arumel.com\\\/es\\\/auto-failover-repmgr-y-postgresql-13-parte-1\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Portada\",\"item\":\"https:\\\/\\\/arumel.com\\\/es\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Auto failover – Repmgr y 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":"Auto failover - Repmgr y 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\/auto-failover-repmgr-y-postgresql-13-parte-1\/","og_locale":"es_ES","og_type":"article","og_title":"Auto failover - Repmgr y Postgresql 13 (parte 1) - Arumel","og_description":"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 entrada, en todos los nodos, […]","og_url":"http:\/\/arumel.com\/es\/auto-failover-repmgr-y-postgresql-13-parte-1\/","og_site_name":"Arumel","article_published_time":"2021-01-12T12:31:42+00:00","og_image":[{"url":"http:\/\/arumel.com\/wp-content\/uploads\/2021\/01\/repmgr-auto-284x300.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\/auto-failover-repmgr-y-postgresql-13-parte-1\/#article","isPartOf":{"@id":"http:\/\/arumel.com\/es\/auto-failover-repmgr-y-postgresql-13-parte-1\/"},"author":{"name":"sm","@id":"http:\/\/arumel.com\/#\/schema\/person\/e270e777d900dcd47f8eb3895c076b64"},"headline":"Auto failover – Repmgr y Postgresql 13 (parte 1)","datePublished":"2021-01-12T12:31:42+00:00","mainEntityOfPage":{"@id":"http:\/\/arumel.com\/es\/auto-failover-repmgr-y-postgresql-13-parte-1\/"},"wordCount":211,"commentCount":0,"image":{"@id":"http:\/\/arumel.com\/es\/auto-failover-repmgr-y-postgresql-13-parte-1\/#primaryimage"},"thumbnailUrl":"http:\/\/arumel.com\/wp-content\/uploads\/2021\/01\/repmgr-auto-284x300.png","keywords":["auto","failover","postgresql","repmgr"],"articleSection":["portada","PostgreSQL"],"inLanguage":"es","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["http:\/\/arumel.com\/es\/auto-failover-repmgr-y-postgresql-13-parte-1\/#respond"]}]},{"@type":"WebPage","@id":"http:\/\/arumel.com\/es\/auto-failover-repmgr-y-postgresql-13-parte-1\/","url":"http:\/\/arumel.com\/es\/auto-failover-repmgr-y-postgresql-13-parte-1\/","name":"Auto failover - Repmgr y Postgresql 13 (parte 1) - Arumel","isPartOf":{"@id":"http:\/\/arumel.com\/#website"},"primaryImageOfPage":{"@id":"http:\/\/arumel.com\/es\/auto-failover-repmgr-y-postgresql-13-parte-1\/#primaryimage"},"image":{"@id":"http:\/\/arumel.com\/es\/auto-failover-repmgr-y-postgresql-13-parte-1\/#primaryimage"},"thumbnailUrl":"http:\/\/arumel.com\/wp-content\/uploads\/2021\/01\/repmgr-auto-284x300.png","datePublished":"2021-01-12T12:31:42+00:00","author":{"@id":"http:\/\/arumel.com\/#\/schema\/person\/e270e777d900dcd47f8eb3895c076b64"},"breadcrumb":{"@id":"http:\/\/arumel.com\/es\/auto-failover-repmgr-y-postgresql-13-parte-1\/#breadcrumb"},"inLanguage":"es","potentialAction":[{"@type":"ReadAction","target":["http:\/\/arumel.com\/es\/auto-failover-repmgr-y-postgresql-13-parte-1\/"]}]},{"@type":"ImageObject","inLanguage":"es","@id":"http:\/\/arumel.com\/es\/auto-failover-repmgr-y-postgresql-13-parte-1\/#primaryimage","url":"http:\/\/arumel.com\/wp-content\/uploads\/2021\/01\/repmgr-auto-284x300.png","contentUrl":"http:\/\/arumel.com\/wp-content\/uploads\/2021\/01\/repmgr-auto-284x300.png"},{"@type":"BreadcrumbList","@id":"http:\/\/arumel.com\/es\/auto-failover-repmgr-y-postgresql-13-parte-1\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Portada","item":"https:\/\/arumel.com\/es\/"},{"@type":"ListItem","position":2,"name":"Auto failover – Repmgr y 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-2Cn","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":10067,"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":10119,"url":"https:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-4\/","url_meta":{"origin":10067,"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":10110,"url":"https:\/\/arumel.com\/es\/failover-auto-pgbouncer-repmgr-postgresql-13-parte-2\/","url_meta":{"origin":10067,"position":2},"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":9995,"url":"https:\/\/arumel.com\/es\/preparacion-entorno-repmgr-y-postgresql-13-parte-1\/","url_meta":{"origin":10067,"position":3},"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":[]},{"id":10087,"url":"https:\/\/arumel.com\/es\/auto-failover-repmgr-y-postgresql-13-parte-2\/","url_meta":{"origin":10067,"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":10040,"url":"https:\/\/arumel.com\/es\/preparacion-entorno-repmgr-y-postgresql-13-parte-2\/","url_meta":{"origin":10067,"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\/10067","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=10067"}],"version-history":[{"count":17,"href":"https:\/\/arumel.com\/es\/wp-json\/wp\/v2\/posts\/10067\/revisions"}],"predecessor-version":[{"id":10190,"href":"https:\/\/arumel.com\/es\/wp-json\/wp\/v2\/posts\/10067\/revisions\/10190"}],"wp:attachment":[{"href":"https:\/\/arumel.com\/es\/wp-json\/wp\/v2\/media?parent=10067"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/arumel.com\/es\/wp-json\/wp\/v2\/categories?post=10067"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/arumel.com\/es\/wp-json\/wp\/v2\/tags?post=10067"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}