Commit 963d54a
authored
KAFKA-19945: Always set status field in StreamsGroupHeartbeat response (#21031)
The status field should always set in the response, even when empty, to
ensure that the status gets reset on the client.
We are not doing this due to an oversight - it is defined as nullable,
and it is null when not set. So status does not clear correctly on the
client, which ignores the field if it's null.
This can cause the streams application to incorrectly timeout, if the
source topic does not exist when the application is first started, but
it is created after the application started. Otherwise, there is no
noticable difference.
Reviewers: Lucas Brutschy <[email protected]>1 parent 7c4ae09 commit 963d54a
File tree
4 files changed
+139
-39
lines changed- clients/src/main/resources/common/message
- core/src/test/scala/unit/kafka/server
- group-coordinator/src
- main/java/org/apache/kafka/coordinator/group
- test/java/org/apache/kafka/coordinator/group
4 files changed
+139
-39
lines changedLines changed: 2 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
53 | 53 | | |
54 | 54 | | |
55 | 55 | | |
56 | | - | |
57 | | - | |
| 56 | + | |
| 57 | + | |
58 | 58 | | |
59 | 59 | | |
60 | 60 | | |
| |||
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
209 | 209 | | |
210 | 210 | | |
211 | 211 | | |
212 | | - | |
| 212 | + | |
213 | 213 | | |
214 | 214 | | |
215 | 215 | | |
| |||
Lines changed: 3 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
2153 | 2153 | | |
2154 | 2154 | | |
2155 | 2155 | | |
2156 | | - | |
2157 | | - | |
2158 | | - | |
| 2156 | + | |
2159 | 2157 | | |
2160 | 2158 | | |
2161 | 2159 | | |
| |||
4215 | 4213 | | |
4216 | 4214 | | |
4217 | 4215 | | |
4218 | | - | |
| 4216 | + | |
| 4217 | + | |
4219 | 4218 | | |
4220 | 4219 | | |
4221 | 4220 | | |
| |||
0 commit comments