Uploaded image for project: 'Flume'
  1. Flume
  2. FLUME-1230

Sink gets initialized even when not active

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.2.0
    • None
    • None

    Description

      Flume configuration requires that components that are not declared in the active lists (agent.sources, agent.sinks, agent.channels, and agent.sinkgroups) be disabled by default. However, in some cases, sinks that are not in the active list will get initialized and started.

      Following configuration can reproduce this scenario:

      agent.sources = s
      agent.channels = c
      #agent.sinks = k1 k2
      
      agent.sources.s.type = netcat
      agent.sources.s.port = 12121
      agent.sources.s.bind = localhost
      agent.sources.s.channels = c
      
      agent.channels.c.type = memory
      
      agent.sinks.k1.type = logger
      agent.sinks.k1.channel = c
      
      agent.sinks.k2.type = null
      agent.sinks.k2.channel = c
      

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            hshreedharan Hari Shreedharan
            aprabhakar Arvind Prabhakar
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment