Sematext Cloud running on AWS infrastructure
Sematext Cloud running on your infrastructure
Infrastructure, application, container monitoring and alerting
Real User Monitoring
Enhnance your site performance with data from actual site visitors
Log Management â hosted ELK stack in the cloud
APM / Tracing
Optimize end-to-end application performance
Check out whatâs new on Sematext Cloud
Application Performance Monitoring
Metrics and Logs
Open Source Agents
Logsene Log Management
Solr & Lucene Consulting
Solr & Lucene Support
Matthias J. Sax
Vahid S Hashemian
Alan D. Cabrera
mail # dev
mail # user
newest on top
oldest on top
. Results from
Loading phrases to help you
refine your search...
[KAFKA-4453] add request prioritization
...Today all requests (client requests, broker requests, controller requests) to a broker are put into the same queue. They all have the same priority. So a backlog of requests ahead of the con...
, 2018-09-13, 08:56
[KAFKA-6082] consider fencing zookeeper updates with controller epoch zkVersion
... Kafka controller may fail to function properly (even after repeated controller movement) due to the following sequence of events: User requests topic deletion Controller A deletes the parti...
, 2018-09-07, 21:20
[KAFKA-1921] Delete offsets for a group with kafka offset storage
...There is currently no way to delete offsets for a consumer group when using kafka offset storage....
, 2018-08-23, 06:18
[KAFKA-3494] mbeans overwritten with identical clients on a single jvm
...Quotas today are implemented on a (client-id, broker) granularity. I think one of the motivating factors for using a simple quota id was to allow for flexibility in the granularity of the qu...
, 2018-08-03, 18:04
[KAFKA-6014] new consumer mirror maker halts after committing offsets to a deleted topic
...New consumer throws an unexpected KafkaException when trying to commit to a topic that has been deleted. MirrorMaker.commitOffsets doesn't attempt to catch the KafkaException and just kills ...
, 2018-07-26, 18:11
[KAFKA-4893] async topic deletion conflicts with max topic length
...As per the documentation, topics can be only 249 characters long to line up with typical filesystem limitations:Each sharded partition log is placed into its own folder under the Kafka log d...
, 2018-07-13, 15:35
[KAFKA-1942] ConsumerGroupCommand does not show offset information in ZK for deleted topic
...Let's say group g consumes from topic t. If we delete topic t using kafka-topics.sh and then try to describe group g using ConsumerGroupCommand, it won't show any of the partition rows for t...
, 2018-06-15, 17:51
[KAFKA-5029] cleanup javadocs and logging
...Remove state change logger, splitting it up into the controller logs or broker logs....
, 2018-06-06, 12:02
[KAFKA-4753] KafkaConsumer susceptible to FetchResponse starvation
...FetchResponse starvation here means that the KafkaConsumer repeatedly fails to fully form FetchResponses within the request timeout from a subset of the brokers its fetching from while Fetch...
, 2018-02-24, 05:50
[KAFKA-5083] always leave the last surviving member of the ISR in ZK
...Currently we erase ISR membership if the replica to be removed from the ISR is the last surviving member of the ISR and unclean leader election is enabled for the corresponding topic.We shou...
, 2018-01-18, 20:34
Brooklyn, NY USA
© Sematext Group. All rights reserved
Terms Of Service