In this episode, Sean Donahue looks back at the tech stories from 2022. The highs, lows, and everything in between. What story did we miss? Which stories surprised you in 2022? Please leave your comments below.<\/p>

Have a wonderful 2023!<\/p>

<\/oembed><\/p>

\u00a0<\/p>

If you have any questions, feel free to reach out to me on\u00a0Twitter<\/a>\u00a0and if you haven't already done so, make sure you are subscribed to the show wherever you consume podcasts.<\/p>

\u00a0<\/p>","id":41482,"featuredImage":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/attachment\/f38aec9c-1b9f-472b-8bc4-5177f93527b7_thumb.png","label":"Blog","replyCount":0,"views":230,"post":{"id":63100,"author":{"id":7898,"url":"\/members\/aluciani-7898","name":"aluciani","avatar":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/icon\/200x200\/77accf89-4f79-48be-81e6-c2ac5507e29b.png","userTitle":"Chevalier","rank":{"isBold":false,"isItalic":false,"isUnderline":false,"name":"Chevalier","color":"#660099"},"userLevel":7},"content":"

In this episode, Sean Donahue looks back at the tech stories from 2022. The highs, lows, and everything in between. What story did we miss? Which stories surprised you in 2022? Please leave your comments below.<\/p>

Have a wonderful 2023!<\/p>

<\/oembed><\/p>

\u00a0<\/p>

If you have any questions, feel free to reach out to me on\u00a0Twitter<\/a>\u00a0and if you haven't already done so, make sure you are subscribed to the show wherever you consume podcasts.<\/p>

\u00a0<\/p>","url":"\/community-blog-154\/nutanix-community-podcast-2022-year-in-review-41482?postid=63100#post63100","creationDate":"2023-01-03T14:40:38+0000","relativeCreationDate":"20 days ago"},"contentType":"article","type":3,"likes":3,"hasCurrentUserLiked":false},"phrases":{"Forum":{"{n} year|{n} years":"{n} year|{n} years","{n} month|{n} months":"{n} month|{n} months","{n} day|{n} days":"{n} day|{n} days","{n} hour|{n} hours":"{n} hour|{n} hours","{n} minute|{n} minutes":"{n} minute|{n} minutes","just":"just now","{plural} ago":"{plural} ago"}}}">

问题

您可以承受多少个节点失败？（4node cluster -rf2）

C
徽章

你好。我对RF2功能有疑问。

当前，它由4个节点和RF2作为群集组成。

据我所知，RF2有1个节点失败。

如果是这样，数据弹性状态不应该下降失败吗？

但是，尽管一个节点失败了，但数据弹性状态仍然可以。

实际上，当前群集中的CPU，内存和存储使用率很低。

目前，只有3个节点为Active CPU IS 20％内存为40％存储为18.5％。

为什么数据弹性状态可以？

即使目前关闭了另一个节点，该服务也有任何问题吗？

还是群集会死亡，如果有1个节点死亡？

如果您不死，我想知道为什么。

\u00a0<\/p>

Hello. I have a question about the RF2 function.<\/p>

Currently, it is composed of 4 nodes and RF2 as a cluster.<\/p>

As far as I know, RF2 has 1 node fail.<\/p>

If so, shouldn't the Data Resiliency Status drop to Fail?<\/p>

However, although one node has failed, the Data Resiliency Status is still OK.<\/p>

In fact, the CPU, Memory, and Storage usage in the current cluster is low.<\/p>

Currently only 3 nodes are active CPU is 20% Memory is 40% Storage is 18.5%.<\/p>

Why is the Data Resiliency Status Ok?<\/p>

Is there any problem with the service even if one more node is currently turned off?<\/p>

Or will the cluster die if 1 more Node dies?<\/p>

If you don't die, I want to know why.<\/p>","quoteUsername":"cubensys","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

该主题已关闭以供评论

4个答复

UPX
UserLevel 2
徽章 +4

你好 @cubensys

解释非常简单。
Nutanix不仅基于最小节点数量（群集为3），而且基于资源的可用性。

这对您而言是什么意思？

您有4个带有RF2的节点，当一个节点失败时，AOS立即开始复制数据以返回稳定的RF2状态。由于您有4个节点，并且可能有足够的资源来保持工作负载活跃，因此系统仅用3个节点返回稳定状态。

如果您的群集处于3个节点，或者如果3个活动节点上留下的资源不足以使工作负载完全运行，那么这显然不会发生。

现在，将数据弹性处于确定状态，您可以失去另一个节点，然后您将面临关键状态。

希望这可以帮助

准备工作是出色工作的起点！
Hi @cubensys<\/user-mention>\u00a0<\/p>

The explanation is fairly simple.
Nutanix bases the resilience factor not only on the minimum number of nodes (which for a cluster is 3) but also on the availability of resources.<\/p>

What does this mean in your case?<\/p>

You have 4 nodes with RF2, when one of the nodes fails AOS\u00a0immediately starts replicating the data to return to a stable RF2 state. Since you have 4 nodes and probably enough resources to keep the workloads active, the system returns to a stable state with only 3 nodes.<\/p>

This obviously would not have happened if your cluster had been at 3 nodes or if the resources left on the 3 active nodes were not enough to keep the workloads fully operational.<\/p>

Now, with your data resiliency in OK state, you can loose another node and then you will face\u00a0a critical status.<\/p>

Hope this helps<\/p>","quoteUsername":"UPX","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

C
徽章 
谢谢您的回答。资源可用性？
Thank you for answer.Then, I understood that the cluster is in a stable state with 3 nodes.If one fails in three nodes, the Data Resiliency Status will be in a critical state,\u00a0but can it be determined that the service is maintained due to resource availability?<\/pre>","quoteUsername":"cubensys","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
UPX
UserLevel 2
徽章 +4 
谢谢您的回答。资源可用性？

不确定我是否理解您的问题，但是通常，如果您对n+1的3个节点群集尺寸，当节点失败时，临界状态仅意味着您不能放松其他组件，但所有工作负载都启动并运行。否则，系统仅维护运行的工作负载，而其他资源则停止。

您可以确定您的群集将用于3种不同的设置的HA类型

最好的努力（系统将根据资源消耗自动决定）

HA（系统将为HA目的保留每个节点的专用内存）

专用节点（系统将整个节点荣誉用作备用）此设置已弃用

您会发现有关HA如何工作的更多有用信息

https://portal.nutanix.com/page/documents/kbs/details?targetId=ka00e000000000000liquca4

准备工作是出色工作的起点！
\t
Thank you for answer.Then, I understood that the cluster is in a stable state with 3 nodes.If one fails in three nodes, the Data Resiliency Status will be in a critical state,\u00a0but can it be determined that the service is maintained due to resource availability?<\/pre>\t<\/content-quote>
Not sure if i understand your question but usually, if you size\u00a0a 3 nodes cluster for N+1, when a node fails the critical state simply means you can not loose other components\u00a0but all the workloads are up and running. Otherwise the system maintain running only the workload there are resources for, the others are stopped.\u00a0<\/p>
You can be sure about the type\u00a0of HA\u00a0your cluster will use with 3 different settings<\/p>
Best Effort (the system will decide automatically based on resource consumption)<\/p>
HA (The system will reserve a dedicate amount of memory per node for HA purpose)<\/p>
Dedicated Node (An entire node wolud be used by the system as spare) this setting\u00a0is deprecated<\/u><\/strong><\/span><\/p>
You will find more useful\u00a0information about how HA works here<\/p>
https:\/\/portal.nutanix.com\/page\/documents\/kbs\/details?targetId=kA00e000000LIQUCA4<\/a><\/p>
\u00a0<\/p>
\u00a0<\/p>
\u00a0<\/p>","quoteUsername":"UPX","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
阿罗纳
秩
UserLevel 6
徽章 +5

嗨，Cubensys，

与其从节点角度观察任务，而要从数据观点的副本数量查看。

您有4个节点。在RF-2群集中，您有2个数据副本。您会失去一个节点，这意味着您将失去数据的第二副本。预期的初始数据弹性状态失败了，因为如果您丢失了另一个节点，则有可能在该节点上丢失相同数据的其他副本。

但是，数据的第二副本仍然可以通过复制现有数据来恢复。复制过程完成后，群集数据弹性状态返回确定。

Hi cubensys,<\/p>

\u00a0<\/p>

Instead of looking at the task from the number of nodes perspective, look at it from the number of copies of data point of view.<\/p>

You have 4 nodes. In an RF-2 cluster you have 2 copies of data. You loose one node which means you lose part of the second copy of the data. The expected initial Data Resiliency state is Fail because if you lose another node then it is possible that with that node you lose the other copy of the same data.<\/p>

However the second copy of data can still be recovered by replicating the existing data. Once the copying process is complete the cluster Data Resiliency status returns to OK.<\/p>","quoteUsername":"Alona","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

条款和条件
Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
Functional","cookiepolicy.modal.level2":"Normal
Functional + analytics","cookiepolicy.modal.level3":"Complete
Functional + analytics + social media + embedded videos"}}}">
Baidu