[
https://issues.apache.org/jira/browse/DRILL-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317633#comment-14317633
]
Parth Chandra commented on DRILL-1697:
--------------------------------------
I drillClientImpl
{code}
if(this->m_pQueryId!=NULL){
DRILL_LOG(LOG_TRACE) << "Clearing state for Query Id - " <<
debugPrintQid(*this->m_pQueryId) << std::endl;
}
{code}
fixes the crash the above example illustrates. However, it does illustrate the
problem that the listener might exit without getting all the results.
> C++ Client. Use the object io_service::work to prevent io_service running
> out of work.
> ---------------------------------------------------------------------------------------
>
> Key: DRILL-1697
> URL: https://issues.apache.org/jira/browse/DRILL-1697
> Project: Apache Drill
> Issue Type: Bug
> Reporter: Xiao Meng
> Assignee: Xiao Meng
> Fix For: 0.8.0
>
> Attachments: DRILL-1697-2.patch, DRILL-1697.1.patch,
> ThreeQueriesTraceOn.txt, ThreeQueriesTraceonWithSleep10Seconds5.txt,
> querySubmitterCrashes.GIF
>
>
> In C++ Client async API, the io_service may stop working because of there is
> a long enough time lag between two consecutive queries.
> References:
> http://www.boost.org/doc/libs/1_55_0/doc/html/boost_asio/reference/io_service.html#boost_asio.reference.io_service.stopping_the_io_service_from_running_out_of_work
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
