if yes, can that be changed?
#is it true that when a clusternode crashes, a takeover will wait until the coredump is complete?
modest geyser
swift eagle
some information from netapp doc
Make sure a spare disk is available that is at least as big as the sum of main memory and NVRAM. Set the option "coredump.metadata_only" to "on". If the problem persists, turn off the option "cf.takeover.on_panic". This will disable the sparecore feature, and delay takeovers until the panicing partner has finished dumping the core.
looks like check to see if you have that option turned off
check to see of the option cf.takeover.on_panic is turned off
in this situation takeover will be delayed untill the time core is written to the disks
much more info on core dump for future references
wintry niche
It depends on the system, really.
If your system was released with ONTAP 9.4 (e.g., FAS27xx, AFF A220, AFF A800) or later, then the core file will always be saved to the boot media. This, in turn, allows the core to be saved far more quickly and the node can reboot faster.
Systems prior to those offered with ONTAP 9.4 will use the behavior as described above. What method is used (spraycore or sparecore) will depend on the system configuration and drive types.