JimGalasyn commented on code in PR #16313:
URL: https://github.com/apache/kafka/pull/16313#discussion_r1638979649
##########
docs/streams/upgrade-guide.html:
##########
@@ -303,6 +303,61 @@ <h3><a id="streams_api_changes_350"
href="#streams_api_changes_350">Streams API
adds a new config <code>default.client.supplier</code> that allows to
use a custom <code>KafkaClientSupplier</code> without any code changes.
</p>
+ <h3><a id="streams_api_changes_320"
href="#streams_api_changes_320">Streams API changes in 3.2.0</a></h3>
+ <p>
+ RocksDB offers many metrics which are critical to monitor and tune its
performance. Kafka Streams started to make RocksDB metrics accessible
+ like any other Kafka metric via <a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-471%3A+Expose+RocksDB+Metrics+in+Kafka+Streams";>KIP-471</a>
in 2.4.0 release.
+ However, the KIP was only partially implemented, and is now completed
with the 3.2.0 release.
+ For a full list of available RocksDB metrics, please consult the <a
href="/{{version}}/documentation/#kafka_streams_client_monitoring">monitoring
documentation</a>.
+ </p>
+
+ <p>
+ Kafka Streams ships with RocksDB and in-memory store implementations
and user can pick which one to use.
Review Comment:
```suggestion
Kafka Streams ships with RocksDB and in-memory store implementations
and users can pick which one to use.
```
--
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: jira-unsubscr...@kafka.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
