From issues-return-842-archive-asf-public=cust-asf.ponee.io@flume.apache.org Fri Mar 8 05:10:04 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 6045B180654 for ; Fri, 8 Mar 2019 06:10:04 +0100 (CET) Received: (qmail 86379 invoked by uid 500); 8 Mar 2019 05:10:03 -0000 Mailing-List: contact issues-help@flume.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flume.apache.org Delivered-To: mailing list issues@flume.apache.org Received: (qmail 86361 invoked by uid 99); 8 Mar 2019 05:10:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Mar 2019 05:10:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 02263C0225 for ; Fri, 8 Mar 2019 05:10:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id J0wwuVfoxqU1 for ; Fri, 8 Mar 2019 05:10:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 1D3275FD0D for ; Fri, 8 Mar 2019 05:10:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6BB88E04AD for ; Fri, 8 Mar 2019 05:10:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 09859257D3 for ; Fri, 8 Mar 2019 05:10:00 +0000 (UTC) Date: Fri, 8 Mar 2019 05:10:00 +0000 (UTC) From: "zhipcui (JIRA)" To: issues@flume.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (FLUME-3323) Kafka channel should supports disable producer/consumer according to the need MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FLUME-3323?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] zhipcui updated FLUME-3323: --------------------------- Description:=20 As the doc said: {noformat} The Kafka channel can be used for multiple scenarios: 1. With Flume source and sink - it provides a reliable and highly available= channel for events 2. With Flume source and interceptor but no sink - it allows writing Flume = events into a Kafka topic, for use by other apps 3. With Flume sink, but no source - it is a low-latency, fault tolerant way= to send events from Kafka to Flume sinks such as HDFS, HBase or Solr{nofor= mat} =C2=A0 Kafka channel will generates producer and consumer=C2=A0both now. When using Kafka channel as scenario 2 (3), the producer(consumer) is just = useless, and if our kafka cluster enable SASL the situation is getting wors= e. Assume we have a kafka account which only=C2=A0has=C2=A0read permissions, a= nd using kafka channel without source,=C2=A0producer shouldn't be generated= . I propose that add two properties to=C2=A0disable producer/consumer. =C2=A0 {noformat} agent.channels.c.noProducer =3D false agent.channels.c.noConsumer=3D false{noformat} =C2=A0 =C2=A0 =C2=A0 =C2=A0 was: As the doc said: {noformat} The Kafka channel can be used for multiple scenarios: 1. With Flume source and sink - it provides a reliable and highly available= channel for events 2. With Flume source and interceptor but no sink - it allows writing Flume = events into a Kafka topic, for use by other apps 3. With Flume sink, but no source - it is a low-latency, fault tolerant way= to send events from Kafka to Flume sinks such as HDFS, HBase or Solr{nofor= mat} =C2=A0 Kafka channel will generates producer and consumer=C2=A0both now. When using Kafka channel as scenario 2 (3), the producer(consumer) is just = useless, and if our kafka cluster enable SASL the situation is getting wors= e. Assume we have a kafka account which only=C2=A0has=C2=A0read permissions, a= nd using kafka channel without source,=C2=A0producer shouldn't be generated= . I propose that add two properties to=C2=A0disable producer/consumer. =C2=A0 {noformat} agent.channels.c.withSource =3D false agent.channels.c.withSink=3D false{noformat} =C2=A0 =C2=A0 =C2=A0 =C2=A0 > Kafka channel should supports disable producer/consumer according to the = need > -------------------------------------------------------------------------= ---- > > Key: FLUME-3323 > URL: https://issues.apache.org/jira/browse/FLUME-3323 > Project: Flume > Issue Type: Improvement > Components: Kafka Channel > Affects Versions: 1.9.0 > Reporter: zhipcui > Priority: Minor > > As the doc said: > {noformat} > The Kafka channel can be used for multiple scenarios: > 1. With Flume source and sink - it provides a reliable and highly availab= le channel for events > 2. With Flume source and interceptor but no sink - it allows writing Flum= e events into a Kafka topic, for use by other apps > 3. With Flume sink, but no source - it is a low-latency, fault tolerant w= ay to send events from Kafka to Flume sinks such as HDFS, HBase or Solr{nof= ormat} > =C2=A0 > Kafka channel will generates producer and consumer=C2=A0both now. > When using Kafka channel as scenario 2 (3), the producer(consumer) is jus= t useless, and if our kafka cluster enable SASL the situation is getting wo= rse. > Assume we have a kafka account which only=C2=A0has=C2=A0read permissions,= and using kafka channel without source,=C2=A0producer shouldn't be generat= ed. > I propose that add two properties to=C2=A0disable producer/consumer. > =C2=A0 > {noformat} > agent.channels.c.noProducer =3D false > agent.channels.c.noConsumer=3D false{noformat} > =C2=A0 > =C2=A0 > =C2=A0 > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@flume.apache.org For additional commands, e-mail: issues-help@flume.apache.org