You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrew Mashenkov (JIRA)" <ji...@apache.org> on 2016/09/05 13:21:20 UTC

[jira] [Commented] (IGNITE-2629) ODBC: Added GridNioAsyncNotifyFilter and GridConnectionBytesVerifyFilter to NIO server.

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

Andrew Mashenkov commented on IGNITE-2629:
------------------------------------------

Vladimir, 

ODBC tests looks fine on TC.

> ODBC: Added GridNioAsyncNotifyFilter and GridConnectionBytesVerifyFilter to NIO server.
> ---------------------------------------------------------------------------------------
>
>                 Key: IGNITE-2629
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2629
>             Project: Ignite
>          Issue Type: Task
>          Components: odbc
>    Affects Versions: 1.5.0.final
>            Reporter: Vladimir Ozerov
>            Assignee: Andrew Mashenkov
>             Fix For: 1.8
>
>
> This is low-priority task, lets return to it once everything else is finished.
> Justification:
> 1) *GridNioAsyncNotifyFilter* moves requests processing to separate thread pool. If you do no do that, all NIO workers might stuck in potentially long-running query operations and you will not be able to accept new client requests what may result in timeouts on client side.
> 2) *GridConnectionBytesVerifyFilter* expects special magic header to ensure connected client identity.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)