• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

Changed advanced setting VSAN.ClomRepairDelay and upgrading to 6.7 u1? Read this…

Duncan Epping · Feb 6, 2019 ·

If you changed the advanced setting VSAN.ClomRepairDelay to anything else than the default 60 minutes there’s a caveat during the upgrade to 6.7 U1 you need to be aware of. When you do this upgrade the default is reset, meaning the value is configured once again to 60 minutes.  It was reported on twitter by “Justin Bias” this week, and I tested in the lab and indeed experience the same behavior. I set my value to 90 and after an upgrade from 6.7 to 6.7 U1 the below was the result.

Why did this happen? Well, in vSAN 6.7 U1 we introduced a new global cluster-wide setting. On a cluster level under “Configure >> vSAN >> Services” you now have the option to set the “Object Repair Time” for the full cluster, instead of doing this on a host by host basis. Hopefully this will make your life a bit easier.

Note that when you make the change globally it appears that the Advanced Settings UI is not updated automatically. The change is however committed to the host, this is just a UI bug at the moment and will be fixed in a future release.

Share it:

  • Tweet

Related

Server, Software Defined, Storage, vSAN 6.7, 6.7 u1, update, upgrade, vsan, vSphere

Reader Interactions

Comments

  1. tronar says

    6 February, 2019 at 11:23

    Does it actually change it in the hosts or just assumes it was 60 and leaves the hosts as they were ?

    • Duncan Epping says

      6 February, 2019 at 11:51

      As I said, it resets the value back to 60. If it was 120, it will set it back to 60 on the host.

      • Hareesh K G says

        7 February, 2019 at 08:51

        Hello Duncan,

        Quick Question , will this automatically restart clomd service after we change this value on Vcenter-Cluster wide ? or should restart clomd service individually on all host after making this change?

        • Duncan Epping says

          8 February, 2019 at 10:21

          vSAN will ensure the setting is applied, no need to manually restart CLOMD

  2. Glenn says

    12 June, 2019 at 09:56

    On 6.7 GA release, how do I change this setting to 120 or 180 minutes? We have maintenance windows coming up that will last around 2 hours, and I want to avoid unnecessary rebuilds.

    • Duncan Epping says

      12 June, 2019 at 12:56

      In 6.7 you need to set it using the advanced setting as specified in the article unfortunately.

  3. strauss says

    17 June, 2019 at 21:10

    interesting take, I will follow for more!

Primary Sidebar

About the author

Duncan Epping is a Chief Technologist in the Office of CTO of the Cloud Platform BU at VMware. He is a VCDX (# 007), the author of the "vSAN Deep Dive", the “vSphere Clustering Technical Deep Dive” series, and the host of the "Unexplored Territory" podcast.

Upcoming Events

29-08-2022 – VMware Explore US
07-11-2022 – VMware Explore EMEA
….

Recommended Reads

Sponsors

Want to support Yellow-Bricks? Buy an advert!

Advertisements

Copyright Yellow-Bricks.com © 2022 · Log in