Thanks Kalyan, will do that.
-Rams
> On 1 Apr 2019, at 5:46 pm, Kalyan Kumar Kalvagadda
> <kkal...@cloudera.com.invalid> wrote:
>
> Ram,
>
> You would see this issue when NN is not able to connect to the sentry
> server. It could be network issue OR sentry service not being up on the
> address provided may be something else.
> You could run a network capture using "tcpdump" filtering the data for
> given host and port and see what's happening to the connection request sent
> from NN.
>
>> On Sat, Mar 30, 2019 at 3:45 AM Ram <bigcher...@gmail.com> wrote:
>>
>> Hi Champs,
>>
>> My active NN log keeps throwing "Failed to obtain Transport for
>> fakehostname:8038:null".
>> The exception is triggered from SentryTransportPool
>>
>> try {
>> TTransportWrapper transport =
>> isPoolEnabled ?
>> pool.borrowObject(addr) :
>> transportFactory.getTransport(addr);
>> LOGGER.debug("[{}] obtained transport {}", id, transport);
>> if (LOGGER.isDebugEnabled() && isPoolEnabled) {
>> LOGGER.debug("Currently {} active connections, {} idle connections",
>> pool.getNumActive(), pool.getNumIdle());
>> }
>> return transport;
>> } catch (IllegalStateException e) {
>> // Should not happen
>> LOGGER.error("Unexpected error from pool {}", id, e);
>> failure = e;
>> } catch (Exception e) {
>> LOGGER.error("Failed to obtain transport for {}: {}",
>> addr, e.getMessage());
>> failure = e;
>>
>>
>> I'm trying to understand the bottom of the issue. On what scenario we get
>> this exception, may be NN couldn't get any connection to Sentry server from
>> the pool, due to network issue? Or the number of threads exhausted? Should
>> increasing sentry.service.server-max-threads help? or is it completely
>> different?
>>
>> Pls advice
>>
>> -Rams
>>
