From user-return-18838-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Mon Apr 9 13:10:46 2018 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 B01B8180645 for ; Mon, 9 Apr 2018 13:10:45 +0200 (CEST) Received: (qmail 15240 invoked by uid 500); 9 Apr 2018 11:10:44 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 15230 invoked by uid 99); 9 Apr 2018 11:10:44 -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; Mon, 09 Apr 2018 11:10:44 +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 1971318061F for ; Mon, 9 Apr 2018 11:10:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.172 X-Spam-Level: ** X-Spam-Status: No, score=2.172 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.972] autolearn=disabled 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 7qVYetOHKmbJ for ; Mon, 9 Apr 2018 11:10:43 +0000 (UTC) Received: from n6.nabble.com (n6.nabble.com [162.255.23.37]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id A09125F522 for ; Mon, 9 Apr 2018 11:10:42 +0000 (UTC) Received: from n6.nabble.com (localhost [127.0.0.1]) by n6.nabble.com (Postfix) with ESMTP id 879BE67977B1 for ; Mon, 9 Apr 2018 04:10:41 -0700 (MST) Date: Mon, 9 Apr 2018 04:10:41 -0700 (MST) From: vbm To: user@ignite.apache.org Message-ID: <1523272241552-0.post@n6.nabble.com> In-Reply-To: References: <1523104853862-0.post@n6.nabble.com> Subject: Re: Ignite visor command issue on K8s cluster MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Dave In the ignite pod logs of the server, I see that the cluster is formed. I see the below trace when I run the command, [02:53:18] Topology snapshot [ver=4, servers=4, clients=0, CPUs=8, heap=6.0GB] This indicates the cluster of 4 nodes has formed. When I login to the container and try to run the ignite visor, it says connected. But when I tried some commands like top, cache. They were not returning any result. I got a link in stack overflow on the usage of visor in K8s https://stackoverflow.com/questions/45197520/running-the-ignite-visor-in-kubernetes So as per this, I created a new pod and as part of docker run command I gave the config file for ignite visor. With this it was able to connect to the cluster. Is this the right approach in K8s environment ? If this is correct, how do I take care of different input from user to the ignite visor to this pod ? Regards, Vishwas -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/