You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@kafka.apache.org by Karthick Kumar <kk...@apptivo.co.in> on 2018/05/11 07:28:33 UTC
Re: Removing the Kafka DEBUG logs in catalina.out using log4j.properties
Hi,
I'm using tomcat node as a Kafka consumer, It prints the INFO, DEBUG and
ERROR logs.
When I analyzed in log file debug logs are taking more space. So i'm having
disk space issue.
I'm using *log4j.properties* for managing the logs, Now I want to remove
the DEBUG logs from my logger file.
Anyone, please guide me to remove the DEBUG logs.
--
With Regards,
Karthick.K
Re: Removing the Kafka DEBUG logs in catalina.out using log4j.properties
Posted by Karthick Kumar <kk...@apptivo.co.in>.
Okay Kaufman, will check on that
On Sun, May 20, 2018 at 12:08 AM, Kaufman Ng <ka...@confluent.io> wrote:
> Karthick,
>
> I am suspecting that it could be the log4j.properties in your webapp is not
> picked up by Tomcat, or somehow Tomcat is overriding your webapp's log4j
> setup.
>
> On Tue, May 15, 2018 at 2:19 AM, Karthick Kumar <kk...@apptivo.co.in>
> wrote:
>
> > Hi Andras/Kaufman,
> >
> > I have tried both logger properties, But it is not working for me.
> >
> > Here I share the some DEBUG logger message which is print in my tomcat
> node
> >
> >
> > DEBUG AbstractCoordinator:704 - Sending Heartbeat request for group
> > apptivodb5-newsfeed-messages-4-consumer to coordinator xx.xx.xx.xx:9092
> > (id: 2147483645 rack: null)
> > DEBUG AbstractCoordinator:717 - Received successful Heartbeat response
> for
> > group apptivodb4-newsfeed-messages-4-consumer
> > DEBUG AbstractCoordinator:717 - Received successful Heartbeat response
> for
> > group apptivodb5-newsfeed-messages-4-consumer
> > DEBUG Fetcher:180 - Sending fetch for partitions
> > [apptivodb5-newsfeed-messages-0-1] to broker xx.xx.xx.xx:9092 (id: 2
> rack:
> > null)
> > DEBUG Fetcher:180 - Sending fetch for partitions
> > [apptivodb1-campaign-launcher-1] to broker xx.xx.xx.xx:9092 (id: 2 rack:
> > null)
> > DEBUG Fetcher:180 - Sending fetch for partitions
> > [apptivodb8-campaign-tracker-email-0] to broker xx.xx.xx.xx:9092 (id: 2
> > rack: null)
> > DEBUG Fetcher:180 - Sending fetch for partitions
> > [apptivodb5-campaign-tracker-email-1] to broker xx.xx.xx.xx:9092 (id: 2
> > rack: null)
> >
> >
> >
> > On Mon, May 14, 2018 at 12:46 AM, Kaufman Ng <ka...@confluent.io>
> wrote:
> >
> > > Is the log coming from your application on Tomcat or Kafka? Make sure
> you
> > > set the right log4j properties file. In general you can set this in
> > > log4j.properties like this:
> > >
> > > log4j.rootLogger=INFO, stdout
> > >
> > > The line in your log4j.properties may look a little bit differently.
> The
> > > key thing is to set the root logger to "INFO".
> > >
> > > Hope this helps.
> > >
> > >
> > > On Sun, May 13, 2018 at 9:10 AM, Andras Beni <an...@cloudera.com>
> > > wrote:
> > >
> > > > Hi Kathick,
> > > >
> > > > You probably want to add this line to your log4j.properties:
> > > > log4j.logger.org.apache.kafka=INFO
> > > > This will remove all DEBUG lines where the logger name starts with
> > > > org.apache.kafka.
> > > >
> > > > HTH,
> > > > Andras
> > > >
> > > > On Fri, May 11, 2018 at 9:28 AM, Karthick Kumar <
> kkumar@apptivo.co.in>
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I'm using tomcat node as a Kafka consumer, It prints the INFO,
> DEBUG
> > > and
> > > > > ERROR logs.
> > > > >
> > > > > When I analyzed in log file debug logs are taking more space. So
> i'm
> > > > having
> > > > > disk space issue.
> > > > >
> > > > > I'm using *log4j.properties* for managing the logs, Now I want to
> > > remove
> > > > > the DEBUG logs from my logger file.
> > > > >
> > > > > Anyone, please guide me to remove the DEBUG logs.
> > > > >
> > > > > --
> > > > > With Regards,
> > > > > Karthick.K
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Kaufman Ng
> > > +1 646 961 8063
> > > Solutions Architect | Confluent | www.confluent.io
> > >
> >
> >
> >
> > --
> > With Regards,
> > Karthick.K
> >
>
>
>
> --
> Kaufman Ng
> +1 646 961 8063
> Solutions Architect | Confluent | www.confluent.io
>
--
With Regards,
Karthick.K
Re: Removing the Kafka DEBUG logs in catalina.out using log4j.properties
Posted by Kaufman Ng <ka...@confluent.io>.
Karthick,
I am suspecting that it could be the log4j.properties in your webapp is not
picked up by Tomcat, or somehow Tomcat is overriding your webapp's log4j
setup.
On Tue, May 15, 2018 at 2:19 AM, Karthick Kumar <kk...@apptivo.co.in>
wrote:
> Hi Andras/Kaufman,
>
> I have tried both logger properties, But it is not working for me.
>
> Here I share the some DEBUG logger message which is print in my tomcat node
>
>
> DEBUG AbstractCoordinator:704 - Sending Heartbeat request for group
> apptivodb5-newsfeed-messages-4-consumer to coordinator xx.xx.xx.xx:9092
> (id: 2147483645 rack: null)
> DEBUG AbstractCoordinator:717 - Received successful Heartbeat response for
> group apptivodb4-newsfeed-messages-4-consumer
> DEBUG AbstractCoordinator:717 - Received successful Heartbeat response for
> group apptivodb5-newsfeed-messages-4-consumer
> DEBUG Fetcher:180 - Sending fetch for partitions
> [apptivodb5-newsfeed-messages-0-1] to broker xx.xx.xx.xx:9092 (id: 2 rack:
> null)
> DEBUG Fetcher:180 - Sending fetch for partitions
> [apptivodb1-campaign-launcher-1] to broker xx.xx.xx.xx:9092 (id: 2 rack:
> null)
> DEBUG Fetcher:180 - Sending fetch for partitions
> [apptivodb8-campaign-tracker-email-0] to broker xx.xx.xx.xx:9092 (id: 2
> rack: null)
> DEBUG Fetcher:180 - Sending fetch for partitions
> [apptivodb5-campaign-tracker-email-1] to broker xx.xx.xx.xx:9092 (id: 2
> rack: null)
>
>
>
> On Mon, May 14, 2018 at 12:46 AM, Kaufman Ng <ka...@confluent.io> wrote:
>
> > Is the log coming from your application on Tomcat or Kafka? Make sure you
> > set the right log4j properties file. In general you can set this in
> > log4j.properties like this:
> >
> > log4j.rootLogger=INFO, stdout
> >
> > The line in your log4j.properties may look a little bit differently. The
> > key thing is to set the root logger to "INFO".
> >
> > Hope this helps.
> >
> >
> > On Sun, May 13, 2018 at 9:10 AM, Andras Beni <an...@cloudera.com>
> > wrote:
> >
> > > Hi Kathick,
> > >
> > > You probably want to add this line to your log4j.properties:
> > > log4j.logger.org.apache.kafka=INFO
> > > This will remove all DEBUG lines where the logger name starts with
> > > org.apache.kafka.
> > >
> > > HTH,
> > > Andras
> > >
> > > On Fri, May 11, 2018 at 9:28 AM, Karthick Kumar <kk...@apptivo.co.in>
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > I'm using tomcat node as a Kafka consumer, It prints the INFO, DEBUG
> > and
> > > > ERROR logs.
> > > >
> > > > When I analyzed in log file debug logs are taking more space. So i'm
> > > having
> > > > disk space issue.
> > > >
> > > > I'm using *log4j.properties* for managing the logs, Now I want to
> > remove
> > > > the DEBUG logs from my logger file.
> > > >
> > > > Anyone, please guide me to remove the DEBUG logs.
> > > >
> > > > --
> > > > With Regards,
> > > > Karthick.K
> > > >
> > >
> >
> >
> >
> > --
> > Kaufman Ng
> > +1 646 961 8063
> > Solutions Architect | Confluent | www.confluent.io
> >
>
>
>
> --
> With Regards,
> Karthick.K
>
--
Kaufman Ng
+1 646 961 8063
Solutions Architect | Confluent | www.confluent.io
Re: Removing the Kafka DEBUG logs in catalina.out using log4j.properties
Posted by Karthick Kumar <kk...@apptivo.co.in>.
Hi Andras/Kaufman,
I have tried both logger properties, But it is not working for me.
Here I share the some DEBUG logger message which is print in my tomcat node
DEBUG AbstractCoordinator:704 - Sending Heartbeat request for group
apptivodb5-newsfeed-messages-4-consumer to coordinator xx.xx.xx.xx:9092
(id: 2147483645 rack: null)
DEBUG AbstractCoordinator:717 - Received successful Heartbeat response for
group apptivodb4-newsfeed-messages-4-consumer
DEBUG AbstractCoordinator:717 - Received successful Heartbeat response for
group apptivodb5-newsfeed-messages-4-consumer
DEBUG Fetcher:180 - Sending fetch for partitions
[apptivodb5-newsfeed-messages-0-1] to broker xx.xx.xx.xx:9092 (id: 2 rack:
null)
DEBUG Fetcher:180 - Sending fetch for partitions
[apptivodb1-campaign-launcher-1] to broker xx.xx.xx.xx:9092 (id: 2 rack:
null)
DEBUG Fetcher:180 - Sending fetch for partitions
[apptivodb8-campaign-tracker-email-0] to broker xx.xx.xx.xx:9092 (id: 2
rack: null)
DEBUG Fetcher:180 - Sending fetch for partitions
[apptivodb5-campaign-tracker-email-1] to broker xx.xx.xx.xx:9092 (id: 2
rack: null)
On Mon, May 14, 2018 at 12:46 AM, Kaufman Ng <ka...@confluent.io> wrote:
> Is the log coming from your application on Tomcat or Kafka? Make sure you
> set the right log4j properties file. In general you can set this in
> log4j.properties like this:
>
> log4j.rootLogger=INFO, stdout
>
> The line in your log4j.properties may look a little bit differently. The
> key thing is to set the root logger to "INFO".
>
> Hope this helps.
>
>
> On Sun, May 13, 2018 at 9:10 AM, Andras Beni <an...@cloudera.com>
> wrote:
>
> > Hi Kathick,
> >
> > You probably want to add this line to your log4j.properties:
> > log4j.logger.org.apache.kafka=INFO
> > This will remove all DEBUG lines where the logger name starts with
> > org.apache.kafka.
> >
> > HTH,
> > Andras
> >
> > On Fri, May 11, 2018 at 9:28 AM, Karthick Kumar <kk...@apptivo.co.in>
> > wrote:
> >
> > > Hi,
> > >
> > > I'm using tomcat node as a Kafka consumer, It prints the INFO, DEBUG
> and
> > > ERROR logs.
> > >
> > > When I analyzed in log file debug logs are taking more space. So i'm
> > having
> > > disk space issue.
> > >
> > > I'm using *log4j.properties* for managing the logs, Now I want to
> remove
> > > the DEBUG logs from my logger file.
> > >
> > > Anyone, please guide me to remove the DEBUG logs.
> > >
> > > --
> > > With Regards,
> > > Karthick.K
> > >
> >
>
>
>
> --
> Kaufman Ng
> +1 646 961 8063
> Solutions Architect | Confluent | www.confluent.io
>
--
With Regards,
Karthick.K
Re: Removing the Kafka DEBUG logs in catalina.out using log4j.properties
Posted by Kaufman Ng <ka...@confluent.io>.
Is the log coming from your application on Tomcat or Kafka? Make sure you
set the right log4j properties file. In general you can set this in
log4j.properties like this:
log4j.rootLogger=INFO, stdout
The line in your log4j.properties may look a little bit differently. The
key thing is to set the root logger to "INFO".
Hope this helps.
On Sun, May 13, 2018 at 9:10 AM, Andras Beni <an...@cloudera.com>
wrote:
> Hi Kathick,
>
> You probably want to add this line to your log4j.properties:
> log4j.logger.org.apache.kafka=INFO
> This will remove all DEBUG lines where the logger name starts with
> org.apache.kafka.
>
> HTH,
> Andras
>
> On Fri, May 11, 2018 at 9:28 AM, Karthick Kumar <kk...@apptivo.co.in>
> wrote:
>
> > Hi,
> >
> > I'm using tomcat node as a Kafka consumer, It prints the INFO, DEBUG and
> > ERROR logs.
> >
> > When I analyzed in log file debug logs are taking more space. So i'm
> having
> > disk space issue.
> >
> > I'm using *log4j.properties* for managing the logs, Now I want to remove
> > the DEBUG logs from my logger file.
> >
> > Anyone, please guide me to remove the DEBUG logs.
> >
> > --
> > With Regards,
> > Karthick.K
> >
>
--
Kaufman Ng
+1 646 961 8063
Solutions Architect | Confluent | www.confluent.io
Re: Removing the Kafka DEBUG logs in catalina.out using log4j.properties
Posted by Andras Beni <an...@cloudera.com>.
Hi Kathick,
You probably want to add this line to your log4j.properties:
log4j.logger.org.apache.kafka=INFO
This will remove all DEBUG lines where the logger name starts with
org.apache.kafka.
HTH,
Andras
On Fri, May 11, 2018 at 9:28 AM, Karthick Kumar <kk...@apptivo.co.in>
wrote:
> Hi,
>
> I'm using tomcat node as a Kafka consumer, It prints the INFO, DEBUG and
> ERROR logs.
>
> When I analyzed in log file debug logs are taking more space. So i'm having
> disk space issue.
>
> I'm using *log4j.properties* for managing the logs, Now I want to remove
> the DEBUG logs from my logger file.
>
> Anyone, please guide me to remove the DEBUG logs.
>
> --
> With Regards,
> Karthick.K
>