You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kafka.apache.org by gu...@apache.org on 2018/04/24 22:40:20 UTC
[kafka] branch trunk updated: KAFKA-6376: Document skipped records
metrics changes (#4922)
This is an automated email from the ASF dual-hosted git repository.
guozhang pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/kafka.git
The following commit(s) were added to refs/heads/trunk by this push:
new 12a0f46 KAFKA-6376: Document skipped records metrics changes (#4922)
12a0f46 is described below
commit 12a0f46895e730f6a3a4c5fc311c206f6d8219e5
Author: John Roesler <vv...@users.noreply.github.com>
AuthorDate: Tue Apr 24 17:40:16 2018 -0500
KAFKA-6376: Document skipped records metrics changes (#4922)
Reviewers: Bill Bejeck <bi...@confluent.io>, Guozhang Wang <wa...@gmail.com>
---
docs/ops.html | 7 ++++++-
docs/streams/upgrade-guide.html | 31 +++++++++++++++++++++++++++++++
2 files changed, 37 insertions(+), 1 deletion(-)
diff --git a/docs/ops.html b/docs/ops.html
index 6ffe976..450a268 100644
--- a/docs/ops.html
+++ b/docs/ops.html
@@ -1353,7 +1353,12 @@ All the following metrics have a recording level of ``info``:
</tr>
<tr>
<td>skipped-records-rate</td>
- <td>The average number of skipped records per second. </td>
+ <td>The average number of skipped records per second.</td>
+ <td>kafka.streams:type=stream-metrics,client-id=([-.\w]+)</td>
+ </tr>
+ <tr>
+ <td>skipped-records-total</td>
+ <td>The total number of skipped records.</td>
<td>kafka.streams:type=stream-metrics,client-id=([-.\w]+)</td>
</tr>
</tbody>
diff --git a/docs/streams/upgrade-guide.html b/docs/streams/upgrade-guide.html
index 7ffafb5..565bd0b 100644
--- a/docs/streams/upgrade-guide.html
+++ b/docs/streams/upgrade-guide.html
@@ -102,6 +102,37 @@
<!-- TODO: verify release verion and update `id` and `href` attributes (also at other places that link to this headline) -->
<h3><a id="streams_api_changes_120" href="#streams_api_changes_120">Streams API changes in 1.2.0</a></h3>
<p>
+ We have removed the <code>skippedDueToDeserializationError-rate</code> and <code>skippedDueToDeserializationError-total</code> metrics.
+ Deserialization errors, and all other causes of record skipping, are now accounted for in the pre-existing metrics
+ <code>skipped-records-rate</code> and <code>skipped-records-total</code>. When a record is skipped, the event is
+ now logged at WARN level. If these warnings become burdensome, we recommend explicitly filtering out unprocessable
+ records instead of depending on record skipping semantics. For more details, see
+ <a href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-274%3A+Kafka+Streams+Skipped+Records+Metrics">KIP-274</a>.
+ As of right now, the potential causes of skipped records are:
+ </p>
+ <ul>
+ <li><code>null</code> keys in table sources</li>
+ <li><code>null</code> keys in table-table inner/left/outer/right joins</li>
+ <li><code>null</code> keys or values in stream-table joins</li>
+ <li><code>null</code> keys or values in stream-stream joins</li>
+ <li><code>null</code> keys or values in aggregations on grouped streams</li>
+ <li><code>null</code> keys or values in reductions on grouped streams</li>
+ <li><code>null</code> keys in aggregations on windowed streams</li>
+ <li><code>null</code> keys in reductions on windowed streams</li>
+ <li><code>null</code> keys in aggregations on session-windowed streams</li>
+ <li>
+ Errors producing results, when the configured <code>default.production.exception.handler</code> decides to
+ <code>CONTINUE</code> (the default is to <code>FAIL</code> and throw an exception).
+ </li>
+ <li>
+ Errors deserializing records, when the configured <code>default.deserialization.exception.handler</code>
+ decides to <code>CONTINUE</code> (the default is to <code>FAIL</code> and throw an exception).
+ This was the case previously captured in the <code>skippedDueToDeserializationError</code> metrics.
+ </li>
+ <li>Fetched records having a negative timestamp.</li>
+ </ul>
+
+ <p>
We have added support for methods in <code>ReadOnlyWindowStore</code> which allows for querying a single window's key-value pair.
For users who have customized window store implementations on the above interface, they'd need to update their code to implement the newly added method as well.
For more details, see <a href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-261%3A+Add+Single+Value+Fetch+in+Window+Stores">KIP-261</a>.
--
To stop receiving notification emails like this one, please contact
guozhang@apache.org.