public static WALKeyImpl createWALKey(final RegionInfo hri, MultiVersionConcurrencyControl mvcc,
    final NavigableMap<byte[], Integer> replicationScope,
    final Map<String, byte[]> extendedAttributes) {
    return new WALKeyImpl(hri.getEncodedNameAsBytes(), hri.getTable(),
      EnvironmentEdgeManager.currentTime(), mvcc, replicationScope, extendedAttributes);
  }
Here we do not abort the RegionServer for {@link WALSyncTimeoutIOException} as
{@link HRegion#doWALAppend} does,because WAL Marker just records the internal state and
seems it is no need to always abort the RegionServer when {@link WAL#sync} timeout,it is
the internal state transition that determines whether RegionServer is aborted or not.
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/WALUtil.java