[
https://issues.apache.org/jira/browse/KAFKA-15823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luke Chen resolved KAFKA-15823.
---
Resolution: Fixed
> NodeToControllerChannelManager: authentication error prevents controller
>
[
https://issues.apache.org/jira/browse/KAFKA-16323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luke Chen resolved KAFKA-16323.
---
Fix Version/s: 3.8.0
3.7.1
Resolution: Fixed
> Failing test: fix
Hi all,
While testing the patch [1], realised that introducing a
new REMOTE_STORAGE_NOT_READY error-code
is not compatible with the consumer. Consumer does not retry the FETCH
request for all the retriable
exceptions [2] instead it retries only for specific error codes. Dropping
the KIP-1007
Hi all,
While testing the patch [1], realised that introducing a
new REMOTE_STORAGE_NOT_READY error-code
is not compatible with the consumer. Consumer does not retry the FETCH
request for all the retriable
exceptions [2] instead it retries only for specific error codes. Dropping
the KIP-1007
Hi Matthias,
> For the oldest iterator metric, I would propose something simple like
> `iterator-opened-ms` and it would just be the actual timestamp when the
> iterator was opened. I don't think we need to compute the actual age,
> but user can to this computation themselves?
That works for me;
Kamal Chandraprakash created KAFKA-16452:
Summary: Bound highwatermark offset to range b/w
local-log-start-offset and log-end-offset
Key: KAFKA-16452
URL: https://issues.apache.org/jira/browse/KAFKA-16452
The time window thing was just an idea. Happy to drop it.
For the oldest iterator metric, I would propose something simple like
`iterator-opened-ms` and it would just be the actual timestamp when the
iterator was opened. I don't think we need to compute the actual age,
but user can to this
Two more follow up thoughts:
(1) I am still not a big fan of the boolean parameter we introduce. Did
you consider to use different method names, like
`addReadOnlyGlobalStore()` (for the optimized method, that would not
reprocess data on restore), and maybe add `addModifiableGlobalStore()`
