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 0D339200BF1 for ; Tue, 3 Jan 2017 21:18:34 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 0BC41160B43; Tue, 3 Jan 2017 20:18:34 +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 06E50160B20 for ; Tue, 3 Jan 2017 21:18:32 +0100 (CET) Received: (qmail 90669 invoked by uid 500); 3 Jan 2017 20:18:32 -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 90656 invoked by uid 99); 3 Jan 2017 20:18:32 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jan 2017 20:18:32 +0000 Received: from [192.168.75.153] (c-73-222-138-29.hsd1.ca.comcast.net [73.222.138.29]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id D56F31A02F0 for ; Tue, 3 Jan 2017 20:18:31 +0000 (UTC) From: Denis Magda Content-Type: multipart/alternative; boundary="Apple-Mail=_4FDCBD80-45E1-4975-890D-0B902DE88443" Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: Old AWS SDK version, why? Date: Tue, 3 Jan 2017 12:18:30 -0800 References: <1483372752362-9824.post@n6.nabble.com> <1483387884027-9825.post@n6.nabble.com> <1483473319758-9855.post@n6.nabble.com> To: user@ignite.apache.org In-Reply-To: <1483473319758-9855.post@n6.nabble.com> Message-Id: <43E5FB2D-63CA-45A3-9718-963AAAB80F1C@apache.org> X-Mailer: Apple Mail (2.3259) archived-at: Tue, 03 Jan 2017 20:18:34 -0000 --Apple-Mail=_4FDCBD80-45E1-4975-890D-0B902DE88443 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Most likely the issue is not related to SDK version. It=E2=80=99s = related to your AWS account. Here is a discussion around a similar issue https://github.com/aws/aws-sdk-ruby/issues/808 = In any case, you can quickly check your assumptions in regards to an = outdated SDK by changing SDK version in ignite-aws pom.xml directly or = by relating the old jars with the new one. =E2=80=94 Denis > On Jan 3, 2017, at 11:55 AM, zshamrock = wrote: >=20 > Why I ask. It is not only matter of depending on the latest version, = but for > AWS, in the specific case, it probably even causes the error. >=20 > When EC2 instance is configured with instance profile, as described = here, > = http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec= 2.html, > so new credentials are issued and periodically are renewed.=20 >=20 > And this is the error we see in the log from time to time (when = running > Ignite in the clustered mode): >=20 > /ERROR [tcp-client-disco-reconnector-#5%%] o.a.i.s.d.t.TcpDiscoverySpi > [null] - Failed to get registered addresses from IP fi > nder on start (retrying every 2000 ms). > org.apache.ignite.spi.IgniteSpiException: Failed to list objects in = the > bucket:=20 > at > = org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder.get= RegisteredAddresses(TcpDiscoveryS3IpFinder.java:168) > ~[ignite-aws-1.7.0.ja > r!/:1.7.0] > at > = org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.registeredAddresses(Tc= pDiscoverySpi.java:1600) > ~[ignite-core-1.7.0.jar!/:1.7.0] > at > = org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.resolvedAddresses(TcpD= iscoverySpi.java:1549) > ~[ignite-core-1.7.0.jar!/:1.7.0] > at > = org.apache.ignite.spi.discovery.tcp.ClientImpl.joinTopology(ClientImpl.jav= a:475) > [ignite-core-1.7.0.jar!/:1.7.0] > at > = org.apache.ignite.spi.discovery.tcp.ClientImpl.access$900(ClientImpl.java:= 118) > [ignite-core-1.7.0.jar!/:1.7.0] > at > = org.apache.ignite.spi.discovery.tcp.ClientImpl$Reconnector.body(ClientImpl= .java:1175) > [ignite-core-1.7.0.jar!/:1.7.0] > at > org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) > [ignite-core-1.7.0.jar!/:1.7.0] > Caused by: com.amazonaws.services.s3.model.AmazonS3Exception: The = provided > token has expired. (Service: Amazon S3; Status Code: 400; Error Code: > ExpiredToken;=20 > Request ID: EFDFC0BD8F4421AA) > at > = com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.j= ava:1307) > ~[aws-java-sdk-core-1.10.50.jar!/:na] > at > = com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.jav= a:894) > ~[aws-java-sdk-core-1.10.50.jar!/:na] > at > = com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:59= 7) > ~[aws-java-sdk-core-1.10.50.jar!/:na] > at > = com.amazonaws.http.AmazonHttpClient.doExecute(AmazonHttpClient.java:363) > ~[aws-java-sdk-core-1.10.50.jar!/:na] > at > = com.amazonaws.http.AmazonHttpClient.executeWithTimer(AmazonHttpClient.java= :329) > ~[aws-java-sdk-core-1.10.50.jar!/:na] > at > com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:308) > ~[aws-java-sdk-core-1.10.50.jar!/:na] > at > = com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3595) > ~[aws-java-sdk-s3-1.10.29.jar!/:na] > at > = com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3548) > ~[aws-java-sdk-s3-1.10.29.jar!/:na] > at > = com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:6= 47) > ~[aws-java-sdk-s3-1.10.29.jar!/:na] > at > = com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:6= 26) > ~[aws-java-sdk-s3-1.10.29.jar!/:na] > at > = org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder.get= RegisteredAddresses(TcpDiscoveryS3IpFinder.java:128) > ~[ignite-aws-1.7.0.ja > r!/:1.7.0] > ... 6 common frames omitted/ >=20 > Which probably could be due to S3 library is not being worked properly = with > EC2 instance profile. So, using the latest S3 AWS SDK, would be a good = thing > to try, whether this indeed was fixed in the new version. >=20 >=20 >=20 > -- > View this message in context: = http://apache-ignite-users.70518.x6.nabble.com/Old-AWS-SDK-version-why-tp9= 824p9855.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. --Apple-Mail=_4FDCBD80-45E1-4975-890D-0B902DE88443 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Most likely the issue is not related to SDK version. It=E2=80=99= s related to your AWS account. Here is a discussion around a similar = issue
https://github.com/aws/aws-sdk-ruby/issues/808

In any case, you can = quickly check your assumptions in regards to an outdated SDK by changing = SDK version in ignite-aws pom.xml directly or by relating the old jars = with the new one.

=E2=80=94
Denis

On = Jan 3, 2017, at 11:55 AM, zshamrock <aliaksandr.kazlou@gmail.com> wrote:

Why = I ask. It is not only matter of depending on the latest version, but = for
AWS, in the specific case, it probably even causes the = error.

When EC2 instance is configured with = instance profile, as described here,
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-fo= r-amazon-ec2.html,
so new credentials are issued and = periodically are renewed.

And this is the = error we see in the log from time to time (when running
Ignite in the clustered mode):

/ERROR [tcp-client-disco-reconnector-#5%%] = o.a.i.s.d.t.TcpDiscoverySpi
[null] - Failed to get = registered addresses from IP fi
nder on start (retrying = every 2000 ms).
org.apache.ignite.spi.IgniteSpiException: = Failed to list objects in the
bucket:
=        at
org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3I= pFinder.getRegisteredAddresses(TcpDiscoveryS3IpFinder.java:168)
~[ignite-aws-1.7.0.ja
r!/:1.7.0]
=        at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.registeredA= ddresses(TcpDiscoverySpi.java:1600)
~[ignite-core-1.7.0.jar!/:1.7.0]
=        at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.resolvedAdd= resses(TcpDiscoverySpi.java:1549)
~[ignite-core-1.7.0.jar!/:1.7.0]
=        at
org.apache.ignite.spi.discovery.tcp.ClientImpl.joinTopology(Cli= entImpl.java:475)
[ignite-core-1.7.0.jar!/:1.7.0]
       at
org.apache.ignite.spi.discovery.tcp.ClientImpl.access$900(Clien= tImpl.java:118)
[ignite-core-1.7.0.jar!/:1.7.0]
       at
org.apache.ignite.spi.discovery.tcp.ClientImpl$Reconnector.body= (ClientImpl.java:1175)
[ignite-core-1.7.0.jar!/:1.7.0]
       at
org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:= 62)
[ignite-core-1.7.0.jar!/:1.7.0]
Caused = by: com.amazonaws.services.s3.model.AmazonS3Exception: The provided
token has expired. (Service: Amazon S3; Status Code: 400; = Error Code:
ExpiredToken;
Request ID: = EFDFC0BD8F4421AA)
=        at
com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonH= ttpClient.java:1307)
~[aws-java-sdk-core-1.10.50.jar!/:na]
=        at
com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHtt= pClient.java:894)
~[aws-java-sdk-core-1.10.50.jar!/:na]
       at
