[jira] [Assigned] (KAFKA-15547) Thread leak in MirrorMakerConfigTest#testClientConfigProperties

[ https://issues.apache.org/jira/browse/KAFKA-15547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalpesh Patel reassigned KAFKA-15547: - Assignee: Kalpesh Patel > Thread leak in

[jira] [Created] (KAFKA-15547) Thread leak in MirrorMakerConfigTest#testClientConfigProperties

Kalpesh Patel created KAFKA-15547: - Summary: Thread leak in MirrorMakerConfigTest#testClientConfigProperties Key: KAFKA-15547 URL: https://issues.apache.org/jira/browse/KAFKA-15547 Project: Kafka

[jira] [Commented] (KAFKA-13139) Empty response after requesting to restart a connector without the tasks results in NPE

[ https://issues.apache.org/jira/browse/KAFKA-13139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17388332#comment-17388332 ] Kalpesh Patel commented on KAFKA-13139: --- Thanks a lot [~rhauch] and [~kkonstantine] for taking

[jira] [Updated] (KAFKA-13035) Kafka Connect: Update documentation for POST /connectors/(string: name)/restart to include task Restart behavior

[ https://issues.apache.org/jira/browse/KAFKA-13035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalpesh Patel updated KAFKA-13035: -- Component/s: KafkaConnect > Kafka Connect: Update documentation for POST /connectors/(string:

[jira] [Assigned] (KAFKA-13035) Kafka Connect: Update documentation for POST /connectors/(string: name)/restart to include task Restart behavior

[ https://issues.apache.org/jira/browse/KAFKA-13035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalpesh Patel reassigned KAFKA-13035: - Assignee: Kalpesh Patel > Kafka Connect: Update documentation for POST

[jira] [Updated] (KAFKA-13035) Kafka Connect: Update documentation for POST /connectors/(string: name)/restart to include task Restart behavior

[ https://issues.apache.org/jira/browse/KAFKA-13035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalpesh Patel updated KAFKA-13035: -- Description: KAFKA-4793 updated the behavior of POST /connectors/(string: name)/restart based

[jira] [Created] (KAFKA-13035) Kafka Connect: Update documentation for POST /connectors/(string: name)/restart to include task Restart behavior

Kalpesh Patel created KAFKA-13035: - Summary: Kafka Connect: Update documentation for POST /connectors/(string: name)/restart to include task Restart behavior Key: KAFKA-13035 URL:

[jira] [Commented] (KAFKA-12482) Remove deprecated rest.host.name and rest.port Connect worker configs

[ https://issues.apache.org/jira/browse/KAFKA-12482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17356532#comment-17356532 ] Kalpesh Patel commented on KAFKA-12482: --- Thanks, I plan to take care of this in the next few

[jira] [Commented] (KAFKA-4793) Kafka Connect: POST /connectors/(string: name)/restart doesn't start failed tasks

[ https://issues.apache.org/jira/browse/KAFKA-4793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355976#comment-17355976 ] Kalpesh Patel commented on KAFKA-4793: -- (y) > Kafka Connect: POST /connectors/(string:

[jira] [Assigned] (KAFKA-4793) Kafka Connect: POST /connectors/(string: name)/restart doesn't start failed tasks

[ https://issues.apache.org/jira/browse/KAFKA-4793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalpesh Patel reassigned KAFKA-4793: Assignee: Kalpesh Patel (was: Randall Hauch) > Kafka Connect: POST /connectors/(string:

[jira] [Commented] (KAFKA-4793) Kafka Connect: POST /connectors/(string: name)/restart doesn't start failed tasks

[ https://issues.apache.org/jira/browse/KAFKA-4793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355967#comment-17355967 ] Kalpesh Patel commented on KAFKA-4793: -- [~rhauch] this is a great proposal, would it be possible for

[jira] [Updated] (KAFKA-9560) Connector::validate is utilized concurrently by the framework, but not documented as thread-safe

[ https://issues.apache.org/jira/browse/KAFKA-9560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalpesh Patel updated KAFKA-9560: - Description: Requests to the {{PUT /connector-plugins/\{connectorType}/config/validate}}

[jira] [Updated] (KAFKA-12704) Concurrent calls to AbstractHerder::getConnector can potentially create two connector instances

[ https://issues.apache.org/jira/browse/KAFKA-12704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalpesh Patel updated KAFKA-12704: -- Description: As discovered in KAFKA-9560, concurrent requests to the {{PUT

[jira] [Updated] (KAFKA-12704) Concurrent calls to AbstractHerder::getConnector can potentially create two connector instances

[ https://issues.apache.org/jira/browse/KAFKA-12704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalpesh Patel updated KAFKA-12704: -- Description: Concurrent requests to the {{PUT

[jira] [Assigned] (KAFKA-12704) Concurrent calls to AbstractHerder::getConnector can potentially create two connector instances

[ https://issues.apache.org/jira/browse/KAFKA-12704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalpesh Patel reassigned KAFKA-12704: - Assignee: Kalpesh Patel > Concurrent calls to AbstractHerder::getConnector can

[jira] [Created] (KAFKA-12704) Concurrent calls to AbstractHerder::getConnector can potentially create two connector instances

Kalpesh Patel created KAFKA-12704: - Summary: Concurrent calls to AbstractHerder::getConnector can potentially create two connector instances Key: KAFKA-12704 URL: https://issues.apache.org/jira/browse/KAFKA-12704

[jira] [Assigned] (KAFKA-8605) Warn users when they have same connector in their plugin-path more than once

[ https://issues.apache.org/jira/browse/KAFKA-8605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalpesh Patel reassigned KAFKA-8605: Assignee: Kalpesh Patel > Warn users when they have same connector in their plugin-path

[jira] [Issue Comment Deleted] (KAFKA-9988) Connect incorrectly logs that task has failed when one takes too long to shutdown

[ https://issues.apache.org/jira/browse/KAFKA-9988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalpesh Patel updated KAFKA-9988: - Comment: was deleted (was: https://github.com/apache/kafka/pull/10503/) > Connect incorrectly

[jira] [Assigned] (KAFKA-10231) Broken Kafka Connect node to node communication if invalid hostname is in place

[ https://issues.apache.org/jira/browse/KAFKA-10231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalpesh Patel reassigned KAFKA-10231: - Assignee: Kalpesh Patel > Broken Kafka Connect node to node communication if invalid

[jira] [Assigned] (KAFKA-12380) Executor in Connect's Worker is not shut down when the worker is

[ https://issues.apache.org/jira/browse/KAFKA-12380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalpesh Patel reassigned KAFKA-12380: - Assignee: (was: Kalpesh Patel) > Executor in Connect's Worker is not shut down

[jira] [Assigned] (KAFKA-12380) Executor in Connect's Worker is not shut down when the worker is

[ https://issues.apache.org/jira/browse/KAFKA-12380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalpesh Patel reassigned KAFKA-12380: - Assignee: Kalpesh Patel > Executor in Connect's Worker is not shut down when the

[jira] [Assigned] (KAFKA-9988) Connect incorrectly logs that task has failed when one takes too long to shutdown

[ https://issues.apache.org/jira/browse/KAFKA-9988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalpesh Patel reassigned KAFKA-9988: Assignee: Kalpesh Patel > Connect incorrectly logs that task has failed when one takes