[
https://issues.apache.org/jira/browse/KAFKA-13631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Schall updated KAFKA-13631:
---------------------------------
Description:
* S{color:#172b4d}etup: kafka with version 2.8.1 with scala version 2.13{color}
* {color:#172b4d}Start zookeeper, kafka server and
kafka-connect-distributed{color}
* {color:#172b4d}Create a FileStreamSinkConnector (e.g. via the following
request:{color}
{code:java}
curl --location --request PUT
'localhost:8083/connectors/local-file-sink/config' \
--header 'Content-Type: application/json' \
--data-raw '{
"name":"local-file-sink",
"connector.class":"FileStreamSink",
"tasks.max":1,
"file":"test.sink.txt",
"topics":"connect-test"
}'{code}
* {color:#172b4d}shutdown the connector via the api as followed:{color}
{code:java}
curl --location --request DELETE 'localhost:8083/connectors/local-file-sink/'
{code}
In the log of connect-distributed will appear the following warnings (for
complete log see attachement, warning appears in l.2103ff. ):
{color:#172b4d}[2022-01-28 10:52:42,246] INFO Stopping connector
local-file-sink (org.apache.kafka.connect.runtime.Worker:382)
[2022-01-28 10:52:42,247] WARN Ignoring stop request for unowned connector
local-file-sink (org.apache.kafka.connect.runtime.Worker:385)
[2022-01-28 10:52:42,247] WARN Ignoring await stop request for non-present
connector local-file-sink (org.apache.kafka.connect.runtime.Worker:410){color}
{color:#172b4d}In the log it looks like, it is tried twice to stop the
connector. The first attempt is successful (log l.2096ff.), but the second
attempt causes the warning, as the connector is already stopped. It is not
traceable for us why the connector is tried to stop twice, but it seems to be
wrong.{color}
{color:#172b4d}Furthermore, the problem also occurs with any other connector we
tried so far, so it is not specific to the FileStreamSinkConnector.{color}
was:
* S{color:#172b4d}etup: kafka with version 2.8.1 with scala version 2.13{color}
* {color:#172b4d}Start zookeeper, kafka server and
kafka-connect-distributed{color}
* {color:#172b4d}Create a FileStreamSinkConnector (e.g. via the following
request:{color}
{color:#000000}curl --location --request PUT
{color}{color:#2a00ff}'localhost:8083/connectors/local-file-sink/config'{color}{color:#000000}
\
--header {color}{color:#2a00ff}'Content-Type:
application/json'{color}{color:#000000} \
--data-raw {color}{color:#2a00ff}'{{color}
{color:#2a00ff}"name"{color}{color:#000000}:{color}{color:#2a00ff}"local-file-sink"{color}{color:#000000},{color}
{color:#2a00ff}"connector.class"{color}{color:#000000}:{color}{color:#2a00ff}"FileStreamSink"{color}{color:#000000},{color}
{color:#2a00ff}"tasks.max"{color}{color:#000000}:{color}{color:#098658}1{color}{color:#000000},{color}
{color:#2a00ff}"file"{color}{color:#000000}:{color}{color:#2a00ff}"test.sink.txt"{color}{color:#000000},{color}
{color:#2a00ff}"topics"{color}{color:#000000}:{color}{color:#2a00ff}"connect-test"{color}
}'
* {color:#172b4d}shutdown the connector via the api as followed:{color}
curl --location --request DELETE
'{color:#2a00ff}localhost:8083/connectors/local-file-sink/'{color}
In the log of connect-distributed will appear the following warnings (for
complete log see attachement, warning appears in l.2103ff. ):
{color:#172b4d}[2022-01-28 10:52:42,246] INFO Stopping connector
local-file-sink (org.apache.kafka.connect.runtime.Worker:382)
[2022-01-28 10:52:42,247] WARN Ignoring stop request for unowned connector
local-file-sink (org.apache.kafka.connect.runtime.Worker:385)
[2022-01-28 10:52:42,247] WARN Ignoring await stop request for non-present
connector local-file-sink (org.apache.kafka.connect.runtime.Worker:410){color}
{color:#172b4d}In the log it looks like, it is tried twice to stop the
connector. The first attempt is successful (log l.2096ff.), but the second
attempt causes the warning, as the connector is already stopped. It is not
traceable for us why the connector is tried to stop twice, but it seems to be
wrong.{color}
{color:#172b4d}Furthermore, the problem also occurs with any other connector we
tried so far, so it is not specific to the FileStreamSinkConnector.{color}
> Warning "Ignoring await stop request for non-present connector..." when
> shutting down connector via API in distributed mode
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-13631
> URL: https://issues.apache.org/jira/browse/KAFKA-13631
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 2.8.1
> Reporter: Simon Schall
> Priority: Minor
> Attachments: connect-1.log
>
>
> * S{color:#172b4d}etup: kafka with version 2.8.1 with scala version
> 2.13{color}
> * {color:#172b4d}Start zookeeper, kafka server and
> kafka-connect-distributed{color}
> * {color:#172b4d}Create a FileStreamSinkConnector (e.g. via the following
> request:{color}
> {code:java}
> curl --location --request PUT
> 'localhost:8083/connectors/local-file-sink/config' \
> --header 'Content-Type: application/json' \
> --data-raw '{
> "name":"local-file-sink",
> "connector.class":"FileStreamSink",
> "tasks.max":1,
> "file":"test.sink.txt",
> "topics":"connect-test"
> }'{code}
>
> * {color:#172b4d}shutdown the connector via the api as followed:{color}
> {code:java}
> curl --location --request DELETE 'localhost:8083/connectors/local-file-sink/'
> {code}
>
> In the log of connect-distributed will appear the following warnings (for
> complete log see attachement, warning appears in l.2103ff. ):
> {color:#172b4d}[2022-01-28 10:52:42,246] INFO Stopping connector
> local-file-sink (org.apache.kafka.connect.runtime.Worker:382)
> [2022-01-28 10:52:42,247] WARN Ignoring stop request for unowned connector
> local-file-sink (org.apache.kafka.connect.runtime.Worker:385)
> [2022-01-28 10:52:42,247] WARN Ignoring await stop request for non-present
> connector local-file-sink (org.apache.kafka.connect.runtime.Worker:410){color}
>
> {color:#172b4d}In the log it looks like, it is tried twice to stop the
> connector. The first attempt is successful (log l.2096ff.), but the second
> attempt causes the warning, as the connector is already stopped. It is not
> traceable for us why the connector is tried to stop twice, but it seems to be
> wrong.{color}
> {color:#172b4d}Furthermore, the problem also occurs with any other connector
> we tried so far, so it is not specific to the FileStreamSinkConnector.{color}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
