rmetzger commented on a change in pull request #15321:
URL: https://github.com/apache/flink/pull/15321#discussion_r599911357
##########
File path: docs/content/docs/deployment/elastic_scaling.md
##########
@@ -104,6 +104,7 @@ Since Reactive Mode is a new, experimental feature, not all
features supported b
- **No support for [local recovery]({{< ref
"docs/ops/state/large_state_tuning">}}#task-local-recovery)**: Local recovery
is a feature that schedules tasks to machines so that the state on that machine
gets re-used if possible. The lack of this feature means that Reactive Mode
will always need to download the entire state from the checkpoint storage.
- **No support for local failover**: Local failover means that the scheduler
is able to restart parts ("regions" in Flink's internals) of a failed job,
instead of the entire job. This limitation impacts only recovery time of
embarrassingly parallel jobs: Flink's default scheduler can restart failed
parts, while Reactive Mode will restart the entire job.
- **Limited integration with Flink's Web UI**: Reactive Mode allows that a
job's parallelism can change over its lifetime. The web UI only shows the
current parallelism the job.
+- **Limited Job metrics**: With the exception of `numRestarts` all
[availability]({{< ref "docs/ops/metrics" >}}#availability) and
[checkpointing]({{< ref "docs/ops/metrics" >}}#checkpointing) metrics with the
`Job` scope are not working correctly.
Review comment:
```suggestion
- **Limited Job metrics**: With the exception of `numRestarts` all
[availability]({{< ref "docs/ops/metrics" >}}#availability) and
[checkpointing]({{< ref "docs/ops/metrics" >}}#checkpointing) metrics with the
`Job` scope are not working correctly.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
