2.0

classic Classic list List threaded Threaded
23 messages Options
12
leathurman leathurman
Reply | Threaded
Open this post in threaded view
|

2.0

Hi all,

We have upgraded to 1.9 and noticed the following issue:


I understand this is to be fixed in 2.0. 

Is there any indicated when this is planned to be released?

Regards
Lea Thurman

--
Lea Thurman
OneSoon Limited
Manchester Business Park
3000 Aviator Way
Manchester M22 5TG

mob:   <a href="tel:+44+(0)+7545+828+526" value="+447973182802" style="color:rgb(17,85,204)" target="_blank">+44 (0) 7545 828 526
tel:      <a href="tel:%2B44%20%280%29%20333%20666%207366" value="+443336667366" style="color:rgb(17,85,204)" target="_blank">+44 (0) 333 666 7366
email:  
[hidden email]
web:    
www.adalyser.com

Adalyser is a registered trademark and trading name of OneSoon Limited
OneSoon is registered in England and Wales Company Number 04746025
ptupitsyn ptupitsyn
Reply | Threaded
Open this post in threaded view
|

Re: 2.0

According to the dev list thread (http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-0-Release-td15690.html),
you can expect 2.0 by the end of the April.


On Tue, Mar 28, 2017 at 10:41 AM, Lea Thurman <[hidden email]> wrote:
Hi all,

We have upgraded to 1.9 and noticed the following issue:


I understand this is to be fixed in 2.0. 

Is there any indicated when this is planned to be released?

Regards
Lea Thurman

--
Lea Thurman
OneSoon Limited
Manchester Business Park
3000 Aviator Way
Manchester M22 5TG

mob:   <a href="tel:+44+(0)+7545+828+526" value="+447973182802" style="color:rgb(17,85,204)" target="_blank">+44 (0) 7545 828 526
tel:      <a href="tel:%2B44%20%280%29%20333%20666%207366" value="+443336667366" style="color:rgb(17,85,204)" target="_blank">+44 (0) 333 666 7366
email:  
[hidden email]
web:    
www.adalyser.com

Adalyser is a registered trademark and trading name of OneSoon Limited
OneSoon is registered in England and Wales Company Number 04746025

leathurman leathurman
Reply | Threaded
Open this post in threaded view
|

Re: 2.0

Thanks Pavel

Would it be worth us reverting to an earlier release. Any idea when it was introduced?

Regards
Lea Thurman.

On 28 March 2017 at 08:46, Pavel Tupitsyn <[hidden email]> wrote:
According to the dev list thread (http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-0-Release-td15690.html),
you can expect 2.0 by the end of the April.


On Tue, Mar 28, 2017 at 10:41 AM, Lea Thurman <[hidden email]> wrote:
Hi all,

We have upgraded to 1.9 and noticed the following issue:


I understand this is to be fixed in 2.0. 

Is there any indicated when this is planned to be released?

Regards
Lea Thurman

--
Lea Thurman
OneSoon Limited
Manchester Business Park
3000 Aviator Way
Manchester M22 5TG

mob:   <a href="tel:+44+(0)+7545+828+526" value="+447973182802" style="color:rgb(17,85,204)" target="_blank">+44 (0) 7545 828 526
tel:      <a href="tel:%2B44%20%280%29%20333%20666%207366" value="+443336667366" style="color:rgb(17,85,204)" target="_blank">+44 (0) 333 666 7366
email:  
[hidden email]
web:    
www.adalyser.com

Adalyser is a registered trademark and trading name of OneSoon Limited
OneSoon is registered in England and Wales Company Number 04746025




--
Lea Thurman
OneSoon Limited
Manchester Business Park
3000 Aviator Way
Manchester M22 5TG

mob:   <a href="tel:+44+(0)+7545+828+526" value="+447973182802" style="color:rgb(17,85,204)" target="_blank">+44 (0) 7545 828 526
tel:      <a href="tel:%2B44%20%280%29%20333%20666%207366" value="+443336667366" style="color:rgb(17,85,204)" target="_blank">+44 (0) 333 666 7366
email:  
[hidden email]
web:    
www.adalyser.com

