You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/03/25 12:56:25 UTC

[jira] [Created] (IGNITE-2897) ODBC: Multiple grids cannot start with default configuration due to port conflict.

Vladimir Ozerov created IGNITE-2897:
---------------------------------------

             Summary: 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)