Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 963BE200C54 for ; Wed, 29 Mar 2017 06:43:47 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 94EB3160B9B; Wed, 29 Mar 2017 04:43:47 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 8D3DB160B89 for ; Wed, 29 Mar 2017 06:43:46 +0200 (CEST) Received: (qmail 28991 invoked by uid 500); 29 Mar 2017 04:43:45 -0000 Mailing-List: contact user-help@predictionio.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@predictionio.incubator.apache.org Delivered-To: mailing list user@predictionio.incubator.apache.org Received: (qmail 28979 invoked by uid 99); 29 Mar 2017 04:43:45 -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; Wed, 29 Mar 2017 04:43:45 +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 40B0B185F71 for ; Wed, 29 Mar 2017 04:43:45 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.453 X-Spam-Level: *** X-Spam-Status: No, score=3.453 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_SOFTFAIL=0.972, WEIRD_PORT=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=getamplify-com.20150623.gappssmtp.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 y_dh8FDpQLNP for ; Wed, 29 Mar 2017 04:43:42 +0000 (UTC) Received: from mail-lf0-f41.google.com (mail-lf0-f41.google.com [209.85.215.41]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 4050C5F2FE for ; Wed, 29 Mar 2017 04:43:42 +0000 (UTC) Received: by mail-lf0-f41.google.com with SMTP id x137so1791136lff.3 for ; Tue, 28 Mar 2017 21:43:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=getamplify-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=Yk0fvExa18GGY5yIl3zj4gIuyT6+yz2Q+bn/JpZBY90=; b=D9RMytUJMONw/7lHgXds0G2KgTfAziT+04QCbnqBAgdjfs+zLfo68+Uny8NuYDr0QK i1Dzxhcsk7E++SYKFU5e3YGUByIsIPopZXH/gorGy2Uced+JETrkjp6NmG+KYnVTwPwQ ixE1cZ9JCMN4qAY6PSo81633xHN+LmDzIQ7BX1HZz5tezgc7r+HVHxCCbgO0ErgVjQV+ 7ndIc0D/jVp/4KAoq70fBOLXYAl7yo59Vubx+ktJhTmrNRFBJ7D61WV2NBPeSt5olrp7 692iZpdWZibtvaGQFSLd1s1CGFClJlAKrfSYx7iBC/Qq5rU3RQkGF3KQsxzFqlXDb92q Epjg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=Yk0fvExa18GGY5yIl3zj4gIuyT6+yz2Q+bn/JpZBY90=; b=bxMz89Nj+WTheUZXQSc+dVlKSqR7/L4fPvk24Jh69RPu2LzlpJ0434+mqu0/4ZOBBs DrVBRkzN8OnzyjlQT2dOKxsn3BqEwlWdrsRBltPULX8QspPQsmI9PvlvOfPEWqQZonGd T81uxK+iCrPqs16rWGQwOM5aJBjE04t8+/Ba8i4hLlv7cJ5GqLy2ZaJ4NUOJ+xQ3n8GJ zs0bq1PrqJ0c+WX5yIpQZvfcgsdYu4i4RRjRb4425kplTm0Vl9wH+rONhCenQF7o4imn gs5btg04tZdgro65xqWPE9zmvo0wNfow8UuQtiYPePS+2jh6baeCDvExxu2IfjxiADYc Gf5A== X-Gm-Message-State: AFeK/H17S46Z2fygnwjJfekMQe4Vdn3lQrHmZywpdb0AzL+vmI2ZlXU2tfI96c+SjEpLZqZKTGctR+FpQip6ig== X-Received: by 10.46.7.68 with SMTP id i4mr2905811ljd.9.1490762621404; Tue, 28 Mar 2017 21:43:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.23.224 with HTTP; Tue, 28 Mar 2017 21:43:20 -0700 (PDT) X-Originating-IP: [45.115.104.43] In-Reply-To: References: From: Ambuj Sharma Date: Wed, 29 Mar 2017 10:13:20 +0530 Message-ID: Subject: Re: ERROR: Remote Elastic search cluster To: user@predictionio.incubator.apache.org Content-Type: multipart/alternative; boundary=f403045f792c7e61e6054bd738df archived-at: Wed, 29 Mar 2017 04:43:47 -0000 --f403045f792c7e61e6054bd738df Content-Type: text/plain; charset=UTF-8 make sure elasticSearch is running nd available from PIO Server. Try to send request to ES using Curl Thanks and Regards Ambuj Sharma Sunrise may late, But Morning is sure..... Team ML Betaout On Tue, Mar 28, 2017 at 11:39 PM, Malay Tripathi wrote: > Hi Ambuj, > > I did try below configuration and ran "pio status", same error. > > PIO_STORAGE_SOURCES_ELASTICSEARCH_TYPE=elasticsearch > > PIO_STORAGE_SOURCES_ELASTICSEARCH_CLUSTERNAME=prod > > PIO_STORAGE_SOURCES_ELASTICSEARCH_HOSTS=aabbcc176 > > PIO_STORAGE_SOURCES_ELASTICSEARCH_PORTS=9300 > > > Thanks, > > Malay > > On Tue, Mar 28, 2017 at 2:34 AM, Ambuj Sharma > wrote: > >> You need to configure only these properties >> >> PIO_STORAGE_SOURCES_ELASTICSEARCH_TYPE=elasticsearch >> PIO_STORAGE_SOURCES_ELASTICSEARCH_CLUSTERNAME= >> PIO_STORAGE_SOURCES_ELASTICSEARCH_HOSTS= >> PIO_STORAGE_SOURCES_ELASTICSEARCH_PORTS=9300 >> >> >> >> Thanks and Regards >> Ambuj Sharma >> Sunrise may late, But Morning is sure..... >> Team ML >> Betaout >> >> On Tue, Mar 28, 2017 at 12:47 PM, Malay Tripathi < >> malaytripathi3@gmail.com> wrote: >> >>> Hi, >>> >>> I have setup 3 node cluster for ES - aabbcc174, aabbcc175, aabbcc176. >>> In my spark edge node, I have installed PredictionIO & given below >>> properties in conf/pio-env.sh- >>> >>> PIO_STORAGE_SOURCES_ELASTICSEARCH_TYPE=elasticsearch >>> >>> PIO_STORAGE_SOURCES_ELASTICSEARCH_CLUSTERNAME=prod >>> >>> PIO_STORAGE_SOURCES_ELASTICSEARCH_HOSTS= aabbcc174, aabbcc175, aabbcc176 >>> >>> PIO_STORAGE_SOURCES_ELASTICSEARCH_PORTS=9300,9300,9300 >>> >>> >>> But if i run *"pio status"* I keep getting error - >>> >>> [ERROR] [Console$] Unable to connect to all storage backends >>> successfully. The following shows the error message from the storage >>> backend. >>> >>> [ERROR] [Console$] None of the configured nodes are available: [] >>> (org.elasticsearch.client.transport.NoNodeAvailableException) >>> >>> [ERROR] [Console$] Dumping configuration of initialized storage backend >>> sources. Please make sure they are correct. >>> >>> [ERROR] [Console$] Source Name: ELASTICSEARCH; Type: elasticsearch; >>> Configuration: HOSTS -> aabbcc174, aabbcc175, aabbcc176, TYPE -> >>> elasticsearch, CLUSTERNAME -> prod >>> >>> >>> Although If i CURL my elastic search from this edge node where "pio >>> status" is failing I get successful response- >>> >>> [xxxxxx@edgeNode conf]$ curl http://aabbcc174:9200/_nodes/process?pretty >>> >>> { >>> >>> "cluster_name" : "prod", >>> >>> "nodes" : { >>> >>> "Jru48ImiSuSbSe95e0Qh8A" : { >>> >>> "name" : "prod-node1", >>> >>> ..... >>> >>> Thanks !!! >>> >> >> > --f403045f792c7e61e6054bd738df Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
make sure elasticSearch is running nd available from PIO S= erver. Try to send request to ES using Curl


Thanks and Regards
Ambuj Sharma
Sunrise may late, But Morning is sure.....
Team ML
Betaout

On Tue, Mar 28, 2017 at 11:39 PM, Malay Trip= athi <malaytripathi3@gmail.com> wrote:

Hi Ambuj,

I did try below configurati= on and ran "pio status", same error.

PIO_= STORAGE_SOURCES_ELASTICSEARCH_TYPE=3Delasticsearch

PIO_STORAGE_SOURCES_= ELASTICSEARCH_CLUSTERNAME=3Dprod

PIO_STORAGE_SOURCES_ELASTICSEARCH_HOSTS=3Daabbcc176

PIO_ST= ORAGE_SOURCES_ELASTICSEARCH_PORTS=3D930= 0


Thanks,

Malay

<= div class=3D"gmail_extra">
On Tue, Mar 28, 20= 17 at 2:34 AM, Ambuj Sharma <ambuj@getamplify.com> wrote:=
You need to configure o= nly these properties

PIO_STORAGE_SOURCES_ELASTICSEA= RCH_TYPE=3Delasticsearch
PIO_STORAGE_SOURCES_ELASTICSEA= RCH_CLUSTERNAME=3D<your cluster Name>
PIO_STORAGE_SOURCES_E= LASTICSEARCH_HOSTS=3D<ES Master IP>
PIO_STORAGE_= SOURCES_ELASTICSEARCH_PORTS=3D9300


<= br>
Thanks and Regards
Ambuj Sharma
Sunrise may late, But Morning is sure.....
Team ML
Betaout

On Tue, Mar 28, 2017 at 12:47 PM, Malay Trip= athi <malaytripathi3@gmail.com> wrote:
Hi,

I have se= tup 3 node cluster for ES - aabbcc174, aabbcc175, aabbcc176.
In my spar= k edge node, I have installed PredictionIO & given below properties in = conf/pio-env.sh-

PIO_STORAGE_SOURCES_ELASTICSEARCH_TYPE=3Delasticsearch

PIO_STORAGE_SOURCES_ELASTICSEARCH_CL= USTERNAME=3Dprod

PIO_STORAGE_SOURCES_ELASTICSEARCH_HO= STS=3D=C2=A0aabbcc174, aabbcc175,=C2=A0aabbcc176=

PIO_STORAGE_SOURCES_ELASTICSEARCH_PORTS=3D9300,9300,9300=


But if i run "pio status"<= /b> I keep getting error -

[ERROR] [Console$] Una= ble to connect to all storage backends successfully. The following shows th= e error message from the storage backend.

[ERROR] [Console$] None of the configured nodes are available: [] (org.el= asticsearch.client.transport.NoNodeAvailableException)

=

[ERROR] [Console$] Dumping configuration of initiali= zed storage backend sources. Please make sure they are correct.

<= p class=3D"m_3489067467359281719m_5660334406133590604m_6738584325417492110g= mail-p1">

[ERROR] [Console$] Source Name: ELASTICSEARCH; T= ype: elasticsearch; Configuration: HOSTS ->=C2=A0aabbcc174,= aabbcc175,=C2=A0aabbcc176, TYPE -> elasticsearch, CLUSTERNAME -&= gt; prod


Although If i CURL my elastic search from this edge node where "p= io status" is failing I get successful response-

<= span class=3D"m_3489067467359281719m_5660334406133590604m_67385843254174921= 10gmail-s1">[xxxxxx@edgeNode conf]$ curl http://aabbcc174:9200/_nodes/p= rocess?pretty

{

=C2=A0 "cluster_name" : "prod",

=C2=A0 "nodes" : {

=C2=A0 =C2=A0 "Jru48ImiSuSbSe95e0Qh8A" : {

=C2=A0 =C2=A0 =C2=A0 "name" : "prod-node1= ",

.....

=C2=A0 =C2=A0 =C2=A0Thanks !!!

=



--f403045f792c7e61e6054bd738df--