org.apache.kafka.connect.errors.ConnectException: Task already exists in this worker





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















How to fix this?




org.apache.kafka.connect.errors.ConnectException: Task already exists in this worker




We have set up kafka and kafka-connect on single server and all my connector are giving above error.



Also after restarting the connect service all the workers are stuck in unassigned mode.










share|improve this question

























  • Which connector are you trying to use? Where are you seeing that? In the /status endpoint of the connector or when you POST the config? Can you please check your worker logs on the server? Also, not important here, but Kafka Connect should ideally not run on the same machine as the broker (you wouldn't run other consumer/producers on your brokers)

    – cricket_007
    Nov 17 '18 at 20:44




















0















How to fix this?




org.apache.kafka.connect.errors.ConnectException: Task already exists in this worker




We have set up kafka and kafka-connect on single server and all my connector are giving above error.



Also after restarting the connect service all the workers are stuck in unassigned mode.










share|improve this question

























  • Which connector are you trying to use? Where are you seeing that? In the /status endpoint of the connector or when you POST the config? Can you please check your worker logs on the server? Also, not important here, but Kafka Connect should ideally not run on the same machine as the broker (you wouldn't run other consumer/producers on your brokers)

    – cricket_007
    Nov 17 '18 at 20:44
















0












0








0








How to fix this?




org.apache.kafka.connect.errors.ConnectException: Task already exists in this worker




We have set up kafka and kafka-connect on single server and all my connector are giving above error.



Also after restarting the connect service all the workers are stuck in unassigned mode.










share|improve this question
















How to fix this?




org.apache.kafka.connect.errors.ConnectException: Task already exists in this worker




We have set up kafka and kafka-connect on single server and all my connector are giving above error.



Also after restarting the connect service all the workers are stuck in unassigned mode.







apache-kafka apache-kafka-connect






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 17 '18 at 20:42









cricket_007

84.5k1147119




84.5k1147119










asked Nov 16 '18 at 16:12









Raghav salotraRaghav salotra

305314




305314













  • Which connector are you trying to use? Where are you seeing that? In the /status endpoint of the connector or when you POST the config? Can you please check your worker logs on the server? Also, not important here, but Kafka Connect should ideally not run on the same machine as the broker (you wouldn't run other consumer/producers on your brokers)

    – cricket_007
    Nov 17 '18 at 20:44





















  • Which connector are you trying to use? Where are you seeing that? In the /status endpoint of the connector or when you POST the config? Can you please check your worker logs on the server? Also, not important here, but Kafka Connect should ideally not run on the same machine as the broker (you wouldn't run other consumer/producers on your brokers)

    – cricket_007
    Nov 17 '18 at 20:44



















Which connector are you trying to use? Where are you seeing that? In the /status endpoint of the connector or when you POST the config? Can you please check your worker logs on the server? Also, not important here, but Kafka Connect should ideally not run on the same machine as the broker (you wouldn't run other consumer/producers on your brokers)

– cricket_007
Nov 17 '18 at 20:44







Which connector are you trying to use? Where are you seeing that? In the /status endpoint of the connector or when you POST the config? Can you please check your worker logs on the server? Also, not important here, but Kafka Connect should ideally not run on the same machine as the broker (you wouldn't run other consumer/producers on your brokers)

– cricket_007
Nov 17 '18 at 20:44














1 Answer
1






active

oldest

votes


















1














I just had this error myself and mananged to fix it by SSH-ing to the Connect server reporting the error, stopping all running instances of Kafka Connect e.g. sudo systemctl stop kafka-connect, or SIGTERM it



# ps -ef | grep java | grep Connect | grep -v grep | awk '{print $2}'
<id>
# kill <id>


Then start it back up via systemctl start kafka-connect, or connect-distributed



Alternatively, you could also try HTTP DELETE & re-POST the connector config.






share|improve this answer
























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53341626%2forg-apache-kafka-connect-errors-connectexception-task-already-exists-in-this-wo%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    I just had this error myself and mananged to fix it by SSH-ing to the Connect server reporting the error, stopping all running instances of Kafka Connect e.g. sudo systemctl stop kafka-connect, or SIGTERM it



    # ps -ef | grep java | grep Connect | grep -v grep | awk '{print $2}'
    <id>
    # kill <id>


    Then start it back up via systemctl start kafka-connect, or connect-distributed



    Alternatively, you could also try HTTP DELETE & re-POST the connector config.






    share|improve this answer




























      1














      I just had this error myself and mananged to fix it by SSH-ing to the Connect server reporting the error, stopping all running instances of Kafka Connect e.g. sudo systemctl stop kafka-connect, or SIGTERM it



      # ps -ef | grep java | grep Connect | grep -v grep | awk '{print $2}'
      <id>
      # kill <id>


      Then start it back up via systemctl start kafka-connect, or connect-distributed



      Alternatively, you could also try HTTP DELETE & re-POST the connector config.






      share|improve this answer


























        1












        1








        1







        I just had this error myself and mananged to fix it by SSH-ing to the Connect server reporting the error, stopping all running instances of Kafka Connect e.g. sudo systemctl stop kafka-connect, or SIGTERM it



        # ps -ef | grep java | grep Connect | grep -v grep | awk '{print $2}'
        <id>
        # kill <id>


        Then start it back up via systemctl start kafka-connect, or connect-distributed



        Alternatively, you could also try HTTP DELETE & re-POST the connector config.






        share|improve this answer













        I just had this error myself and mananged to fix it by SSH-ing to the Connect server reporting the error, stopping all running instances of Kafka Connect e.g. sudo systemctl stop kafka-connect, or SIGTERM it



        # ps -ef | grep java | grep Connect | grep -v grep | awk '{print $2}'
        <id>
        # kill <id>


        Then start it back up via systemctl start kafka-connect, or connect-distributed



        Alternatively, you could also try HTTP DELETE & re-POST the connector config.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 17 '18 at 22:55









        cricket_007cricket_007

        84.5k1147119




        84.5k1147119
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53341626%2forg-apache-kafka-connect-errors-connectexception-task-already-exists-in-this-wo%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Florida Star v. B. J. F.

            Error while running script in elastic search , gateway timeout

            Adding quotations to stringified JSON object values