[jira] [Updated] (KAFKA-13517) Update Admin::describeConfigs to allow fetching specific configurations

2022-02-20 Thread Vikas Singh (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Singh updated KAFKA-13517: Description: A list of {{ConfigResource}} class is passed as argument to

[jira] [Updated] (KAFKA-13517) Update Admin::describeConfigs to allow fetching specific configurations

2022-02-20 Thread Vikas Singh (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Singh updated KAFKA-13517: Summary: Update Admin::describeConfigs to allow fetching specific configurations (was: Add

[jira] [Created] (KAFKA-13517) Add ConfigurationKeys to ConfigResource class

2021-12-07 Thread Vikas Singh (Jira)
Vikas Singh created KAFKA-13517: --- Summary: Add ConfigurationKeys to ConfigResource class Key: KAFKA-13517 URL: https://issues.apache.org/jira/browse/KAFKA-13517 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-13432) ApiException should provide a way to capture stacktrace

2021-11-03 Thread Vikas Singh (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-13432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438341#comment-17438341 ] Vikas Singh commented on KAFKA-13432: - One simple solution can be to fill in the stacktrace based on

[jira] [Created] (KAFKA-13432) ApiException should provide a way to capture stacktrace

2021-11-03 Thread Vikas Singh (Jira)
Vikas Singh created KAFKA-13432: --- Summary: ApiException should provide a way to capture stacktrace Key: KAFKA-13432 URL: https://issues.apache.org/jira/browse/KAFKA-13432 Project: Kafka Issue

[jira] [Issue Comment Deleted] (KAFKA-9370) Return UNKNOWN_TOPIC_OR_PARTITION if topic deletion is in progress

2020-09-28 Thread Vikas Singh (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-9370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Singh updated KAFKA-9370: --- Comment: was deleted (was: https://github.com/apache/kafka/pull/9347) > Return

[jira] [Commented] (KAFKA-9370) Return UNKNOWN_TOPIC_OR_PARTITION if topic deletion is in progress

2020-09-28 Thread Vikas Singh (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-9370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17203527#comment-17203527 ] Vikas Singh commented on KAFKA-9370: https://github.com/apache/kafka/pull/9347 > Return

[jira] [Assigned] (KAFKA-10531) KafkaBasedLog can sleep for negative values

2020-09-28 Thread Vikas Singh (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-10531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Singh reassigned KAFKA-10531: --- Assignee: Vikas Singh > KafkaBasedLog can sleep for negative values >

[jira] [Created] (KAFKA-10531) KafkaBasedLog can sleep for negative values

2020-09-28 Thread Vikas Singh (Jira)
Vikas Singh created KAFKA-10531: --- Summary: KafkaBasedLog can sleep for negative values Key: KAFKA-10531 URL: https://issues.apache.org/jira/browse/KAFKA-10531 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-10175) MetadataCache::getClusterMetadata returns null for offline replicas

2020-06-16 Thread Vikas Singh (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-10175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Singh updated KAFKA-10175: Summary: MetadataCache::getClusterMetadata returns null for offline replicas (was:

[jira] [Updated] (KAFKA-10175) MetadataCache::getCluster returns null for offline replicas

2020-06-16 Thread Vikas Singh (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-10175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Singh updated KAFKA-10175: Description: This line in the code always returns null:

[jira] [Updated] (KAFKA-10175) MetadataCache::getCluster returns null for offline replicas

2020-06-16 Thread Vikas Singh (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-10175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Singh updated KAFKA-10175: Description: This line in the code always returns null:

[jira] [Updated] (KAFKA-10175) MetadataCache::getCluster returns null for offline replicas

2020-06-16 Thread Vikas Singh (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-10175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Singh updated KAFKA-10175: Description: This line in the code always returns null: >

[jira] [Created] (KAFKA-10175) MetadataCache::getCluster returns null for offline replicas

2020-06-16 Thread Vikas Singh (Jira)
Vikas Singh created KAFKA-10175: --- Summary: MetadataCache::getCluster returns null for offline replicas Key: KAFKA-10175 URL: https://issues.apache.org/jira/browse/KAFKA-10175 Project: Kafka

[jira] [Updated] (KAFKA-9254) Updating Kafka Broker configuration dynamically twice reverts log configuration to default

2020-01-24 Thread Vikas Singh (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-9254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Singh updated KAFKA-9254: --- Summary: Updating Kafka Broker configuration dynamically twice reverts log configuration to default

[jira] [Created] (KAFKA-9370) Return UNKNOWN_TOPIC_OR_PARTITION if topic deletion is in progress

2020-01-06 Thread Vikas Singh (Jira)
Vikas Singh created KAFKA-9370: -- Summary: Return UNKNOWN_TOPIC_OR_PARTITION if topic deletion is in progress Key: KAFKA-9370 URL: https://issues.apache.org/jira/browse/KAFKA-9370 Project: Kafka

[jira] [Assigned] (KAFKA-9370) Return UNKNOWN_TOPIC_OR_PARTITION if topic deletion is in progress

2020-01-06 Thread Vikas Singh (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-9370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Singh reassigned KAFKA-9370: -- Assignee: Vikas Singh > Return UNKNOWN_TOPIC_OR_PARTITION if topic deletion is in progress >

[jira] [Assigned] (KAFKA-9330) Calling AdminClient.close in the AdminClient completion callback causes deadlock

2019-12-23 Thread Vikas Singh (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-9330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Singh reassigned KAFKA-9330: -- Assignee: Vikas Singh > Calling AdminClient.close in the AdminClient completion callback

[jira] [Created] (KAFKA-9330) Calling AdminClient.close in the AdminClient completion callback causes deadlock

2019-12-23 Thread Vikas Singh (Jira)
Vikas Singh created KAFKA-9330: -- Summary: Calling AdminClient.close in the AdminClient completion callback causes deadlock Key: KAFKA-9330 URL: https://issues.apache.org/jira/browse/KAFKA-9330 Project:

[jira] [Assigned] (KAFKA-9329) KafkaController::replicasAreValid should return error

2019-12-23 Thread Vikas Singh (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-9329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Singh reassigned KAFKA-9329: -- Assignee: Vikas Singh > KafkaController::replicasAreValid should return error >

[jira] [Created] (KAFKA-9329) KafkaController::replicasAreValid should return error

2019-12-23 Thread Vikas Singh (Jira)
Vikas Singh created KAFKA-9329: -- Summary: KafkaController::replicasAreValid should return error Key: KAFKA-9329 URL: https://issues.apache.org/jira/browse/KAFKA-9329 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-9265) kafka.log.Log instances are leaking on log delete

2019-12-03 Thread Vikas Singh (Jira)
Vikas Singh created KAFKA-9265: -- Summary: kafka.log.Log instances are leaking on log delete Key: KAFKA-9265 URL: https://issues.apache.org/jira/browse/KAFKA-9265 Project: Kafka Issue Type: Bug

[jira] [Assigned] (KAFKA-9265) kafka.log.Log instances are leaking on log delete

2019-12-03 Thread Vikas Singh (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-9265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Singh reassigned KAFKA-9265: -- Assignee: Vikas Singh > kafka.log.Log instances are leaking on log delete >

[jira] [Created] (KAFKA-8988) Replace CreatePartitions request/response with automated protocol

2019-10-04 Thread Vikas Singh (Jira)
Vikas Singh created KAFKA-8988: -- Summary: Replace CreatePartitions request/response with automated protocol Key: KAFKA-8988 URL: https://issues.apache.org/jira/browse/KAFKA-8988 Project: Kafka

[jira] [Updated] (KAFKA-8813) Race condition when creating topics and changing their configuration

2019-09-03 Thread Vikas Singh (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-8813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Singh updated KAFKA-8813: --- Description: In Partition.createLog we do: {code:java} val props = stateStore.fetchTopicConfig() val

[jira] [Updated] (KAFKA-8813) Race condition when creating topics and changing their configuration

2019-09-03 Thread Vikas Singh (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-8813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Singh updated KAFKA-8813: --- Description: In Partition.createLog we do: {code:java} val props = stateStore.fetchTopicConfig() val

[jira] [Updated] (KAFKA-8813) Race condition when creating topics and changing their configuration

2019-09-03 Thread Vikas Singh (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-8813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Singh updated KAFKA-8813: --- Description: In Partition.createLog we do: {code:java} val props = stateStore.fetchTopicConfig() val

[jira] [Assigned] (KAFKA-8813) Race condition when creating topics and changing their configuration

2019-08-26 Thread Vikas Singh (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-8813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Singh reassigned KAFKA-8813: -- Assignee: Vikas Singh > Race condition when creating topics and changing their configuration

[jira] [Commented] (KAFKA-8813) Race condition when creating topics and changing their configuration

2019-08-26 Thread Vikas Singh (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-8813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916232#comment-16916232 ] Vikas Singh commented on KAFKA-8813: I am working on a fix for this issue. Expect a PR sometime this

[jira] [Commented] (KAFKA-8001) Fetch from future replica stalls when local replica becomes a leader

2019-06-19 Thread Vikas Singh (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-8001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16868153#comment-16868153 ] Vikas Singh commented on KAFKA-8001: Comment from Jason on PR that need to be taken care of:

[jira] [Commented] (KAFKA-8525) Make log in Partion non-optional

2019-06-17 Thread Vikas Singh (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-8525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16865789#comment-16865789 ] Vikas Singh commented on KAFKA-8525: #2 was already done as part of KAFKA-8457. This Jira will only

[jira] [Resolved] (KAFKA-8457) Remove Log dependency from Replica

2019-06-17 Thread Vikas Singh (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-8457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Singh resolved KAFKA-8457. Resolution: Fixed Fixed in commit 57baa4079d9fc14103411f790b9a025c9f2146a4 > Remove Log

[jira] [Assigned] (KAFKA-8525) Make log in Partion non-optional

2019-06-11 Thread Vikas Singh (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-8525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Singh reassigned KAFKA-8525: -- Assignee: Vikas Singh > Make log in Partion non-optional > >

[jira] [Created] (KAFKA-8525) Make log in Partion non-optional

2019-06-11 Thread Vikas Singh (JIRA)
Vikas Singh created KAFKA-8525: -- Summary: Make log in Partion non-optional Key: KAFKA-8525 URL: https://issues.apache.org/jira/browse/KAFKA-8525 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-8457) Remove Log dependency from Replica

2019-05-31 Thread Vikas Singh (JIRA)
Vikas Singh created KAFKA-8457: -- Summary: Remove Log dependency from Replica Key: KAFKA-8457 URL: https://issues.apache.org/jira/browse/KAFKA-8457 Project: Kafka Issue Type: Bug

[jira] [Resolved] (KAFKA-8341) AdminClient should retry coordinator lookup after NOT_COORDINATOR error

2019-05-24 Thread Vikas Singh (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-8341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Singh resolved KAFKA-8341. Resolution: Fixed fixed in commit 46a02f3231cd6d340c622636159b9f59b4b3cb6e > AdminClient should

[jira] [Created] (KAFKA-8398) NPE when unmapping files after moving log directories using AlterReplicaLogDirs

2019-05-20 Thread Vikas Singh (JIRA)
Vikas Singh created KAFKA-8398: -- Summary: NPE when unmapping files after moving log directories using AlterReplicaLogDirs Key: KAFKA-8398 URL: https://issues.apache.org/jira/browse/KAFKA-8398 Project:

[jira] [Assigned] (KAFKA-8001) Fetch from future replica stalls when local replica becomes a leader

2019-05-09 Thread Vikas Singh (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-8001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Singh reassigned KAFKA-8001: -- Assignee: Vikas Singh (was: Colin Hicks) > Fetch from future replica stalls when local