Adalyser is a registered trademark and trading name of OneSoon Limited
OneSoon is registered in England and Wales Company Number 04746025
Denis Magda-2 Denis Magda-2
Reply | Threaded
Open this post in threaded view
|

Re: 2.0

Lea, 

If you can’t wait for 2.0 release I would suggest you pick my commit, merge it to your fork of Ignite 1.9 release and build it from sources.

Does it work for you?

Denis

On Mar 28, 2017, at 1:21 AM, Lea Thurman <[hidden email]> wrote:

Thanks Pavel

Would it be worth us reverting to an earlier release. Any idea when it was introduced?

Regards
Lea Thurman.

On 28 March 2017 at 08:46, Pavel Tupitsyn <[hidden email]> wrote:
According to the dev list thread (http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-0-Release-td15690.html),
you can expect 2.0 by the end of the April.


On Tue, Mar 28, 2017 at 10:41 AM, Lea Thurman <[hidden email]> wrote:
Hi all,

We have upgraded to 1.9 and noticed the following issue:


I understand this is to be fixed in 2.0. 

Is there any indicated when this is planned to be released?

Regards
Lea Thurman

--
Lea Thurman
OneSoon Limited
Manchester Business Park
3000 Aviator Way
Manchester M22 5TG

mob:   <a href="tel:+44+(0)+7545+828+526" value="+447973182802" style="color:rgb(17,85,204)" target="_blank" class="">+44 (0) 7545 828 526
tel:      <a href="tel:%2B44%20%280%29%20333%20666%207366" value="+443336667366" style="color:rgb(17,85,204)" target="_blank" class="">+44 (0) 333 666 7366
email:  
[hidden email]
web:    
www.adalyser.com

Adalyser is a registered trademark and trading name of OneSoon Limited
OneSoon is registered in England and Wales Company Number 04746025




--
Lea Thurman
OneSoon Limited
Manchester Business Park
3000 Aviator Way
Manchester M22 5TG

mob:   <a href="tel:+44+(0)+7545+828+526" value="+447973182802" style="color:rgb(17,85,204)" target="_blank" class="">+44 (0) 7545 828 526
tel:      <a href="tel:%2B44%20%280%29%20333%20666%207366" value="+443336667366" style="color:rgb(17,85,204)" target="_blank" class="">+44 (0) 333 666 7366
email:  
[hidden email]
web:    
www.adalyser.com

Adalyser is a registered trademark and trading name of OneSoon Limited
OneSoon is registered in England and Wales Company Number 04746025

dsetrakyan dsetrakyan
Reply | Threaded
Open this post in threaded view
|

Re: 2.0

Thanks Denis!

Lea, I just want to clarify that if you manually pick Denis' commit, it will likely fix your issue, but it will not be an official Ignite release and will not have undergone the regular testing and QA cycle that all Ignite releases generally go through.

D.


On Tue, Mar 28, 2017 at 10:19 AM, Denis Magda <[hidden email]> wrote:
Lea, 

If you can’t wait for 2.0 release I would suggest you pick my commit, merge it to your fork of Ignite 1.9 release and build it from sources.

Does it work for you?

Denis

On Mar 28, 2017, at 1:21 AM, Lea Thurman <[hidden email]> wrote:

Thanks Pavel

Would it be worth us reverting to an earlier release. Any idea when it was introduced?

Regards
Lea Thurman.

On 28 March 2017 at 08:46, Pavel Tupitsyn <[hidden email]> wrote:
According to the dev list thread (http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-0-Release-td15690.html),
you can expect 2.0 by the end of the April.


On Tue, Mar 28, 2017 at 10:41 AM, Lea Thurman <[hidden email]> wrote:
Hi all,

We have upgraded to 1.9 and noticed the following issue:


I understand this is to be fixed in 2.0. 

Is there any indicated when this is planned to be released?

Regards
Lea Thurman

--
Lea Thurman
OneSoon Limited
Manchester Business Park
3000 Aviator Way
Manchester M22 5TG

mob:   <a href="tel:+44+(0)+7545+828+526" value="+447973182802" style="color:rgb(17,85,204)" target="_blank">+44 (0) 7545 828 526
tel:      <a href="tel:%2B44%20%280%29%20333%20666%207366" value="+443336667366" style="color:rgb(17,85,204)" target="_blank">+44 (0) 333 666 7366
email:  
[hidden email]
web:    
www.adalyser.com

Adalyser is a registered trademark and trading name of OneSoon Limited
OneSoon is registered in England and Wales Company Number 04746025




--
Lea Thurman
OneSoon Limited
Manchester Business Park
3000 Aviator Way
Manchester M22 5TG

mob:   <a href="tel:+44+(0)+7545+828+526" value="+447973182802" style="color:rgb(17,85,204)" target="_blank">+44 (0) 7545 828 526
tel:      <a href="tel:%2B44%20%280%29%20333%20666%207366" value="+443336667366" style="color:rgb(17,85,204)" target="_blank">+44 (0) 333 666 7366
email:  
[hidden email]
web:    
www.adalyser.com

Adalyser is a registered trademark and trading name of OneSoon Limited
OneSoon is registered in England and Wales Company Number 04746025


Lea Thurman Lea Thurman
Reply | Threaded
Open this post in threaded view
|

Re: 2.0

Hi Dimitry

Yes I think that would work and will give a go.

Thanks
Lea

On 28 Mar 2017, at 6:51 pm, Dmitriy Setrakyan <[hidden email]> wrote:

Thanks Denis!

Lea, I just want to clarify that if you manually pick Denis' commit, it will likely fix your issue, but it will not be an official Ignite release and will not have undergone the regular testing and QA cycle that all Ignite releases generally go through.

D.


On Tue, Mar 28, 2017 at 10:19 AM, Denis Magda <[hidden email]> wrote:
Lea, 

If you can’t wait for 2.0 release I would suggest you pick my commit, merge it to your fork of Ignite 1.9 release and build it from sources.

Does it work for you?

Denis

On Mar 28, 2017, at 1:21 AM, Lea Thurman <[hidden email]> wrote:

Thanks Pavel

Would it be worth us reverting to an earlier release. Any idea when it was introduced?

Regards
Lea Thurman.

On 28 March 2017 at 08:46, Pavel Tupitsyn <[hidden email]> wrote:
According to the dev list thread (http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-0-Release-td15690.html),
you can expect 2.0 by the end of the April.


On Tue, Mar 28, 2017 at 10:41 AM, Lea Thurman <[hidden email]> wrote:
Hi all,

We have upgraded to 1.9 and noticed the following issue:


I understand this is to be fixed in 2.0. 

Is there any indicated when this is planned to be released?

Regards
Lea Thurman

--
Lea Thurman
OneSoon Limited
Manchester Business Park
3000 Aviator Way
Manchester M22 5TG

mob:   <a href="tel:+44+(0)+7545+828+526" value="+447973182802" style="color:rgb(17,85,204)" target="_blank">+44 (0) 7545 828 526
tel:      <a href="tel:%2B44%20%280%29%20333%20666%207366" value="+443336667366" style="color:rgb(17,85,204)" target="_blank">+44 (0) 333 666 7366
email:  
[hidden email]
web:    
www.adalyser.com

Adalyser is a registered trademark and trading name of OneSoon Limited
OneSoon is registered in England and Wales Company Number 04746025




--
Lea Thurman
OneSoon Limited
Manchester Business Park
3000 Aviator Way
Manchester M22 5TG