com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpCli= ent.java:597)
~[aws-java-sdk-core-1.10.50.jar!/:na]
       at
com.amazonaws.http.AmazonHttpClient.doExecute(AmazonHttpClient.= java:363)
~[aws-java-sdk-core-1.10.50.jar!/:na]
       at
com.amazonaws.http.AmazonHttpClient.executeWithTimer(AmazonHttp= Client.java:329)
~[aws-java-sdk-core-1.10.50.jar!/:na]
       at
com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.ja= va:308)
~[aws-java-sdk-core-1.10.50.jar!/:na]
=        at
com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.= java:3595)
~[aws-java-sdk-s3-1.10.29.jar!/:na]
       at
com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.= java:3548)
~[aws-java-sdk-s3-1.10.29.jar!/:na]
       at
com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Cl= ient.java:647)
~[aws-java-sdk-s3-1.10.29.jar!/:na]
       at
com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Cl= ient.java:626)
~[aws-java-sdk-s3-1.10.29.jar!/:na]
       at
org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3I= pFinder.getRegisteredAddresses(TcpDiscoveryS3IpFinder.java:128)
~[ignite-aws-1.7.0.ja
r!/:1.7.0]
=        ... 6 common frames = omitted/

Which probably could be due to S3 = library is not being worked properly with
EC2 instance = profile. So, using the latest S3 AWS SDK, would be a good thing
to try, whether this indeed was fixed in the new version.



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Old-AWS-SDK-vers= ion-why-tp9824p9855.html
Sent from the Apache Ignite = Users mailing list archive at Nabble.com.

= --Apple-Mail=_4FDCBD80-45E1-4975-890D-0B902DE88443--