[
https://issues.apache.org/jira/browse/IGNITE-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214251#comment-15214251
]
ASF GitHub Bot commented on IGNITE-2897:
----------------------------------------
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/583
IGNITE-2897: ODBC is now disabled by default.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/isapego/ignite ignite-2897
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/583.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 #583
----
commit 546eeca158bb128641a1a602e8b081501d4b3286
Author: isapego <[email protected]>
Date: 2016-03-28T14:27:14Z
IGNITE-2897: ODBC is now disabled by default.
----
> ODBC: Multiple grids cannot start with default configuration due to port
> conflict.
> ----------------------------------------------------------------------------------
>
> Key: IGNITE-2897
> URL: https://issues.apache.org/jira/browse/IGNITE-2897
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
> Affects Versions: 1.5.0.final
> Reporter: Vladimir Ozerov
> Assignee: Igor Sapego
> Fix For: 1.6
>
>
> *Problem*
> Currently each node has ODBC enabled by default. ODBC processor has a single
> default port and each node tries to occupy it. As a result, second node
> cannot start due to port conflict.
> *Possible solutions*
> 1) Do not start ODBC processor by default.
> Cons: will require explicit config for ODBC users.
> 2) Scan several ports until free port is found.
> Cons: will require changes on client side.
> Anything else?
> I think that for now could go with the most easy and straightforward solution
> - do not start ODBC processor by default. This way we merge ODBC faster. In
> future releases we could easily make it start by default with normal port
> scan. It should not affect compatibility anyhow.
> Thoughts?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
