[GitHub] ignite pull request #785: [IGNITE-3221] Bad ip used , when fixed ip in hostn...

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request #785: [IGNITE-3221] Bad ip used , when fixed ip in hostn...

andrey-kuznetsov
GitHub user sebadiaz opened a pull request:

    https://github.com/apache/ignite/pull/785

    [IGNITE-3221] Bad ip used , when fixed ip in hostname

    The target is to set the ip written in a string format instead to call the DNS to resolve it.
   
    DNS could not be well working in some case and the IP is the more clear connection that we can make

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sebadiaz/ignite master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/785.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #785
   
----
commit 266a2dd9725eaa5251a6fce876745ee4080b3dfb
Author: Sebastien Diaz <[hidden email]>
Date:   2016-06-08T11:36:47Z

    IGNITE-3221 check IP and convert it

commit 26443bf41e4a8acb031054c5c295be22b6921102
Author: Sebastien Diaz <[hidden email]>
Date:   2016-06-08T11:37:50Z

    IGNITE-3221 check IP and convert it

commit f3bdc95f8a507d26e6b7ca598a609f77f9609fba
Author: Sebastien Diaz <[hidden email]>
Date:   2016-06-08T11:39:51Z

    IGNITE-3221 check IP and convert it

commit 0d1091e9ad7b8cee9f1078171a6e8362d8731f1f
Author: Sebastien Diaz <[hidden email]>
Date:   2016-06-08T11:42:49Z

    IGNITE-3221 check IP and convert it

commit 9f357d020e64b7374d47593bc35dc57d685f87f1
Author: Sebastien Diaz <[hidden email]>
Date:   2016-06-08T11:43:54Z

    IGNITE-3221 check IP and convert it

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---