davidradl commented on code in PR #25884:
URL: https://github.com/apache/flink/pull/25884#discussion_r1910600361
##########
docs/content/docs/ops/metrics.md:
##########
@@ -1526,6 +1526,41 @@ Note that for failed checkpoints, metrics are updated on
a best efforts basis an
### RocksDB
Certain RocksDB native metrics are available but disabled by default, you can
find full documentation [here]({{< ref "docs/deployment/config"
>}}#rocksdb-native-metrics)
+### ForStDB
+<table class="table table-bordered">
+ <thead>
+ <tr>
+ <th class="text-left" style="width: 18%">Scope</th>
+ <th class="text-left" style="width: 26%">Metrics</th>
+ <th class="text-left" style="width: 48%">Description</th>
+ <th class="text-left" style="width: 8%">Type</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <th rowspan="4"><strong>Task/Operator</strong></th>
+ <td>forst.fileCache.hit</td>
+ <td>The hit count of ForSt state backend cache.</td>
Review Comment:
> > Do the cache entries get invalidated at any time , due to size or time?
>
> Yes.
>
> > Is this something we can capture in the metrics?
>
> Something means what? could you give an example?
>
> > Can the counters be reset - would this be useful?
>
> The counter can not be reset while the job is running, this counter is a
common counter defined in Flink, if you want to make the counter resettable, a
discussion may need to be started.
@fredia thanks for your reply. Sorry for the bassc questions. I am not sure
how the invalidation occurs - can you count the number of invalidations in a
similar way to the hits and misses.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
