State of Disaggregated HCI (HCI Mesh)-vSAN 8 U1

Thu, 22 Jun 2023 19:02:28 +0000

Introduction

I have already talked about HCI Mesh (dHCI) when it was first launched with vSAN 7.0 U1 here, I would encourage you to read thru my previous blog for better understanding of this feature and its capabilities.

This feature was originally announced with vSAN OSA for 7.0 U1 with standard vSAN clusters where a server cluster could share its vSAN Datastore with 5 Client vSAN cluster and a Client Cluster could mount upto 5 remote vSAN Datastore.Compute-Only cluster was not supported in this initial release.

Native vSAN Trace Object

Tue, 20 Jun 2023 18:11:08 +0000

vSANTraces are generally used to troubleshoot and debug critical performance issues in vSAN(OSA and ESA) and also in some cases they are used to troubleshoot vSAN data-path related problems such as Stuck-IO, Congestion, slow/no de-stage etcetera. vSANTraces are not require to troubleshoot/debug all kinds of issues however is required for certain cases.

In any vSAN enabled host, you might have noticed that the default location/path where the traces are collected is “/vsantraces”. Depending on the requirement, users may however change the path for vSANTraces to external Storage or a local datastore and change the default settings of “Number Of Files To Rotate:” and “Maximum Trace File Size:” for vSANTraces using esxcli commands. Having said that VMware doesnt recommend/allow customers to set the path for vSANTraces to vSAN-Datastore directly because it will impact performance of the virtual machines running on vSANDatastore as vsanTraces are write heavy (every subsystem of vSAN data-path writes to traces for bunch IO) which helps engineering to debug issues.

VSAN 8 U1 on blogs.hareeshkg.com

State of Disaggregated HCI (HCI Mesh)-vSAN 8 U1

Introduction

Native vSAN Trace Object