You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/08/26 11:14:20 UTC
[jira] [Commented] (IGNITE-2974) ODBC: Implement fine-grained NIO
server configuration.
[ https://issues.apache.org/jira/browse/IGNITE-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438807#comment-15438807 ]
Vladimir Ozerov commented on IGNITE-2974:
-----------------------------------------
Looks like there is no need to bother with common config. Let's just simply expose fine-grained parameters directly to {{OdbcConfiguration}}.
Configuration params to expose:
{{socketSendBufferSize}}
{{socketSendReceiveSize}}
{{idleTimeout}}
> ODBC: Implement fine-grained NIO server configuration.
> ------------------------------------------------------
>
> Key: IGNITE-2974
> URL: https://issues.apache.org/jira/browse/IGNITE-2974
> Project: Ignite
> Issue Type: Task
> Components: general, odbc
> Affects Versions: 1.5.0.final
> Reporter: Vladimir Ozerov
> Labels: roadmap
>
> ODBC uses {{GridNioServer}} internally to handle user requests. This server has a number of properties, e.g. selector count buffer size, etc.
> We can expose these properties in {{OdbcConfiguration}}, but it appears to be too complex for users. Moreover, this is not the only component where we need NIO server configuration.
> I propose to create separate bean and name it {{ServerConfiguration}}. This bean will be used in ODBC and any other component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)