{"id":4929,"date":"2018-04-02T19:53:06","date_gmt":"2018-04-03T02:53:06","guid":{"rendered":"https:\/\/www.couchbase.com\/blog\/?p=4929"},"modified":"2025-06-13T23:43:09","modified_gmt":"2025-06-14T06:43:09","slug":"auto-failover-features-couchbase-server-5-5-developer-build","status":"publish","type":"post","link":"https:\/\/www.couchbase.com\/blog\/pt\/auto-failover-features-couchbase-server-5-5-developer-build\/","title":{"rendered":"Recursos de Auto-FailOver no Couchbase Server 5.5"},"content":{"rendered":"<p><span style=\"font-weight: 400\">O Couchbase melhora ainda mais a alta disponibilidade para implementa\u00e7\u00f5es de miss\u00e3o cr\u00edtica e reduz a interven\u00e7\u00e3o do operador. O Couchbase aprimora a detec\u00e7\u00e3o de falhas comuns de disco e faz o failover autom\u00e1tico do n\u00f3 com discos defeituosos, economizando tempo e energia dos operadores. Ele tamb\u00e9m lida com v\u00e1rias falhas de servidor com base na contagem de r\u00e9plicas para evitar a perda de dados e pode fazer o failover de um grupo inteiro de servidores se um rack ou zona n\u00e3o estiver dispon\u00edvel.<\/span><\/p>\n<p><span style=\"font-weight: 400\">Os usu\u00e1rios agora podem configurar o failover autom\u00e1tico para disco, v\u00e1rios n\u00f3s e todo o grupo de servidores (rack-zone) em <a href=\"https:\/\/www.couchbase.com\/blog\/pt\/couchbase-server-5-5-beta-2\/\">Servidor Couchbase 5.5<\/a>.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-large wp-image-4932\" src=\"https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/2018\/04\/Screen-Shot-2018-04-01-at-2.29.09-PM-1024x502.png\" alt=\"\" width=\"900\" height=\"441\" srcset=\"https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2018\/04\/Screen-Shot-2018-04-01-at-2.29.09-PM-1024x502.png 1024w, https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2018\/04\/Screen-Shot-2018-04-01-at-2.29.09-PM-300x147.png 300w, https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2018\/04\/Screen-Shot-2018-04-01-at-2.29.09-PM-768x377.png 768w, https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2018\/04\/Screen-Shot-2018-04-01-at-2.29.09-PM-1536x753.png 1536w, https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2018\/04\/Screen-Shot-2018-04-01-at-2.29.09-PM-20x10.png 20w, https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2018\/04\/Screen-Shot-2018-04-01-at-2.29.09-PM-1320x647.png 1320w, https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2018\/04\/Screen-Shot-2018-04-01-at-2.29.09-PM.png 2048w\" sizes=\"auto, (max-width: 900px) 100vw, 900px\" \/><\/p>\n<p><span style=\"font-weight: 400\">Vamos dar uma olhada em cada um desses aprimoramentos em detalhes. \u00a0<\/span><\/p>\n<h2><span style=\"font-weight: 400\">Auto-FailOver em problemas de disco<\/span><\/h2>\n<p><span style=\"font-weight: 400\">Antes do Couchbase Server 5.5, o gerenciador de cluster n\u00e3o fazia failover automaticamente quando encontrava problemas relacionados ao disco em um n\u00f3. O n\u00f3 continuava a operar por algum tempo, at\u00e9 ficar sem mem\u00f3ria ou encontrar algum outro problema. <\/span><\/p>\n<p><span style=\"font-weight: 400\">No entanto, o gerenciador de cluster tem alertas integrados para \"<\/span><span style=\"font-weight: 400\">quando a falha do disco \u00e9 detectada durante a persist\u00eancia dos dados no disco\" e <\/span><span style=\"font-weight: 400\">\"O espa\u00e7o em disco usado para armazenamento persistente atingiu pelo menos 90% de capacidade\". \u00a0<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-4931\" src=\"https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/2018\/04\/Couchbase_Console_Enterprise_Edition_5_5_0_build_2036_-_Demo.png\" alt=\"\" width=\"843\" height=\"382\" srcset=\"https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2018\/04\/Couchbase_Console_Enterprise_Edition_5_5_0_build_2036_-_Demo.png 843w, https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2018\/04\/Couchbase_Console_Enterprise_Edition_5_5_0_build_2036_-_Demo-300x136.png 300w, https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2018\/04\/Couchbase_Console_Enterprise_Edition_5_5_0_build_2036_-_Demo-768x348.png 768w, https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2018\/04\/Couchbase_Console_Enterprise_Edition_5_5_0_build_2036_-_Demo-20x9.png 20w\" sizes=\"auto, (max-width: 843px) 100vw, 843px\" \/><\/p>\n<p><span style=\"font-weight: 400\">No Couchbase Server 5.5, os usu\u00e1rios poder\u00e3o definir as seguintes configura\u00e7\u00f5es nas Configura\u00e7\u00f5es de disponibilidade do n\u00f3 no Console da Web do Couchbase ou por meio da API CLI\/REST.<\/span><\/p>\n<ul>\n<li style=\"list-style-type: none\">\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Ativar o failover autom\u00e1tico para falhas cont\u00ednuas de leitura\/grava\u00e7\u00e3o no disco de dados <\/span>\n<ul>\n<li><span style=\"font-weight: 400\">Habilite o failover autom\u00e1tico do n\u00f3 para ativar esse recurso\u00a0<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Ele estar\u00e1 desativado por padr\u00e3o.<\/span><\/li>\n<\/ul>\n<\/li>\n<li><b><span style=\"font-weight: 400\">O per\u00edodo de tempo em segundos<\/span><\/b>\n<ul>\n<li>O m\u00ednimo pode ser definido como 5 segundos, o m\u00e1ximo como 3600 segundos e o padr\u00e3o \u00e9 120 segundos.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2><span style=\"font-weight: 400\">Como isso funciona?<\/span><\/h2>\n<p><span style=\"font-weight: 400\">O gerenciador de cluster do Couchbase continua monitorando duas estat\u00edsticas <\/span><\/p>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">N\u00famero de falhas ao tentar gravar itens no disco.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">N\u00famero de falhas durante a tentativa de leitura de um disco.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400\">Se essa estat\u00edstica continuar a aumentar durante o tempo limite do failover autom\u00e1tico e a op\u00e7\u00e3o \"failover autom\u00e1tico em problemas de disco\" estiver ativada, o gerenciador de cluster far\u00e1 o failover autom\u00e1tico do n\u00f3. <\/span><\/p>\n<p><span style=\"font-weight: 400\">As estat\u00edsticas acima est\u00e3o dispon\u00edveis na p\u00e1gina Estat\u00edsticas como -<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Falhas de leitura de disco do #<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Falhas de grava\u00e7\u00e3o de disco do #<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400\">Observa\u00e7\u00e3o - \u00c9 poss\u00edvel que uma estat\u00edstica aumente e a outra n\u00e3o. Por exemplo, quando o disco estiver cheio, as grava\u00e7\u00f5es falhar\u00e3o, fazendo com que as \"falhas de grava\u00e7\u00e3o\" aumentem, mas as leituras ainda poder\u00e3o ser feitas.<\/span><\/p>\n<h2><span style=\"font-weight: 400\">Auto-FailOver em mais de um n\u00f3<\/span><\/h2>\n<p><span style=\"font-weight: 400\">Antes do Couchbase Server 5.5, a contagem de failover autom\u00e1tico ou a cota era definida como 1, ou seja, apenas um n\u00f3 pode sofrer failover autom\u00e1tico antes de exigir interven\u00e7\u00e3o do usu\u00e1rio. Essa era uma restri\u00e7\u00e3o para evitar uma falha de rea\u00e7\u00e3o em cadeia de v\u00e1rios ou de todos os n\u00f3s do cluster.<\/span><\/p>\n<p><span style=\"font-weight: 400\">No entanto, o gerenciador de cluster forneceu o alerta interno \"Node was auto-failed-over\" no primeiro n\u00f3 e \"<\/span><span style=\"font-weight: 400\">O n\u00famero m\u00e1ximo de n\u00f3s com falha autom\u00e1tica foi atingido\".<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-4930\" src=\"https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/2018\/04\/Couchbase_Console_Enterprise_Edition_5_5_0_build_2036_-_Demo-2.png\" alt=\"\" width=\"816\" height=\"391\" srcset=\"https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2018\/04\/Couchbase_Console_Enterprise_Edition_5_5_0_build_2036_-_Demo-2.png 816w, https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2018\/04\/Couchbase_Console_Enterprise_Edition_5_5_0_build_2036_-_Demo-2-300x144.png 300w, https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2018\/04\/Couchbase_Console_Enterprise_Edition_5_5_0_build_2036_-_Demo-2-768x368.png 768w, https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2018\/04\/Couchbase_Console_Enterprise_Edition_5_5_0_build_2036_-_Demo-2-20x10.png 20w\" sizes=\"auto, (max-width: 816px) 100vw, 816px\" \/><\/p>\n<p><span style=\"font-weight: 400\">No Couchbase Server 5.5, os usu\u00e1rios poder\u00e3o configurar o failover de v\u00e1rias inst\u00e2ncias se todos os buckets no cluster estiverem configurados com &gt; 1 r\u00e9plica, caso em que o m\u00e1ximo de 3 inst\u00e2ncias poder\u00e1 sofrer failover automaticamente <\/span><span style=\"font-weight: 400\">sem <\/span><span style=\"font-weight: 400\">exigindo<\/span><span style=\"font-weight: 400\"> interven\u00e7\u00e3o manual, como a redefini\u00e7\u00e3o da cota de failover autom\u00e1tico. <\/span><\/p>\n<p><span style=\"font-weight: 400\">Os usu\u00e1rios agora podem configurar <\/span><span style=\"font-weight: 400\">as seguintes configura\u00e7\u00f5es nas Configura\u00e7\u00f5es de disponibilidade do n\u00f3 no Console da Web do Couchbase ou por meio da API CLI\/REST.<\/span><\/p>\n<ul>\n<li style=\"list-style-type: none\">\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Ativar o failover autom\u00e1tico para at\u00e9 1 evento padr\u00e3o e um m\u00e1ximo de 3 eventos <\/span>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Isso ativar\u00e1 o recurso e poder\u00e1 ser ativado somente quando o failover autom\u00e1tico estiver ativado.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Ele estar\u00e1 desativado por padr\u00e3o.<\/span><\/li>\n<\/ul>\n<\/li>\n<li><b><span style=\"font-weight: 400\">O per\u00edodo de tempo em segundos<\/span><\/b>\n<ul>\n<li>O m\u00ednimo pode ser definido como 5 segundos, o m\u00e1ximo como 3600 segundos e o padr\u00e3o \u00e9 120 segundos.<\/li>\n<li><span style=\"font-weight: 400\">Pode ser editado pelo usu\u00e1rio a qualquer momento<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2><span style=\"font-weight: 400\">Como isso funciona?<\/span><\/h2>\n<p><span style=\"font-weight: 400\">O gerenciador de cluster valida o n\u00famero de r\u00e9plicas configuradas para todos os compartimentos no cluster. No caso de diferentes compartimentos com diferentes r\u00e9plicas configuradas, o gerenciador de cluster considerar\u00e1 apenas as r\u00e9plicas m\u00e1ximas configuradas em todos os compartimentos. <\/span><\/p>\n<p><span style=\"font-weight: 400\">Por exemplo, se um cluster tiver\u00a0<\/span><\/p>\n<ul>\n<li style=\"list-style-type: none\">\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">um bucket com 1 r\u00e9plica e outro com 2 r\u00e9plicas e, em seguida, permitir o failover autom\u00e1tico de at\u00e9 apenas 1 n\u00f3.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">dois buckets com 2 r\u00e9plicas e, em seguida, permitir o failover autom\u00e1tico de at\u00e9 2 n\u00f3s.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">tr\u00eas buckets com 2 r\u00e9plicas, 2 r\u00e9plicas e 3 r\u00e9plicas configuradas e, em seguida, permitir o failover autom\u00e1tico de at\u00e9 2 n\u00f3s.<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400\">A cota m\u00e1xima de failover autom\u00e1tico se aplica a todos os n\u00f3s do cluster, incluindo os n\u00f3s de dados, consulta, \u00edndice e pesquisa. <\/span><\/p>\n<p><span style=\"font-weight: 400\">Se dois ou mais n\u00f3s falharem exatamente ao mesmo tempo, o failover autom\u00e1tico n\u00e3o funcionar\u00e1 (independentemente da contagem m\u00e1xima definida pelo usu\u00e1rio), com exce\u00e7\u00e3o do failover autom\u00e1tico do grupo de servidores discutido posteriormente. Essa restri\u00e7\u00e3o est\u00e1 em vigor para evitar que uma parti\u00e7\u00e3o de rede fa\u00e7a com que duas ou mais metades de um cluster falhem uma na outra. Ela protege a integridade e a consist\u00eancia dos dados. <\/span><\/p>\n<p><span style=\"font-weight: 400\">Observa\u00e7\u00e3o - Quando v\u00e1rios n\u00f3s falham, isso aumenta a carga no cluster. Os usu\u00e1rios que desejam permitir o failover autom\u00e1tico de mais de um n\u00f3 precisam se certificar de que t\u00eam capacidade suficiente para lidar com as falhas. <\/span><\/p>\n<h2><span style=\"font-weight: 400\">Grupos de servidores Auto-FailOver (reconhecimento de zona de rack)<\/span><\/h2>\n<p><span style=\"font-weight: 400\">O Rack-Zone Awareness permite agrupamentos l\u00f3gicos de servidores em um cluster em que cada grupo de servidores pertence fisicamente a um rack ou zona de disponibilidade. <\/span><\/p>\n<p><span style=\"font-weight: 400\">No Couchbase Server 5.5, os usu\u00e1rios poder\u00e3o definir as seguintes configura\u00e7\u00f5es nas Configura\u00e7\u00f5es de disponibilidade do n\u00f3 no Console da Web do Couchbase ou por meio da API CLI\/REST.<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Ativar o failover autom\u00e1tico de grupos de servidores<\/span>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Habilite o failover autom\u00e1tico do n\u00f3 para ativar esse recurso\u00a0<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Ser\u00e1 <\/span><b>desligado<\/b><span style=\"font-weight: 400\"> por padr\u00e3o.<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2><span style=\"font-weight: 400\">Como isso funciona?<\/span><\/h2>\n<p><span style=\"font-weight: 400\">Para que o failover autom\u00e1tico de grupos de servidores funcione - <\/span><\/p>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Os clusters exigem um m\u00ednimo de 3 grupos de servidores no momento da falha. Essa restri\u00e7\u00e3o \u00e9 necess\u00e1ria porque, se houver apenas dois grupos de servidores e houver uma parti\u00e7\u00e3o de rede entre eles, os dois grupos de servidores poder\u00e3o tentar fazer failover um do outro.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Todos os n\u00f3s do grupo de servidores falharam. Isso indica uma falha correlacionada que provavelmente afetou toda a zona ou o rack.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Todos os n\u00f3s com falha pertencem ao mesmo grupo de servidores. Isso evita que uma parti\u00e7\u00e3o de rede fa\u00e7a com que duas ou mais metades de um cluster falhem uma na outra.<\/span><\/li>\n<\/ul>\n<h5><span style=\"font-weight: 400\">Recursos adicionais<\/span><\/h5>\n<ul>\n<li style=\"font-weight: 400\"><a href=\"https:\/\/www.couchbase.com\/blog\/pt\/downloads\/\"><span style=\"font-weight: 400\">Fa\u00e7a o download do Couchbase Server 5.5<\/span><\/a><\/li>\n<li style=\"font-weight: 400\"><a href=\"https:\/\/developer.couchbase.com\/documentation\/server\/5.5\/introduction\/intro.html\"><span style=\"font-weight: 400\">Documenta\u00e7\u00e3o do Couchbase Server 5.5<\/span><\/a><\/li>\n<li style=\"font-weight: 400\"><a href=\"https:\/\/hub.docker.com\/r\/couchbase\/server\/tags\/\"><span style=\"font-weight: 400\">Cont\u00eainer do Docker do servidor Couchbase 5.5<\/span><\/a><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Compartilhe suas ideias sobre o<\/span><a href=\"https:\/\/www.couchbase.com\/blog\/pt\/forums\/\"><span style=\"font-weight: 400\"> F\u00f3runs do Couchbase<\/span><\/a><\/li>\n<\/ul>","protected":false},"excerpt":{"rendered":"<p>Couchbase further improves high availability for mission-critical deployments and reduces operator intervention. Couchbase enhances the detection of common disk failures and automatically fails over the node with bad disks saving operators time and energy. It also handles multiple server failures [&hellip;]<\/p>","protected":false},"author":8,"featured_media":13873,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[1815,1821,1816],"tags":[2258,2182,2126],"ppma_author":[8952],"class_list":["post-4929","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-best-practices-and-tutorials","category-couchbase-architecture","category-couchbase-server","tag-5-5","tag-devbuild","tag-high-availability"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v26.1 (Yoast SEO v26.1.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Auto-FailOver Features in Couchbase Server 5.5 - The Couchbase Blog<\/title>\n<meta name=\"description\" content=\"Learn how Auto-FailOver Feature in Couchbase Server 5.5 handles the disk related issues on a node. Also, check how does it work.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.couchbase.com\/blog\/pt\/auto-failover-features-couchbase-server-5-5-developer-build\/\" \/>\n<meta property=\"og:locale\" content=\"pt_BR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Auto-FailOver Features in Couchbase Server 5.5\" \/>\n<meta property=\"og:description\" content=\"Learn how Auto-FailOver Feature in Couchbase Server 5.5 handles the disk related issues on a node. Also, check how does it work.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.couchbase.com\/blog\/pt\/auto-failover-features-couchbase-server-5-5-developer-build\/\" \/>\n<meta property=\"og:site_name\" content=\"The Couchbase Blog\" \/>\n<meta property=\"article:published_time\" content=\"2018-04-03T02:53:06+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-06-14T06:43:09+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2018\/04\/Screen-Shot-2018-04-01-at-2.29.09-PM.png\" \/>\n\t<meta property=\"og:image:width\" content=\"2048\" \/>\n\t<meta property=\"og:image:height\" content=\"1004\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Anil Kumar, Director Product Management, Couchbase Cloud-Native Database\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@anilkumar1129\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Anil Kumar, Director Product Management, Couchbase Cloud-Native Database\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\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\":\"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/\"},\"author\":{\"name\":\"Anil Kumar, Director Product Management, Couchbase Cloud-Native Database\",\"@id\":\"https:\/\/www.couchbase.com\/blog\/#\/schema\/person\/ed8c1d98490712a9c8fd5a9e066c61db\"},\"headline\":\"Auto-FailOver Features in Couchbase Server 5.5\",\"datePublished\":\"2018-04-03T02:53:06+00:00\",\"dateModified\":\"2025-06-14T06:43:09+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/\"},\"wordCount\":945,\"commentCount\":1,\"publisher\":{\"@id\":\"https:\/\/www.couchbase.com\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2022\/11\/couchbase-nosql-dbaas.png\",\"keywords\":[\"5.5\",\"devbuild\",\"High Availability\"],\"articleSection\":[\"Best Practices and Tutorials\",\"Couchbase Architecture\",\"Couchbase Server\"],\"inLanguage\":\"pt-BR\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/\",\"url\":\"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/\",\"name\":\"Auto-FailOver Features in Couchbase Server 5.5 - The Couchbase Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.couchbase.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2022\/11\/couchbase-nosql-dbaas.png\",\"datePublished\":\"2018-04-03T02:53:06+00:00\",\"dateModified\":\"2025-06-14T06:43:09+00:00\",\"description\":\"Learn how Auto-FailOver Feature in Couchbase Server 5.5 handles the disk related issues on a node. Also, check how does it work.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/#breadcrumb\"},\"inLanguage\":\"pt-BR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-BR\",\"@id\":\"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/#primaryimage\",\"url\":\"https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2022\/11\/couchbase-nosql-dbaas.png\",\"contentUrl\":\"https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2022\/11\/couchbase-nosql-dbaas.png\",\"width\":1800,\"height\":630},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.couchbase.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Auto-FailOver Features in Couchbase Server 5.5\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.couchbase.com\/blog\/#website\",\"url\":\"https:\/\/www.couchbase.com\/blog\/\",\"name\":\"The Couchbase Blog\",\"description\":\"Couchbase, the NoSQL Database\",\"publisher\":{\"@id\":\"https:\/\/www.couchbase.com\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.couchbase.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pt-BR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.couchbase.com\/blog\/#organization\",\"name\":\"The Couchbase Blog\",\"url\":\"https:\/\/www.couchbase.com\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-BR\",\"@id\":\"https:\/\/www.couchbase.com\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/2023\/04\/admin-logo.png\",\"contentUrl\":\"https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/2023\/04\/admin-logo.png\",\"width\":218,\"height\":34,\"caption\":\"The Couchbase Blog\"},\"image\":{\"@id\":\"https:\/\/www.couchbase.com\/blog\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.couchbase.com\/blog\/#\/schema\/person\/ed8c1d98490712a9c8fd5a9e066c61db\",\"name\":\"Anil Kumar, Director Product Management, Couchbase Cloud-Native Database\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-BR\",\"@id\":\"https:\/\/www.couchbase.com\/blog\/#\/schema\/person\/image\/86e4570d5755b073087333983950b3a0\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/7a4ec23feb4ba1eed5342b1010841d36c47c1f330c26d85b3b8340b8f89ea3d7?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/7a4ec23feb4ba1eed5342b1010841d36c47c1f330c26d85b3b8340b8f89ea3d7?s=96&d=mm&r=g\",\"caption\":\"Anil Kumar, Director Product Management, Couchbase Cloud-Native Database\"},\"description\":\"Anil Kumar is the Director of Product Management at Couchbase. Anil\u2019s career spans more than 19+ years of building software products across various domains, including enterprise software and cloud services. He is a hands-on product leader responsible for Couchbase Server, Couchbase Cloud, and Kubernetes product lines, including evangelizing the product strategy and vision with customers, partners, developers, and analysts. Before joining Couchbase, Anil spent several years working at Microsoft Redmond. Anil holds a master\u2019s degree in computer science from the University of Toronto (Canada) and a bachelor\u2019s in information technology from Visvesvaraya Technological University (India).\",\"sameAs\":[\"https:\/\/x.com\/@anilkumar1129\"],\"url\":\"https:\/\/www.couchbase.com\/blog\/pt\/author\/anil-kumar\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Auto-FailOver Features in Couchbase Server 5.5 - The Couchbase Blog","description":"Saiba como o recurso Auto-FailOver no Couchbase Server 5.5 lida com os problemas relacionados ao disco em um n\u00f3. Al\u00e9m disso, veja como ele funciona.","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":"https:\/\/www.couchbase.com\/blog\/pt\/auto-failover-features-couchbase-server-5-5-developer-build\/","og_locale":"pt_BR","og_type":"article","og_title":"Auto-FailOver Features in Couchbase Server 5.5","og_description":"Learn how Auto-FailOver Feature in Couchbase Server 5.5 handles the disk related issues on a node. Also, check how does it work.","og_url":"https:\/\/www.couchbase.com\/blog\/pt\/auto-failover-features-couchbase-server-5-5-developer-build\/","og_site_name":"The Couchbase Blog","article_published_time":"2018-04-03T02:53:06+00:00","article_modified_time":"2025-06-14T06:43:09+00:00","og_image":[{"width":2048,"height":1004,"url":"https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2018\/04\/Screen-Shot-2018-04-01-at-2.29.09-PM.png","type":"image\/png"}],"author":"Anil Kumar, Director Product Management, Couchbase Cloud-Native Database","twitter_card":"summary_large_image","twitter_creator":"@anilkumar1129","twitter_misc":{"Written by":"Anil Kumar, Director Product Management, Couchbase Cloud-Native Database","Est. reading time":"5 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/#article","isPartOf":{"@id":"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/"},"author":{"name":"Anil Kumar, Director Product Management, Couchbase Cloud-Native Database","@id":"https:\/\/www.couchbase.com\/blog\/#\/schema\/person\/ed8c1d98490712a9c8fd5a9e066c61db"},"headline":"Auto-FailOver Features in Couchbase Server 5.5","datePublished":"2018-04-03T02:53:06+00:00","dateModified":"2025-06-14T06:43:09+00:00","mainEntityOfPage":{"@id":"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/"},"wordCount":945,"commentCount":1,"publisher":{"@id":"https:\/\/www.couchbase.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/#primaryimage"},"thumbnailUrl":"https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2022\/11\/couchbase-nosql-dbaas.png","keywords":["5.5","devbuild","High Availability"],"articleSection":["Best Practices and Tutorials","Couchbase Architecture","Couchbase Server"],"inLanguage":"pt-BR","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/","url":"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/","name":"Auto-FailOver Features in Couchbase Server 5.5 - The Couchbase Blog","isPartOf":{"@id":"https:\/\/www.couchbase.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/#primaryimage"},"image":{"@id":"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/#primaryimage"},"thumbnailUrl":"https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2022\/11\/couchbase-nosql-dbaas.png","datePublished":"2018-04-03T02:53:06+00:00","dateModified":"2025-06-14T06:43:09+00:00","description":"Saiba como o recurso Auto-FailOver no Couchbase Server 5.5 lida com os problemas relacionados ao disco em um n\u00f3. Al\u00e9m disso, veja como ele funciona.","breadcrumb":{"@id":"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/#breadcrumb"},"inLanguage":"pt-BR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/"]}]},{"@type":"ImageObject","inLanguage":"pt-BR","@id":"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/#primaryimage","url":"https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2022\/11\/couchbase-nosql-dbaas.png","contentUrl":"https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/sites\/1\/2022\/11\/couchbase-nosql-dbaas.png","width":1800,"height":630},{"@type":"BreadcrumbList","@id":"https:\/\/www.couchbase.com\/blog\/auto-failover-features-couchbase-server-5-5-developer-build\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.couchbase.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Auto-FailOver Features in Couchbase Server 5.5"}]},{"@type":"WebSite","@id":"https:\/\/www.couchbase.com\/blog\/#website","url":"https:\/\/www.couchbase.com\/blog\/","name":"Blog do Couchbase","description":"Couchbase, o banco de dados NoSQL","publisher":{"@id":"https:\/\/www.couchbase.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.couchbase.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pt-BR"},{"@type":"Organization","@id":"https:\/\/www.couchbase.com\/blog\/#organization","name":"Blog do Couchbase","url":"https:\/\/www.couchbase.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"pt-BR","@id":"https:\/\/www.couchbase.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/2023\/04\/admin-logo.png","contentUrl":"https:\/\/www.couchbase.com\/blog\/wp-content\/uploads\/2023\/04\/admin-logo.png","width":218,"height":34,"caption":"The Couchbase Blog"},"image":{"@id":"https:\/\/www.couchbase.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.couchbase.com\/blog\/#\/schema\/person\/ed8c1d98490712a9c8fd5a9e066c61db","name":"Anil Kumar, diretor de gerenciamento de produtos do banco de dados nativo da nuvem Couchbase","image":{"@type":"ImageObject","inLanguage":"pt-BR","@id":"https:\/\/www.couchbase.com\/blog\/#\/schema\/person\/image\/86e4570d5755b073087333983950b3a0","url":"https:\/\/secure.gravatar.com\/avatar\/7a4ec23feb4ba1eed5342b1010841d36c47c1f330c26d85b3b8340b8f89ea3d7?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/7a4ec23feb4ba1eed5342b1010841d36c47c1f330c26d85b3b8340b8f89ea3d7?s=96&d=mm&r=g","caption":"Anil Kumar, Director Product Management, Couchbase Cloud-Native Database"},"description":"Anil Kumar \u00e9 o diretor de gerenciamento de produtos da Couchbase. A carreira de Anil abrange mais de 19 anos de desenvolvimento de produtos de software em v\u00e1rios dom\u00ednios, incluindo software corporativo e servi\u00e7os em nuvem. Ele \u00e9 um l\u00edder de produto pr\u00e1tico respons\u00e1vel pelas linhas de produtos Couchbase Server, Couchbase Cloud e Kubernetes, incluindo a divulga\u00e7\u00e3o da estrat\u00e9gia e da vis\u00e3o do produto com clientes, parceiros, desenvolvedores e analistas. Antes de ingressar na Couchbase, Anil passou v\u00e1rios anos trabalhando na Microsoft Redmond. Anil tem mestrado em ci\u00eancia da computa\u00e7\u00e3o pela Universidade de Toronto (Canad\u00e1) e \u00e9 bacharel em tecnologia da informa\u00e7\u00e3o pela Universidade Tecnol\u00f3gica de Visvesvaraya (\u00cdndia).","sameAs":["https:\/\/x.com\/@anilkumar1129"],"url":"https:\/\/www.couchbase.com\/blog\/pt\/author\/anil-kumar\/"}]}},"authors":[{"term_id":8952,"user_id":8,"is_guest":0,"slug":"anil-kumar","display_name":"Anil Kumar, Director Product Management, Couchbase Cloud-Native Database","avatar_url":"https:\/\/secure.gravatar.com\/avatar\/7a4ec23feb4ba1eed5342b1010841d36c47c1f330c26d85b3b8340b8f89ea3d7?s=96&d=mm&r=g","author_category":"","last_name":"Kumar, Director Product Management, Couchbase Cloud-Native Database","first_name":"Anil","job_title":"","user_url":"","description":"Anil Kumar \u00e9 o diretor de gerenciamento de produtos da Couchbase. A carreira de Anil abrange mais de 19 anos de desenvolvimento de produtos de software em v\u00e1rios dom\u00ednios, incluindo software corporativo e servi\u00e7os em nuvem. Ele \u00e9 um l\u00edder de produto pr\u00e1tico respons\u00e1vel pelas linhas de produtos Couchbase Server, Couchbase Cloud e Kubernetes, incluindo a divulga\u00e7\u00e3o da estrat\u00e9gia e da vis\u00e3o do produto com clientes, parceiros, desenvolvedores e analistas. Antes de ingressar na Couchbase, Anil passou v\u00e1rios anos trabalhando na Microsoft Redmond. Anil tem mestrado em ci\u00eancia da computa\u00e7\u00e3o pela Universidade de Toronto (Canad\u00e1) e \u00e9 bacharel em tecnologia da informa\u00e7\u00e3o pela Universidade Tecnol\u00f3gica de Visvesvaraya (\u00cdndia)."}],"_links":{"self":[{"href":"https:\/\/www.couchbase.com\/blog\/pt\/wp-json\/wp\/v2\/posts\/4929","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.couchbase.com\/blog\/pt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.couchbase.com\/blog\/pt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.couchbase.com\/blog\/pt\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/www.couchbase.com\/blog\/pt\/wp-json\/wp\/v2\/comments?post=4929"}],"version-history":[{"count":0,"href":"https:\/\/www.couchbase.com\/blog\/pt\/wp-json\/wp\/v2\/posts\/4929\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.couchbase.com\/blog\/pt\/wp-json\/wp\/v2\/media\/13873"}],"wp:attachment":[{"href":"https:\/\/www.couchbase.com\/blog\/pt\/wp-json\/wp\/v2\/media?parent=4929"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.couchbase.com\/blog\/pt\/wp-json\/wp\/v2\/categories?post=4929"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.couchbase.com\/blog\/pt\/wp-json\/wp\/v2\/tags?post=4929"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.couchbase.com\/blog\/pt\/wp-json\/wp\/v2\/ppma_author?post=4929"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}