[
https://issues.apache.org/jira/browse/IGNITE-12146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16930659#comment-16930659
]
Igor Sapego commented on IGNITE-12146:
--------------------------------------
[~livelace], are you sure that this is a rootcause of your issue? You can
easily check it by simply changing DEFALT_IO_TIMEOUT constant to something
bigger like 20, rebuilding Ignite and check, if the issue persists. Just to be
sure that we are fixing a right issue.
> Make timeout of network operations customizable
> -----------------------------------------------
>
> Key: IGNITE-12146
> URL: https://issues.apache.org/jira/browse/IGNITE-12146
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
> Affects Versions: 2.7.5
> Reporter: Oleg Popov
> Priority: Major
> Labels: cpp
>
> I'm performing a data migration from MariaDB to Apache Ignite and I do bulk
> insertions with help of a "converter". All works fine except of appearing of
> a message at the end of operations:
> *Can not send message to remote host: timeout*
> but all data succefully placed into Ignite cluster.
> Short investigation showed that default values of network operations are too
> low in my case (do data migration, remember?). Default values:
> [https://github.com/apache/ignite/blob/ignite-2.7.5/modules/platforms/cpp/thin-client/src/impl/data_router.h#L61]
>
> It would be much better to have an option to customize these values through
> "IgniteClientConfiguration" (the python client has such option?).
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
