You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gflag values have default values that are specified in (C++) code. We want to be able to specify a different default from the C++ code default for certain gflags for dbs set up through Platform.
For example, we want to set the gflag fail_on_out_of_range_clock_skew=false for Platform universes though it is set to true in OSS universes. This is because we want to handle clock skew issues through alerts rather than crashes in the Platform case.
This will involve:
Set the gflag to this value for newly created Platform universes for VMs
Gflag values have default values that are specified in (C++) code. We want to be able to specify a different default from the C++ code default for certain gflags for dbs set up through Platform.
For example, we want to set the gflag
fail_on_out_of_range_clock_skew=false
for Platform universes though it is set to true in OSS universes. This is because we want to handle clock skew issues through alerts rather than crashes in the Platform case.This will involve:
This is because unknown gflags cause k8s yb processes to crash (VMs use conf files instead). We can avoid this logic by fixing [k8s] [YW] Use flagfile to specify gflags to yb-master/tserver in helm chart #6684
For the k8s work, we will also need to complete the helm chart versioning work (#8950).
@jvigil-yugabyte @bmatican @streddy-yb
The text was updated successfully, but these errors were encountered: