Re: [PR] KAFKA-15649: Handle directory failure timeout [kafka]

2024-05-23 Thread via GitHub
soarez merged PR #15697: URL: https://github.com/apache/kafka/pull/15697 -- 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:

Re: [PR] KAFKA-15649: Handle directory failure timeout [kafka]

2024-05-23 Thread via GitHub
viktorsomogyi commented on PR #15697: URL: https://github.com/apache/kafka/pull/15697#issuecomment-2127130632 @soarez thanks for the info. I addressed your comment. Do you have anything more to add or are we good to go? -- This is an automated message from the Apache Git Service. To

Re: [PR] KAFKA-15649: Handle directory failure timeout [kafka]

2024-05-09 Thread via GitHub
soarez commented on code in PR #15697: URL: https://github.com/apache/kafka/pull/15697#discussion_r1593094798 ## core/src/main/scala/kafka/server/ReplicaManager.scala: ## @@ -2466,7 +2467,6 @@ class ReplicaManager(val config: KafkaConfig, s"for partitions

Re: [PR] KAFKA-15649: Handle directory failure timeout [kafka]

2024-05-07 Thread via GitHub
viktorsomogyi commented on PR #15697: URL: https://github.com/apache/kafka/pull/15697#issuecomment-2098821932 @soarez at the end I chose the shortcut regarding detecting leaders before shutdown. The reason is complex as the solution that would be required for this is complex too. So on

Re: [PR] KAFKA-15649: Handle directory failure timeout [kafka]

2024-04-18 Thread via GitHub
viktorsomogyi commented on PR #15697: URL: https://github.com/apache/kafka/pull/15697#issuecomment-2064216189 Rebased on latest trunk as there were some conflicts. Addressed some of the comments but there are 2 things I need to investigate: * `LogDirFailureTest` fails in `@AfterAll`

Re: [PR] KAFKA-15649: Handle directory failure timeout [kafka]

2024-04-18 Thread via GitHub
viktorsomogyi commented on code in PR #15697: URL: https://github.com/apache/kafka/pull/15697#discussion_r1570907841 ## core/src/main/scala/kafka/server/KafkaConfig.scala: ## @@ -528,6 +529,10 @@ object KafkaConfig { "If log.message.timestamp.type=CreateTime, the message

Re: [PR] KAFKA-15649: Handle directory failure timeout [kafka]

2024-04-15 Thread via GitHub
mimaison commented on code in PR #15697: URL: https://github.com/apache/kafka/pull/15697#discussion_r1565973156 ## core/src/main/scala/kafka/server/KafkaConfig.scala: ## @@ -870,6 +875,7 @@ object KafkaConfig { .define(CreateTopicPolicyClassNameProp, CLASS, null, LOW,

Re: [PR] KAFKA-15649: Handle directory failure timeout [kafka]

2024-04-12 Thread via GitHub
soarez commented on code in PR #15697: URL: https://github.com/apache/kafka/pull/15697#discussion_r1562612304 ## core/src/main/scala/kafka/server/BrokerLifecycleManager.scala: ## @@ -507,6 +522,7 @@ class BrokerLifecycleManager( if (errorCode == Errors.NONE) {

Re: [PR] KAFKA-15649: Handle directory failure timeout [kafka]

2024-04-11 Thread via GitHub
viktorsomogyi commented on PR #15697: URL: https://github.com/apache/kafka/pull/15697#issuecomment-2049303060 Rebased it due to conflicts. -- 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

[PR] KAFKA-15649: Handle directory failure timeout [kafka]

2024-04-11 Thread via GitHub
viktorsomogyi opened a new pull request, #15697: URL: https://github.com/apache/kafka/pull/15697 A broker that is unable to communicate with the controller will shut down after the configurable log.dir.failure.timeout.ms. The implementation adds a new event to the Kafka EventQueue.