You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Anil <an...@gmail.com> on 2017/04/01 03:32:25 UTC
Re: 2.0
Thank you Denis and Val.
I will post the debug logs. thanks.
On 31 March 2017 at 22:02, Denis Magda <dm...@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 <an...@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 <va...@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.
>>
>
>
>
Re: 2.0
Posted by Anil <an...@gmail.com>.
Hi Nikolai,
Yes. It is working :).
and vertx-ignite cluster also joined the cluster now :) . not sure how it
started working :)
Thanks.
On 3 April 2017 at 21:44, Nikolai Tikhonov <nt...@apache.org> wrote:
> I mean that host equals machine. Can you try to start nodes with
> TcpDiscoveryVmIpFinder and check that ignite will be work properly?
>
> On Mon, Apr 3, 2017 at 7:08 PM, Anil <an...@gmail.com> wrote:
>
>> Hi Nikolai,
>>
>> What do you mean by hosts ? Two machines able to connect each other.
>>
>> Thanks
>>
>> On 3 April 2017 at 21:12, Nikolai Tikhonov <nt...@apache.org> wrote:
>>
>>> Hi Anil,
>>>
>>> Are you sure that you this addresses (172.31.1.189#47500,
>>> 172.31.7.192#47500) reacheable from the hosts? Could you check it by telnet?
>>>
>>> On Mon, Apr 3, 2017 at 12:20 PM, Anil <an...@gmail.com> wrote:
>>>
>>>> Hi Val,
>>>>
>>>> I tried without vertx and still nodes not joining the cluster. Looks
>>>> like the issue is not because of vertx.
>>>>
>>>> Thanks
>>>>
>>>> On 3 April 2017 at 12:13, Anil <an...@gmail.com> wrote:
>>>>
>>>>> Hi Val,
>>>>>
>>>>> Can you help me in understanding following -
>>>>>
>>>>> 1. I see empty files created with 127.0.0.1#47500 and
>>>>> 0:0:0:0:0:0:0:1%lo#47500 along with actualipaddress#port. any specific
>>>>> reason ?
>>>>>
>>>>> - A number of nodes will have single set of 127.0.0.1#47500 and
>>>>> 0:0:0:0:0:0:0:1%lo#47500 empty files.
>>>>>
>>>>> 2. a node is deleting the empty file of other node. the delete of file
>>>>> happens only during un-register (as per the code).
>>>>>
>>>>> logs of 192 -
>>>>>
>>>>> 2017-04-03 06:20:03 WARN TcpDiscoveryS3IpFinder:480 - Creating file
>>>>> in the bucket with name - 172.31.7.192#47500
>>>>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - listing the
>>>>> bucket objects - 3
>>>>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>>> registered (before) - 0:0:0:0:0:0:0:1%lo - 47500
>>>>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>>> registered - 0:0:0:0:0:0:0:1%lo - 47500
>>>>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>>> registered (before) - 127.0.0.1 - 47500
>>>>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>>> registered - 127.0.0.1 - 47500
>>>>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>>> registered (before) - 172.31.1.189 - 47500
>>>>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>>> registered - 172.31.1.189 - 47500
>>>>> *2017-04-03 06:21:15 WARN TcpDiscoveryS3IpFinder:480 - deleting file
>>>>> in the bucket with name - 172.31.1.189#47500*
>>>>> 2017-04-03 06:21:15 WARN TcpDiscoveryS3IpFinder:480 - Creating file
>>>>> in the bucket with name - 172.31.7.192#47500
>>>>>
>>>>> logs of 189 -
>>>>>
>>>>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - listing the
>>>>> bucket objects - 3
>>>>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>>> registered (before) - 0:0:0:0:0:0:0:1%lo - 47500
>>>>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>>> registered - 0:0:0:0:0:0:0:1%lo - 47500
>>>>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>>> registered (before) - 127.0.0.1 - 47500
>>>>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>>> registered - 127.0.0.1 - 47500
>>>>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>>> registered (before) - 172.31.7.192 - 47500
>>>>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>>> registered - 172.31.7.192 - 47500
>>>>> *2017-04-03 06:24:00 WARN TcpDiscoveryS3IpFinder:480 - deleting file
>>>>> in the bucket with name - 172.31.7.192#47500*
>>>>> 2017-04-03 06:24:00 WARN TcpDiscoveryS3IpFinder:480 - Creating file
>>>>> in the bucket with name - 172.31.1.189#47500
>>>>>
>>>>> Thanks
>>>>>
>>>>> On 2 April 2017 at 14:34, Anil <an...@gmail.com> wrote:
>>>>>
>>>>>> Hi Val,
>>>>>>
>>>>>> Nodes not joining the cluster. I just shared the logs to understand
>>>>>> if there is any info in the logs.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On 2 April 2017 at 11:32, vkulichenko <va...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Anil,
>>>>>>>
>>>>>>> I'm not sure I understand what is the issue in the first place. What
>>>>>>> is not
>>>>>>> working?
>>>>>>>
>>>>>>> -Val
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> View this message in context: http://apache-ignite-users.705
>>>>>>> 18.x6.nabble.com/2-0-tp11487p11640.html
>>>>>>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: 2.0
Posted by Nikolai Tikhonov <nt...@apache.org>.
I mean that host equals machine. Can you try to start nodes with
TcpDiscoveryVmIpFinder and check that ignite will be work properly?
On Mon, Apr 3, 2017 at 7:08 PM, Anil <an...@gmail.com> wrote:
> Hi Nikolai,
>
> What do you mean by hosts ? Two machines able to connect each other.
>
> Thanks
>
> On 3 April 2017 at 21:12, Nikolai Tikhonov <nt...@apache.org> wrote:
>
>> Hi Anil,
>>
>> Are you sure that you this addresses (172.31.1.189#47500,
>> 172.31.7.192#47500) reacheable from the hosts? Could you check it by telnet?
>>
>> On Mon, Apr 3, 2017 at 12:20 PM, Anil <an...@gmail.com> wrote:
>>
>>> Hi Val,
>>>
>>> I tried without vertx and still nodes not joining the cluster. Looks
>>> like the issue is not because of vertx.
>>>
>>> Thanks
>>>
>>> On 3 April 2017 at 12:13, Anil <an...@gmail.com> wrote:
>>>
>>>> Hi Val,
>>>>
>>>> Can you help me in understanding following -
>>>>
>>>> 1. I see empty files created with 127.0.0.1#47500 and
>>>> 0:0:0:0:0:0:0:1%lo#47500 along with actualipaddress#port. any specific
>>>> reason ?
>>>>
>>>> - A number of nodes will have single set of 127.0.0.1#47500 and
>>>> 0:0:0:0:0:0:0:1%lo#47500 empty files.
>>>>
>>>> 2. a node is deleting the empty file of other node. the delete of file
>>>> happens only during un-register (as per the code).
>>>>
>>>> logs of 192 -
>>>>
>>>> 2017-04-03 06:20:03 WARN TcpDiscoveryS3IpFinder:480 - Creating file in
>>>> the bucket with name - 172.31.7.192#47500
>>>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - listing the
>>>> bucket objects - 3
>>>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>> registered (before) - 0:0:0:0:0:0:0:1%lo - 47500
>>>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>> registered - 0:0:0:0:0:0:0:1%lo - 47500
>>>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>> registered (before) - 127.0.0.1 - 47500
>>>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>> registered - 127.0.0.1 - 47500
>>>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>> registered (before) - 172.31.1.189 - 47500
>>>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>> registered - 172.31.1.189 - 47500
>>>> *2017-04-03 06:21:15 WARN TcpDiscoveryS3IpFinder:480 - deleting file
>>>> in the bucket with name - 172.31.1.189#47500*
>>>> 2017-04-03 06:21:15 WARN TcpDiscoveryS3IpFinder:480 - Creating file in
>>>> the bucket with name - 172.31.7.192#47500
>>>>
>>>> logs of 189 -
>>>>
>>>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - listing the
>>>> bucket objects - 3
>>>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>> registered (before) - 0:0:0:0:0:0:0:1%lo - 47500
>>>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>> registered - 0:0:0:0:0:0:0:1%lo - 47500
>>>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>> registered (before) - 127.0.0.1 - 47500
>>>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>> registered - 127.0.0.1 - 47500
>>>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>> registered (before) - 172.31.7.192 - 47500
>>>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>>> registered - 172.31.7.192 - 47500
>>>> *2017-04-03 06:24:00 WARN TcpDiscoveryS3IpFinder:480 - deleting file
>>>> in the bucket with name - 172.31.7.192#47500*
>>>> 2017-04-03 06:24:00 WARN TcpDiscoveryS3IpFinder:480 - Creating file in
>>>> the bucket with name - 172.31.1.189#47500
>>>>
>>>> Thanks
>>>>
>>>> On 2 April 2017 at 14:34, Anil <an...@gmail.com> wrote:
>>>>
>>>>> Hi Val,
>>>>>
>>>>> Nodes not joining the cluster. I just shared the logs to understand if
>>>>> there is any info in the logs.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On 2 April 2017 at 11:32, vkulichenko <va...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Anil,
>>>>>>
>>>>>> I'm not sure I understand what is the issue in the first place. What
>>>>>> is not
>>>>>> working?
>>>>>>
>>>>>> -Val
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> View this message in context: http://apache-ignite-users.705
>>>>>> 18.x6.nabble.com/2-0-tp11487p11640.html
>>>>>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
Re: 2.0
Posted by Anil <an...@gmail.com>.
Hi Nikolai,
What do you mean by hosts ? Two machines able to connect each other.
Thanks
On 3 April 2017 at 21:12, Nikolai Tikhonov <nt...@apache.org> wrote:
> Hi Anil,
>
> Are you sure that you this addresses (172.31.1.189#47500,
> 172.31.7.192#47500) reacheable from the hosts? Could you check it by telnet?
>
> On Mon, Apr 3, 2017 at 12:20 PM, Anil <an...@gmail.com> wrote:
>
>> Hi Val,
>>
>> I tried without vertx and still nodes not joining the cluster. Looks like
>> the issue is not because of vertx.
>>
>> Thanks
>>
>> On 3 April 2017 at 12:13, Anil <an...@gmail.com> wrote:
>>
>>> Hi Val,
>>>
>>> Can you help me in understanding following -
>>>
>>> 1. I see empty files created with 127.0.0.1#47500 and
>>> 0:0:0:0:0:0:0:1%lo#47500 along with actualipaddress#port. any specific
>>> reason ?
>>>
>>> - A number of nodes will have single set of 127.0.0.1#47500 and
>>> 0:0:0:0:0:0:0:1%lo#47500 empty files.
>>>
>>> 2. a node is deleting the empty file of other node. the delete of file
>>> happens only during un-register (as per the code).
>>>
>>> logs of 192 -
>>>
>>> 2017-04-03 06:20:03 WARN TcpDiscoveryS3IpFinder:480 - Creating file in
>>> the bucket with name - 172.31.7.192#47500
>>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - listing the
>>> bucket objects - 3
>>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>> registered (before) - 0:0:0:0:0:0:0:1%lo - 47500
>>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>> registered - 0:0:0:0:0:0:0:1%lo - 47500
>>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>> registered (before) - 127.0.0.1 - 47500
>>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>> registered - 127.0.0.1 - 47500
>>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>> registered (before) - 172.31.1.189 - 47500
>>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>> registered - 172.31.1.189 - 47500
>>> *2017-04-03 06:21:15 WARN TcpDiscoveryS3IpFinder:480 - deleting file in
>>> the bucket with name - 172.31.1.189#47500*
>>> 2017-04-03 06:21:15 WARN TcpDiscoveryS3IpFinder:480 - Creating file in
>>> the bucket with name - 172.31.7.192#47500
>>>
>>> logs of 189 -
>>>
>>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - listing the
>>> bucket objects - 3
>>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>> registered (before) - 0:0:0:0:0:0:0:1%lo - 47500
>>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>> registered - 0:0:0:0:0:0:0:1%lo - 47500
>>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>> registered (before) - 127.0.0.1 - 47500
>>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>> registered - 127.0.0.1 - 47500
>>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>> registered (before) - 172.31.7.192 - 47500
>>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>>> registered - 172.31.7.192 - 47500
>>> *2017-04-03 06:24:00 WARN TcpDiscoveryS3IpFinder:480 - deleting file in
>>> the bucket with name - 172.31.7.192#47500*
>>> 2017-04-03 06:24:00 WARN TcpDiscoveryS3IpFinder:480 - Creating file in
>>> the bucket with name - 172.31.1.189#47500
>>>
>>> Thanks
>>>
>>> On 2 April 2017 at 14:34, Anil <an...@gmail.com> wrote:
>>>
>>>> Hi Val,
>>>>
>>>> Nodes not joining the cluster. I just shared the logs to understand if
>>>> there is any info in the logs.
>>>>
>>>> Thanks
>>>>
>>>> On 2 April 2017 at 11:32, vkulichenko <va...@gmail.com>
>>>> wrote:
>>>>
>>>>> Anil,
>>>>>
>>>>> I'm not sure I understand what is the issue in the first place. What
>>>>> is not
>>>>> working?
>>>>>
>>>>> -Val
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> View this message in context: http://apache-ignite-users.705
>>>>> 18.x6.nabble.com/2-0-tp11487p11640.html
>>>>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>>>>
>>>>
>>>>
>>>
>>
>
Re: 2.0
Posted by Nikolai Tikhonov <nt...@apache.org>.
Hi Anil,
Are you sure that you this addresses (172.31.1.189#47500,
172.31.7.192#47500) reacheable from the hosts? Could you check it by telnet?
On Mon, Apr 3, 2017 at 12:20 PM, Anil <an...@gmail.com> wrote:
> Hi Val,
>
> I tried without vertx and still nodes not joining the cluster. Looks like
> the issue is not because of vertx.
>
> Thanks
>
> On 3 April 2017 at 12:13, Anil <an...@gmail.com> wrote:
>
>> Hi Val,
>>
>> Can you help me in understanding following -
>>
>> 1. I see empty files created with 127.0.0.1#47500 and
>> 0:0:0:0:0:0:0:1%lo#47500 along with actualipaddress#port. any specific
>> reason ?
>>
>> - A number of nodes will have single set of 127.0.0.1#47500 and
>> 0:0:0:0:0:0:0:1%lo#47500 empty files.
>>
>> 2. a node is deleting the empty file of other node. the delete of file
>> happens only during un-register (as per the code).
>>
>> logs of 192 -
>>
>> 2017-04-03 06:20:03 WARN TcpDiscoveryS3IpFinder:480 - Creating file in
>> the bucket with name - 172.31.7.192#47500
>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - listing the bucket
>> objects - 3
>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>> registered (before) - 0:0:0:0:0:0:0:1%lo - 47500
>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>> registered - 0:0:0:0:0:0:0:1%lo - 47500
>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>> registered (before) - 127.0.0.1 - 47500
>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>> registered - 127.0.0.1 - 47500
>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>> registered (before) - 172.31.1.189 - 47500
>> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>> registered - 172.31.1.189 - 47500
>> *2017-04-03 06:21:15 WARN TcpDiscoveryS3IpFinder:480 - deleting file in
>> the bucket with name - 172.31.1.189#47500*
>> 2017-04-03 06:21:15 WARN TcpDiscoveryS3IpFinder:480 - Creating file in
>> the bucket with name - 172.31.7.192#47500
>>
>> logs of 189 -
>>
>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - listing the bucket
>> objects - 3
>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>> registered (before) - 0:0:0:0:0:0:0:1%lo - 47500
>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>> registered - 0:0:0:0:0:0:0:1%lo - 47500
>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>> registered (before) - 127.0.0.1 - 47500
>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>> registered - 127.0.0.1 - 47500
>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>> registered (before) - 172.31.7.192 - 47500
>> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
>> registered - 172.31.7.192 - 47500
>> *2017-04-03 06:24:00 WARN TcpDiscoveryS3IpFinder:480 - deleting file in
>> the bucket with name - 172.31.7.192#47500*
>> 2017-04-03 06:24:00 WARN TcpDiscoveryS3IpFinder:480 - Creating file in
>> the bucket with name - 172.31.1.189#47500
>>
>> Thanks
>>
>> On 2 April 2017 at 14:34, Anil <an...@gmail.com> wrote:
>>
>>> Hi Val,
>>>
>>> Nodes not joining the cluster. I just shared the logs to understand if
>>> there is any info in the logs.
>>>
>>> Thanks
>>>
>>> On 2 April 2017 at 11:32, vkulichenko <va...@gmail.com>
>>> wrote:
>>>
>>>> Anil,
>>>>
>>>> I'm not sure I understand what is the issue in the first place. What is
>>>> not
>>>> working?
>>>>
>>>> -Val
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context: http://apache-ignite-users.705
>>>> 18.x6.nabble.com/2-0-tp11487p11640.html
>>>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>>>
>>>
>>>
>>
>
Re: 2.0
Posted by Anil <an...@gmail.com>.
Hi Val,
I tried without vertx and still nodes not joining the cluster. Looks like
the issue is not because of vertx.
Thanks
On 3 April 2017 at 12:13, Anil <an...@gmail.com> wrote:
> Hi Val,
>
> Can you help me in understanding following -
>
> 1. I see empty files created with 127.0.0.1#47500 and
> 0:0:0:0:0:0:0:1%lo#47500 along with actualipaddress#port. any specific
> reason ?
>
> - A number of nodes will have single set of 127.0.0.1#47500 and
> 0:0:0:0:0:0:0:1%lo#47500 empty files.
>
> 2. a node is deleting the empty file of other node. the delete of file
> happens only during un-register (as per the code).
>
> logs of 192 -
>
> 2017-04-03 06:20:03 WARN TcpDiscoveryS3IpFinder:480 - Creating file in
> the bucket with name - 172.31.7.192#47500
> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - listing the bucket
> objects - 3
> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
> registered (before) - 0:0:0:0:0:0:0:1%lo - 47500
> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
> registered - 0:0:0:0:0:0:0:1%lo - 47500
> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
> registered (before) - 127.0.0.1 - 47500
> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
> registered - 127.0.0.1 - 47500
> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
> registered (before) - 172.31.1.189 - 47500
> 2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
> registered - 172.31.1.189 - 47500
> *2017-04-03 06:21:15 WARN TcpDiscoveryS3IpFinder:480 - deleting file in
> the bucket with name - 172.31.1.189#47500*
> 2017-04-03 06:21:15 WARN TcpDiscoveryS3IpFinder:480 - Creating file in
> the bucket with name - 172.31.7.192#47500
>
> logs of 189 -
>
> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - listing the bucket
> objects - 3
> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
> registered (before) - 0:0:0:0:0:0:0:1%lo - 47500
> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
> registered - 0:0:0:0:0:0:0:1%lo - 47500
> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
> registered (before) - 127.0.0.1 - 47500
> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
> registered - 127.0.0.1 - 47500
> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
> registered (before) - 172.31.7.192 - 47500
> 2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
> registered - 172.31.7.192 - 47500
> *2017-04-03 06:24:00 WARN TcpDiscoveryS3IpFinder:480 - deleting file in
> the bucket with name - 172.31.7.192#47500*
> 2017-04-03 06:24:00 WARN TcpDiscoveryS3IpFinder:480 - Creating file in
> the bucket with name - 172.31.1.189#47500
>
> Thanks
>
> On 2 April 2017 at 14:34, Anil <an...@gmail.com> wrote:
>
>> Hi Val,
>>
>> Nodes not joining the cluster. I just shared the logs to understand if
>> there is any info in the logs.
>>
>> Thanks
>>
>> On 2 April 2017 at 11:32, vkulichenko <va...@gmail.com>
>> wrote:
>>
>>> Anil,
>>>
>>> I'm not sure I understand what is the issue in the first place. What is
>>> not
>>> working?
>>>
>>> -Val
>>>
>>>
>>>
>>> --
>>> View this message in context: http://apache-ignite-users.705
>>> 18.x6.nabble.com/2-0-tp11487p11640.html
>>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>>
>>
>>
>
Re: 2.0
Posted by Anil <an...@gmail.com>.
Hi Val,
Can you help me in understanding following -
1. I see empty files created with 127.0.0.1#47500 and
0:0:0:0:0:0:0:1%lo#47500 along with actualipaddress#port. any specific
reason ?
- A number of nodes will have single set of 127.0.0.1#47500 and
0:0:0:0:0:0:0:1%lo#47500 empty files.
2. a node is deleting the empty file of other node. the delete of file
happens only during un-register (as per the code).
logs of 192 -
2017-04-03 06:20:03 WARN TcpDiscoveryS3IpFinder:480 - Creating file in the
bucket with name - 172.31.7.192#47500
2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - listing the bucket
objects - 3
2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
registered (before) - 0:0:0:0:0:0:0:1%lo - 47500
2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
registered - 0:0:0:0:0:0:0:1%lo - 47500
2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
registered (before) - 127.0.0.1 - 47500
2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
registered - 127.0.0.1 - 47500
2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
registered (before) - 172.31.1.189 - 47500
2017-04-03 06:21:05 WARN TcpDiscoveryS3IpFinder:480 - Address to be
registered - 172.31.1.189 - 47500
*2017-04-03 06:21:15 WARN TcpDiscoveryS3IpFinder:480 - deleting file in
the bucket with name - 172.31.1.189#47500*
2017-04-03 06:21:15 WARN TcpDiscoveryS3IpFinder:480 - Creating file in the
bucket with name - 172.31.7.192#47500
logs of 189 -
2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - listing the bucket
objects - 3
2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
registered (before) - 0:0:0:0:0:0:0:1%lo - 47500
2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
registered - 0:0:0:0:0:0:0:1%lo - 47500
2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
registered (before) - 127.0.0.1 - 47500
2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
registered - 127.0.0.1 - 47500
2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
registered (before) - 172.31.7.192 - 47500
2017-04-03 06:23:50 WARN TcpDiscoveryS3IpFinder:480 - Address to be
registered - 172.31.7.192 - 47500
*2017-04-03 06:24:00 WARN TcpDiscoveryS3IpFinder:480 - deleting file in
the bucket with name - 172.31.7.192#47500*
2017-04-03 06:24:00 WARN TcpDiscoveryS3IpFinder:480 - Creating file in the
bucket with name - 172.31.1.189#47500
Thanks
On 2 April 2017 at 14:34, Anil <an...@gmail.com> wrote:
> Hi Val,
>
> Nodes not joining the cluster. I just shared the logs to understand if
> there is any info in the logs.
>
> Thanks
>
> On 2 April 2017 at 11:32, vkulichenko <va...@gmail.com>
> wrote:
>
>> Anil,
>>
>> I'm not sure I understand what is the issue in the first place. What is
>> not
>> working?
>>
>> -Val
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-users.705
>> 18.x6.nabble.com/2-0-tp11487p11640.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>
Re: 2.0
Posted by Anil <an...@gmail.com>.
Hi Val,
Nodes not joining the cluster. I just shared the logs to understand if
there is any info in the logs.
Thanks
On 2 April 2017 at 11:32, vkulichenko <va...@gmail.com> wrote:
> Anil,
>
> I'm not sure I understand what is the issue in the first place. What is not
> working?
>
> -Val
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/2-0-tp11487p11640.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
Re: 2.0
Posted by vkulichenko <va...@gmail.com>.
Anil,
I'm not sure I understand what is the issue in the first place. What is not
working?
-Val
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/2-0-tp11487p11640.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: 2.0
Posted by Anil <an...@gmail.com>.
Hi Denis and Val,
I have added the extra logs in TcpDiscoveryS3IpFinder#registerAddresses and
have attached the complete logs
Info logs :
on 189 - logs-189.txt
on 192 - logs-192.txt
Debug logs :
debug logs on 192 - debug.zip
please let me know if you see any issues. thanks
On 1 April 2017 at 09:02, Anil <an...@gmail.com> wrote:
> Thank you Denis and Val.
>
> I will post the debug logs. thanks.
>
> On 31 March 2017 at 22:02, Denis Magda <dm...@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 <an...@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 <va...@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.
>>>
>>
>>
>>
>