ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anil <anilk...@gmail.com>
Subject Re: 2.0
Date Sat, 01 Apr 2017 03:32:25 GMT
Thank you Denis and Val.

I will post the debug logs. thanks.

On 31 March 2017 at 22:02, Denis Magda <dmagda@apache.org> wrote:

> Anil,
>
> Try to connect to the S3 bucket you specified in the configuration
>
> <property name="bucketName" value="testing-ignite"/>
>
> and check you see there IP address the cluster nodes should have written
> there.
>
> If there is no address then something goes wrong with networking. This
> message proves this:
> 2017-03-29 10:23:39 WARN  MacAddressUtil:136 - Failed to find a usable
> hardware address from the network interfaces; using random bytes:
> c6:25:2b:74:0a:78:fc:66
>
> Also I would suggest enabling DEBUG level for loggers.
>
> —
> Denis
>
> On Mar 31, 2017, at 9:28 AM, Anil <anilklce@gmail.com> wrote:
>
> I will look into netty documentation.
>
> i see following log -
>
> 2017-03-31 10:04:55 INFO  TcpDiscoverySpi:475 - Successfully bound to TCP
> port [port=47500, localHost=0.0.0.0/0.0.0.0, locNodeId=3cd86374-c96c-4961-
> bf9f-fc058f89ddc0]
> 2017-03-31 10:04:55 WARN  TcpDiscoveryS3IpFinder:480 - Amazon client
> configuration is not set (will use default).
>
> Was it Ok ?
>
> On 30 March 2017 at 23:29, vkulichenko <valentin.kulichenko@gmail.com>
> wrote:
>
>> Anil,
>>
>> So it's coming from vertx then. I would refer to their documentation and
>> other resources to understand why this warning is shown (my guess is that
>> it's specific to AWS). As I said, Ignite node is started successfully.
>>
>> -Val
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-users.705
>> 18.x6.nabble.com/2-0-tp11487p11580.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>
>

Mime
View raw message