mob:   <a href="tel:+44+(0)+7545+828+526" value="+447973182802" style="color:rgb(17,85,204)" target="_blank">+44 (0) 7545 828 526
tel:      <a href="tel:%2B44%20%280%29%20333%20666%207366" value="+443336667366" style="color:rgb(17,85,204)" target="_blank">+44 (0) 333 666 7366
email:  
[hidden email]
web:    
www.adalyser.com

Adalyser is a registered trademark and trading name of OneSoon Limited
OneSoon is registered in England and Wales Company Number 04746025


Anil Anil
Reply | Threaded
Open this post in threaded view
|

Re: 2.0

In reply to this post by Denis Magda-2
Hi,

I tried to use latest ignite-aws (with vertx-ignite) and nodes are not joining the cluster.

     <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
       <property name="ipFinder">
        <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder">
           <property name="awsCredentials">
             <bean class="com.amazonaws.auth.BasicAWSCredentials">
               <constructor-arg value="XXXXXXXXXXXXX" />
               <constructor-arg value="XXXXXXXXXXXXXXXXXXXXX" />
             </bean>
           </property>
           <property name="bucketName" value="testing-ignite"/>
         </bean>
       </property>
     </bean>

logs :

2017-03-29 10:23:39 INFO  GridDiscoveryManager:475 - Topology snapshot [ver=1, servers=1, clients=0, CPUs=4, heap=3.5GB]
2017-03-29 10:23:39 INFO  GridCacheProcessor:475 - Started cache [name=__vertx.haInfo, mode=PARTITIONED]
2017-03-29 10:23:39 INFO  GridCachePartitionExchangeManager:475 - Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=1, minorTopVer=1], evt=DISCOVERY_CUSTOM_EVT, node=d97a7af4-8711-479b-b90e-e9f085d3dc6b]
2017-03-29 10:23:39 INFO  GridCacheProcessor:475 - Started cache [name=__vertx.subs, mode=PARTITIONED]
2017-03-29 10:23:39 WARN  GridEventStorageManager:480 - Added listener for disabled event type: CACHE_OBJECT_REMOVED
2017-03-29 10:23:39 INFO  GridCachePartitionExchangeManager:475 - Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=1, minorTopVer=2], evt=DISCOVERY_CUSTOM_EVT, node=d97a7af4-8711-479b-b90e-e9f085d3dc6b]
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


Any other configurations required ? Did I miss anything  ? Please advise.

Thanks

On 28 March 2017 at 22:49, Denis Magda <[hidden email]> wrote:
Lea, 

If you can’t wait for 2.0 release I would suggest you pick my commit, merge it to your fork of Ignite 1.9 release and build it from sources.

Does it work for you?

Denis

On Mar 28, 2017, at 1:21 AM, Lea Thurman <[hidden email]> wrote:

Thanks Pavel

Would it be worth us reverting to an earlier release. Any idea when it was introduced?

Regards
Lea Thurman.

On 28 March 2017 at 08:46, Pavel Tupitsyn <[hidden email]> wrote:
According to the dev list thread (http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-0-Release-td15690.html),
you can expect 2.0 by the end of the April.


On Tue, Mar 28, 2017 at 10:41 AM, Lea Thurman <[hidden email]> wrote:
Hi all,

We have upgraded to 1.9 and noticed the following issue:


I understand this is to be fixed in 2.0. 

Is there any indicated when this is planned to be released?

Regards
Lea Thurman

--
Lea Thurman
OneSoon Limited
Manchester Business Park
3000 Aviator Way
Manchester M22 5TG

mob:   <a href="tel:+44+(0)+7545+828+526" value="+447973182802" style="color:rgb(17,85,204)" target="_blank">+44 (0) 7545 828 526
tel:      <a href="tel:%2B44%20%280%29%20333%20666%207366" value="+443336667366" style="color:rgb(17,85,204)" target="_blank">+44 (0) 333 666 7366
email:  
[hidden email]
web:    
www.adalyser.com

Adalyser is a registered trademark and trading name of OneSoon Limited
OneSoon is registered in England and Wales Company Number 04746025




