From user-return-14365-archive-asf-public=cust-asf.ponee.io@storm.apache.org Thu Apr 4 18:07:34 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 05C2918064C for ; Thu, 4 Apr 2019 20:07:33 +0200 (CEST) Received: (qmail 84659 invoked by uid 500); 4 Apr 2019 18:07:32 -0000 Mailing-List: contact user-help@storm.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@storm.apache.org Delivered-To: mailing list user@storm.apache.org Received: (qmail 84649 invoked by uid 99); 4 Apr 2019 18:07:32 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Apr 2019 18:07:32 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 3E47A180897 for ; Thu, 4 Apr 2019 18:07:32 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.801 X-Spam-Level: ** X-Spam-Status: No, score=2.801 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_REPLY=1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id c-RDQGuEsMT8 for ; Thu, 4 Apr 2019 18:07:30 +0000 (UTC) Received: from mail-ot1-f52.google.com (mail-ot1-f52.google.com [209.85.210.52]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id F145060E4E for ; Thu, 4 Apr 2019 18:07:29 +0000 (UTC) Received: by mail-ot1-f52.google.com with SMTP id j10so3236537otq.0 for ; Thu, 04 Apr 2019 11:07:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=aQe1uAtJTbOB9QbOBDb/24wvQzNrIiSmEJH1wBnOnNU=; b=b/teG2AGgSNjYziqAyGzXLsGD5SHb/tWoKsVsdwUFh6PQJUMisHphtuxKVk12PzjOY 7P4P8ZVkVg6yUlsVQeScBVyShFe1GhVEMN4jfLL8XYd36vuSZ35tMiZTfcrkaoqazWVl wzzD8oNsnxTlYelbxYDJFve9g3HWnyxXOujK1E8RxHx4WOk3ekWH+SyuGTU4zvpdb3G4 o78zvM1EwavClyX+IAv7vvBoou2BjzJGg8DAx6YHOFUqiUnQV7aLpTHnV7ajpPQBR/PM oQ5//MnE+jpghx4hK5J7kVw2OgQuX/vUqHqTrZWU8tyNEemfPVyIfwyRNzSpj5Ib5/03 U6RQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=aQe1uAtJTbOB9QbOBDb/24wvQzNrIiSmEJH1wBnOnNU=; b=uSrxTh95GJtixlV82lh5lvUIGeAynXN4UKrLan+ObdzCzH8RMIONtdNy8eJCMds403 fVKndgQ1GtK+p0QCpOMf2I8p/L0oYcxLJg+BdyLbleXBA5cV8gNF2A/DnH6CAm3pWeLr b9z7lhDUiY71Hu2hgiSW2jUNzU+sJXN6vbiS0AT+/pwAH1fB5J6qbjqIYaTOhWmftUze Hzq/Ia8bmOOMJ2KU6aPLOHZwEwb30I8wQ85EbKM5WzqVuAuklYdFPBRybcG8XERCC7MB ZiZ+eUUmL8ZR3rfzJzBs7Rb2u4kTWiJNzYnj5JDlaJZT0VY4AGHJQF9EZLLWAYSgIWzB Pm/w== X-Gm-Message-State: APjAAAVWSznGJUbUUWhDgn8a4eupvtyBy1T42RrbS/A0tJJZol/Pz4IU qKLeiljKGE/Ppx7AFFVN1I5qEJuUnLoTN0DFNA0+jw== X-Google-Smtp-Source: APXvYqzXegNfU0t6Wkc006pZrr6IXkhf9eLM30mfzFe5zvWEQlA/UWgyj1jE078OhX79Hn4jf0fo/7+Zv2NyhyHe51I= X-Received: by 2002:a05:6830:2051:: with SMTP id f17mr5014117otp.223.1554401248602; Thu, 04 Apr 2019 11:07:28 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?Q?Stig_Rohde_D=C3=B8ssing?= Date: Thu, 4 Apr 2019 20:07:17 +0200 Message-ID: Subject: Re: storm logs on console of kubernetes containers/pods To: user@storm.apache.org Content-Type: multipart/alternative; boundary="00000000000042ef2d0585b83e8c" --00000000000042ef2d0585b83e8c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable You could probably also just tail the worker log files into the console you are using to run the supervisor, but it'll most likely get messy to read. Den tor. 4. apr. 2019 kl. 20.04 skrev Stig Rohde D=C3=B8ssing < stigdoessing@gmail.com>: > I don't think you can get the worker logs in the console directly. The > issue is that your container will be running both the supervisor, and a > number of workers. The workers are started by the supervisor, and aren't > attached to the console you use to start the supervisor. Even if you > configure a console appender in worker.xml, the output won't be going int= o > the supervisor console, which is what I think you need. > > I think to fix this would require either copying the worker log to the > supervisor console (we probably don't want this), or make how the > supervisor starts/monitors workers more flexible. If the supervisor could > start the worker in a different container per worker instead of both > supervisors and workers being in one container, that would be a better fi= t > I think. > > Den tor. 4. apr. 2019 kl. 19.39 skrev Dhiman Kundu >: > >> Hi, >> We are using storm 1.2.2 on kubernetes(K8) cluster. We have 1 storm >> nimbus and 3 supervisors to submit topology. We are getting logs in >> worker.log file against each supervisor. >> But we want logs within kubernetes console which can be accessed with >> "kubectl logs -f -n namespace". >> We changed the worker.xml within log4j2 folder. We add the corresponding >> console Appender. But we are not getting logs in kubctl container's >> console. I want to know whether its possible to get logs in console. >> >> Please correct me if I am wrong. >> >> Thanks, >> Dhiman >> > --00000000000042ef2d0585b83e8c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
You could probably also just tail the worker log files int= o the console you are using to run the supervisor, but it'll most likel= y get messy to read.

Den tor. 4. apr. 2019 kl. 20.04 skrev Stig Rohde D= =C3=B8ssing <stigdoessing@gmai= l.com>:
<= div dir=3D"ltr">
I don't think you can get the worker logs in the c= onsole directly. The issue is that your container will be running both the = supervisor, and a number of workers. The workers are started by the supervi= sor, and aren't attached to the console you use to start the supervisor= . Even if you configure a console appender in worker.xml, the output won= 9;t be going into the supervisor console, which is what I think you need.

I think to fix this would require either copying th= e worker log to the supervisor console (we probably don't want this), o= r make how the supervisor starts/monitors workers more flexible. If the sup= ervisor could start the worker in a different container per worker instead = of both supervisors and workers being in one container, that would be a bet= ter fit I think.

Den tor. 4. apr. 2019 kl. 19.39 skrev Dhiman Kund= u <kundudhima= n@gmail.com>:
Hi,
We are using storm= 1.2.2 on kubernetes(K8) cluster. We have 1 storm nimbus and 3 supervisors = to submit topology. We are getting logs in worker.log file against each sup= ervisor.
But we want logs within kubernetes console which can be accesse= d with "kubectl logs -f <supervisor container/pod> -n namespace&= quot;.
We changed the worker.xml within log4j2 folder. We add the corres= ponding console Appender. But we are not getting logs in kubctl container&#= 39;s console. I want to know whether its possible to get logs in console.
Please correct me if I am wrong.

Thanks,
Dhiman
--00000000000042ef2d0585b83e8c--