• antirez's avatar
    Cluster: atomic update of nodes.conf file. · 6c63df30
    antirez authored
    The way the file was generated was unsafe and leaded to nodes.conf file
    corruption (zero length file) on server stop/crash during the creation
    of the file.
    
    The previous file update method was as simple as open with O_TRUNC
    followed by the write call. While the write call was a single one with
    the full payload, ensuring no half-written files for POSIX semantics,
    stopping the server just after the open call resulted into a zero-length
    file (all the nodes information lost!).
    6c63df30
cluster.c 131 KB