Changes of disabled config MUST be eventually visible

CHANGELOG.md

@@ -11,10 +11,19 @@ release.
 
 ### Traces
 
+- Changes of `TracerConfig.disabled` MUST be eventually visible.
+  ([#4645](https://github.com/open-telemetry/opentelemetry-specification/pull/4645))
+
 ### Metrics
 
+- Changes of `MeterConfig.disabled` MUST be eventually visible.
+  ([#4645](https://github.com/open-telemetry/opentelemetry-specification/pull/4645))
+
 ### Logs
 
+- Changes of `LoggerConfig.disabled` MUST be eventually visible.
+  ([#4645](https://github.com/open-telemetry/opentelemetry-specification/pull/4645))
+
 ### Baggage
 
 ### Profiles

specification/logs/sdk.md

@@ -217,6 +217,7 @@ It consists of the following parameters:
 
 It is not necessary for implementations to ensure that changes to any of these
 parameters are immediately visible to callers of `Enabled`.
+However, the changes MUST be eventually visible.
 
 ### Emit a LogRecord
 

specification/metrics/sdk.md

@@ -1013,6 +1013,7 @@ aggregation when no matching views match the instrument.
 
 It is not necessary for implementations to ensure that changes
 to `MeterConfig.disabled` are immediately visible to callers of `Enabled`.
+However, the changes MUST be eventually visible.
 
 ## Attribute limits
 

specification/trace/sdk.md

@@ -207,9 +207,11 @@ It consists of the following parameters:
 
   The value of `disabled` MUST be used to resolve whether a `Tracer`
   is [Enabled](./api.md#enabled). If `disabled` is `true`, `Enabled`
-  returns `false`. If `disabled` is `false`, `Enabled` returns `true`. It is not
-  necessary for implementations to ensure that changes to `disabled` are
-  immediately visible to callers of `Enabled`.
+  returns `false`. If `disabled` is `false`, `Enabled` returns `true`.
+
+  It is not necessary for implementations to ensure that changes to `disabled`
+  are immediately visible to callers of `Enabled`.
+  However, the changes MUST be eventually visible.
 
 ### Enabled