[
https://issues.apache.org/jira/browse/HBASE-18086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090802#comment-16090802
]
Ted Yu commented on HBASE-18086:
--------------------------------
When using load-client against an hbase 1.1 cluster, sometimes I got:
{code}
2017-07-17 23:38:42,333:9228(0x7fd65a5ea700):ZOO_INFO@check_events@1728:
initiated connection to server [172.26.109.227:2181]
2017-07-17 23:38:42,351:9228(0x7fd65a5ea700):ZOO_INFO@check_events@1775:
session establishment complete on server [172.26.109.227:2181],
sessionId=0x15d3dfaa94a07d1, negotiated timeout=40000
load-client: io/async/AsyncSocket.cpp:837: virtual void
folly::AsyncSocket::closeNow(): Assertion `eventBase_ == nullptr ||
eventBase_->isInEventBaseThread()' failed.
*** Aborted at 1500334722 (unix time) try "date -d @1500334722" if you are
using GNU date ***
PC: @ 0x7fd66bd68418 gsignal
*** SIGABRT (@0x240c) received by PID 9228 (TID 0x7fd6689a9700) from PID 9228;
stack trace: ***
@ 0x7fd66ce933d0 (unknown)
@ 0x7fd66bd68418 gsignal
@ 0x7fd66bd6a01a abort
@ 0x7fd66bd60bd7 (unknown)
@ 0x7fd66bd60c82 __assert_fail
@ 0x60d9e4 folly::AsyncSocket::closeNow()
@ 0x60abf5 folly::AsyncSocket::destroy()
@ 0x50f6a2 std::_Sp_counted_deleter<>::_M_dispose()
@ 0x517c91 wangle::AsyncSocketHandler::~AsyncSocketHandler()
@ 0x51f090 wangle::ContextImpl<>::~ContextImpl()
@ 0x51e505 wangle::PipelineBase::~PipelineBase()
@ 0x51e001 wangle::Pipeline<>::~Pipeline()
@ 0x50ec1e wangle::ClientBootstrap<>::~ClientBootstrap()
@ 0x5072be hbase::ConnectionPool::GetNewConnection()
@ 0x50628c hbase::ConnectionPool::GetConnection()
@ 0x50c0b7 hbase::RpcClient::GetConnection()
@ 0x50c25e hbase::RpcClient::AsyncCall()
@ 0x47e23e hbase::RawAsyncTable::Call<>()
@ 0x46bf0b std::_Function_handler<>::_M_invoke()
@ 0x4ceddc hbase::AsyncSingleRequestRpcRetryingCaller<>::Call()
@ 0x4dfc60
_ZZZN5folly6FutureISt10shared_ptrIN5hbase14RegionLocationEEE18thenImplementationIZNS2_35AsyncSingleRequestRpcRetryingCallerINS_4UnitEE14LocateThenCallEvEUlS4_E_NS_6detail14callableResultIS4_SA_EELb0EJOS4_EEENSt9enable_ifIXntsrNT0_13ReturnsFutureE5valueENSG_6ReturnEE4typeEOT_NSB_9argResultIXT1_ESK_JDpT2_EEEENUlONS_3TryIS4_EEE_clESS_ENKUlvE_clEv
@ 0x4dfa2f
_ZN5folly11makeTryWithIZZNS_6FutureISt10shared_ptrIN5hbase14RegionLocationEEE18thenImplementationIZNS3_35AsyncSingleRequestRpcRetryingCallerINS_4UnitEE14LocateThenCallEvEUlS5_E_NS_6detail14callableResultIS5_SB_EELb0EJOS5_EEENSt9enable_ifIXntsrNT0_13ReturnsFutureE5valueENSH_6ReturnEE4typeEOT_NSC_9argResultIXT1_ESL_JDpT2_EEEENUlONS_3TryIS5_EEE_clEST_EUlvE_EENSG_IXsr3std7is_sameINSt9result_ofIFSL_vEE4typeEvEE5valueENSR_IvEEE4typeESM_
@ 0x4df906
_ZN5folly7PromiseINS_4UnitEE7setWithIZZNS_6FutureISt10shared_ptrIN5hbase14RegionLocationEEE18thenImplementationIZNS6_35AsyncSingleRequestRpcRetryingCallerIS1_E14LocateThenCallEvEUlS8_E_NS_6detail14callableResultIS8_SD_EELb0EJOS8_EEENSt9enable_ifIXntsrNT0_13ReturnsFutureE5valueENSJ_6ReturnEE4typeEOT_NSE_9argResultIXT1_ESN_JDpT2_EEEENUlONS_3TryIS8_EEE_clESV_EUlvE_EEvSO_
@ 0x4df67d
_ZN5folly6detail8function18FunctionTypeTraitsIFvONS_3TryISt10shared_ptrIN5hbase14RegionLocationEEEEEE13ExecutorMixin13invokeFunctorINS1_9ExecutorsISA_E15FunctorExecutorIZNS_6FutureIS7_E18thenImplementationIZNS5_35AsyncSingleRequestRpcRetryingCallerINS_4UnitEE14LocateThenCallEvEUlS7_E_NS0_14callableResultIS7_SN_EELb0EJOS7_EEENSt9enable_ifIXntsrNT0_13ReturnsFutureE5valueENSS_6ReturnEE4typeEOT_NS0_9argResultIXT1_ESW_JDpT2_EEEEUlS9_E_NS1_25SelectNonConstFunctionTagEEEEEvPNSF_10ExecutorIfES9_
@ 0x434e8c folly::detail::Core<>::doCallback()
@ 0x45c325 folly::detail::Core<>::setResult()
@ 0x451c0b
_ZN5folly6detail8function6invokeIRZNS_6FutureISt10shared_ptrIN5hbase14RegionLocationEEE18thenImplementationIZNS5_13LocationCache14LocateFromMetaERKNS5_2pb9TableNameERKSsE3$_7NS0_14callableResultIS7_SH_EELb0EJOS7_EEENSt9enable_ifIXntsrNT0_13ReturnsFutureE5valueENSM_6ReturnEE4typeEOT_NS0_9argResultIXT1_ESQ_JDpT2_EEEEUlONS_3TryIS7_EEE_JSX_EEEDTclclsr3stdE7forwardISQ_Efp_Espclsr3stdE7forwardIT0_Efp0_EEESR_DpOS11_
@ 0x434e8c folly::detail::Core<>::doCallback()
@ 0x45c325 folly::detail::Core<>::setResult()
@ 0x4509ea
_ZN5folly6detail8function6invokeIRZNS_6FutureISt10shared_ptrIN5hbase14RegionLocationEEE18thenImplementationIZNS5_13LocationCache14LocateFromMetaERKNS5_2pb9TableNameERKSsE3$_6NS0_14callableResultIS7_SH_EELb0EJOS7_EEENSt9enable_ifIXntsrNT0_13ReturnsFutureE5valueENSM_6ReturnEE4typeEOT_NS0_9argResultIXT1_ESQ_JDpT2_EEEEUlONS_3TryIS7_EEE_JSX_EEEDTclclsr3stdE7forwardISQ_Efp_Espclsr3stdE7forwardIT0_Efp0_EEESR_DpOS11_
@ 0x434e8c folly::detail::Core<>::doCallback()
@ 0x45c325 folly::detail::Core<>::setResult()
{code}
> Create native client which creates load on selected cluster
> -----------------------------------------------------------
>
> Key: HBASE-18086
> URL: https://issues.apache.org/jira/browse/HBASE-18086
> Project: HBase
> Issue Type: Sub-task
> Reporter: Ted Yu
> Assignee: Ted Yu
> Attachments: 18086.v11.txt, 18086.v12.txt, 18086.v14.txt,
> 18086.v1.txt, 18086.v3.txt, 18086.v4.txt, 18086.v5.txt, 18086.v6.txt,
> 18086.v7.txt, 18086.v8.txt
>
>
> This task is to create a client which uses multiple threads to conduct Puts
> followed by Gets against selected cluster.
> Default is to run the tool against local cluster.
> This would give us some idea on the characteristics of native client in terms
> of handling high load.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