--
Lea Thurman
OneSoon Limited
Manchester Business Park
3000 Aviator Way
Manchester M22 5TG

mob:   <a href="tel:+44+(0)+7545+828+526" value="+447973182802" style="color:rgb(17,85,204)" target="_blank">+44 (0) 7545 828 526
tel:      <a href="tel:%2B44%20%280%29%20333%20666%207366" value="+443336667366" style="color:rgb(17,85,204)" target="_blank">+44 (0) 333 666 7366
email:  
[hidden email]
web:    
www.adalyser.com

Adalyser is a registered trademark and trading name of OneSoon Limited
OneSoon is registered in England and Wales Company Number 04746025


vkulichenko vkulichenko
Reply | Threaded
Open this post in threaded view
|

Re: 2.0

Hi Anil,

What is the MacAddressUtil class? I can't find it in any of Ignite dependencies, is it coming from your code? In any case, it looks like the node is started, so there are no issues with discovery.

-Val
Anil Anil
Reply | Threaded
Open this post in threaded view
|

Re: 2.0

Hi Val,

No. MacAddressUtil  is not from my application. netty-common jar which is from vertx-core. i am deploying ignite application as micro service using  vertx-ignite.

Thanks

On 29 March 2017 at 23:41, vkulichenko <[hidden email]> wrote:
Hi Anil,

What is the MacAddressUtil class? I can't find it in any of Ignite
dependencies, is it coming from your code? In any case, it looks like the
node is started, so there are no issues with discovery.

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/2-0-tp11487p11552.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

vkulichenko vkulichenko
Reply | Threaded
Open this post in threaded view
|

Re: 2.0

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
Anil Anil
Reply | Threaded
Open this post in threaded view
|

Re: 2.0

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 <[hidden email]> 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.70518.x6.nabble.com/2-0-tp11487p11580.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Denis Magda-2 Denis Magda-2
Reply | Threaded
Open this post in threaded view
|

Re: 2.0

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 <[hidden email]> 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 <[hidden email]> 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.70518.x6.nabble.com/2-0-tp11487p11580.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


vkulichenko vkulichenko
Reply | Threaded
Open this post in threaded view
|

Re: 2.0

In reply to this post by Anil
Yes, this warning is OK. It just indicates that default client configuration is used.

-Val
Anil Anil
Reply | Threaded
Open this post in threaded view
|

Re: 2.0

In reply to this post by Denis Magda-2
Thank you Denis and Val.

I will post the debug logs. thanks.

On 31 March 2017 at 22:02, Denis Magda <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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.70518.x6.nabble.com/2-0-tp11487p11580.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.



Anil Anil
Reply | Threaded
Open this post in threaded view
|

Re: 2.0

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 <[hidden email]> wrote:
Thank you Denis and Val.

I will post the debug logs. thanks.

On 31 March 2017 at 22:02, Denis Magda <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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.70518.x6.nabble.com/2-0-tp11487p11580.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.





logs-189.txt (20K) Download Attachment
logs-192.txt (18K) Download Attachment
debug.zip (315K) Download Attachment
TcpDiscoveryS3IpFinder.java (17K) Download Attachment
vkulichenko vkulichenko
Reply | Threaded
Open this post in threaded view
|

Re: 2.0

Anil,

I'm not sure I understand what is the issue in the first place. What is not working?

-Val
Anil Anil
Reply | Threaded
Open this post in threaded view
|

Re: 2.0

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 <[hidden email]> 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.

Anil Anil
Reply | Threaded
Open this post in threaded view
|

Re: 2.0

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 <[hidden email]> 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 <[hidden email]> 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.


Anil Anil
Reply | Threaded
Open this post in threaded view
|

Re: 2.0

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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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.



Nikolai Tikhonov-2 Nikolai Tikhonov-2
Reply | Threaded
Open this post in threaded view
|

Re: 2.0

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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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.




12