Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not stable issue: Sometimes an error occurs after starting or restarting the pipeline that transfers data from the Zendesk Source to the Destination #18

Open
SerhiiSpivak opened this issue Nov 14, 2022 · 4 comments
Labels
bug Something isn't working

Comments

@SerhiiSpivak
Copy link

SerhiiSpivak commented Nov 14, 2022

Bug description

Sometimes an error occurs after starting or restarting the pipeline that transfers data from the Zendesk Source to the Destination

The issue isn't stable

 2022-09-28T12:51:14+00:00 ERR destination acker node stopped before processing all messages error="nacked 1 messages when stopping destination acker node, some nacks failed: no DLQ handler configured" component=DestinationAckerNode node_id=2dd849e9-d967-403f-9105-ad3e98f61468-acker pipeline_id=0f70b007-80a1-4010-b1ac-f7b800c43191 stack=[{"file":"/home/serhiispivak/go/src/github.com/conduit/pkg/pipeline/stream/destination_acker.go","func":"[github.com/conduitio/conduit/pkg/pipeline/stream.(*DestinationAckerNode](http://github.com/conduitio/conduit/pkg/pipeline/stream.(*DestinationAckerNode)).teardown","line":182},{"file":"/home/serhiispivak/go/src/github.com/conduit/pkg/pipeline/stream/source_acker.go","func":"[github.com/conduitio/conduit/pkg/pipeline/stream.(*SourceAckerNode](http://github.com/conduitio/conduit/pkg/pipeline/stream.(*SourceAckerNode)).registerNackHandler.func1","line":118}] 2022-09-28T12:51:14+00:00 ERR node stopped error="node 2dd849e9-d967-403f-9105-ad3e98f61468-acker stopped with error: failed to receive ack: %!w(<nil>)" component=pipeline.Service node_id=2dd849e9-d967-403f-9105-ad3e98f61468-acker stack=[{"file":"/home/serhiispivak/go/src/github.com/conduit/pkg/pipeline/lifecycle.go","func":"[github.com/conduitio/conduit/pkg/pipeline.(*Service](http://github.com/conduitio/conduit/pkg/pipeline.(*Service)).runPipeline.func1","line":411},{"file":"/home/serhiispivak/go/src/github.com/conduit/pkg/pipeline/stream/destination_acker.go","func":"[github.com/conduitio/conduit/pkg/pipeline/stream.(*DestinationAckerNode](http://github.com/conduitio/conduit/pkg/pipeline/stream.(*DestinationAckerNode)).worker","line":131}]

Steps to reproduce

  1. Create a Pipeline
  2. Create Zendesk Source connector and the Destination connector (for example NATS PubSub Destination connector), config:
version: 1.0                  

pipelines:                    
  pipeline1:                   
    status: stopped             
    name: pipeline1             
    description: desc           
    connectors:                 
      con1:                 
        type: source            
        plugin: standalone:zendesk    
        name: zendesk-source             
        settings:              
          zendesk.domain: <domain> 
          zendesk.userName: <user name in zendesk>
          zendesk.apiToken: <zendesk api token>
          pollingPeriod:
      con2:
        type: destination
        plugin: standalone:nats-pubsub
        name: nats-pubsub-DESTINATION
        settings:
           urls: <NATS connection URL> 
           subject: sbj
           connectionName:
           nkeyPath:
           credentialsFilePath:
           tls.clientCertPath:
           tls.clientPrivateKeyPath:
           tls.rootCACertPath:
           maxReconnects:
           reconnectWait:
  1. Start (or restart) the pipeline
  2. Get an error
2022-09-28T12:51:14+00:00 ERR destination acker node stopped before processing all messages error="nacked 1 messages when stopping destination acker node, some nacks failed: no DLQ handler configured" component=DestinationAckerNode node_id=2dd849e9-d967-403f-9105-ad3e98f61468-acker pipeline_id=0f70b007-80a1-4010-b1ac-f7b800c43191 stack=[{"file":"/home/serhiispivak/go/src/github.com/conduit/pkg/pipeline/stream/destination_acker.go","func":"[github.com/conduitio/conduit/pkg/pipeline/stream.(*DestinationAckerNode](http://github.com/conduitio/conduit/pkg/pipeline/stream.(*DestinationAckerNode)).teardown","line":182},{"file":"/home/serhiispivak/go/src/github.com/conduit/pkg/pipeline/stream/source_acker.go","func":"[github.com/conduitio/conduit/pkg/pipeline/stream.(*SourceAckerNode](http://github.com/conduitio/conduit/pkg/pipeline/stream.(*SourceAckerNode)).registerNackHandler.func1","line":118}] 2022-09-28T12:51:14+00:00 ERR node stopped error="node 2dd849e9-d967-403f-9105-ad3e98f61468-acker stopped with error: failed to receive ack: %!w(<nil>)" component=pipeline.Service node_id=2dd849e9-d967-403f-9105-ad3e98f61468-acker stack=[{"file":"/home/serhiispivak/go/src/github.com/conduit/pkg/pipeline/lifecycle.go","func":"[github.com/conduitio/conduit/pkg/pipeline.(*Service](http://github.com/conduitio/conduit/pkg/pipeline.(*Service)).runPipeline.func1","line":411},{"file":"/home/serhiispivak/go/src/github.com/conduit/pkg/pipeline/stream/destination_acker.go","func":"[github.com/conduitio/conduit/pkg/pipeline/stream.(*DestinationAckerNode](http://github.com/conduitio/conduit/pkg/pipeline/stream.(*DestinationAckerNode)).worker","line":131}]

Version

v0.3.0-nightly.20220927

@SerhiiSpivak SerhiiSpivak added the bug Something isn't working label Nov 14, 2022
@hariso
Copy link

hariso commented Nov 14, 2022

@SerhiiSpivak Thanks for this report!

Do you have more of the error? Also, can you try it either with 0.3.0 (the stable version) or the latest 0.4 nightly?

@SerhiiSpivak
Copy link
Author

@hariso Hi, Haris!
Yes, I can try to re-test it either with 0.3.0 (the stable version) or the latest 0.4 nightly.
Could you please set a priority for this issue?
I’m currently testing Snowflake after the changes and will be testing Clickhouse in the next few days as well as preparing test documentation. Should I start with the re-testing of this issue before?

@hariso
Copy link

hariso commented Nov 15, 2022

@SerhiiSpivak I can't say much about the priority, I'll need to ask @uchennakevinm1 and @hariso. But at the very least, let's use the latest version of Conduit in all future tests.

@SerhiiSpivak
Copy link
Author

@hariso Thanks for your reply!
Yes, I am currently using Conduit v0.4.0-nightly.20221020. These tests were executed in September and I used a previous version of Conduit.
Ok, I'll retest this issue on the latest version of Conduit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants