ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Igor Sapego (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-2897) ODBC: Multiple grids cannot start with default configuration due to port conflict.
Date Mon, 28 Mar 2016 13:39:25 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214197#comment-15214197
] 

Igor Sapego commented on IGNITE-2897:
-------------------------------------

I believe we should disable ODBC by default for now. Scanning of several ports would be not
just a fix for the issue but more like new feature.

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

Mime
View raw message