tephra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Poorna Chandra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TEPHRA-153) Status for transaction manager reports as running through CLI when down
Date Thu, 01 Sep 2016 21:59:21 GMT

    [ https://issues.apache.org/jira/browse/TEPHRA-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15456748#comment-15456748

Poorna Chandra commented on TEPHRA-153:

[~jamestaylor] [~mujtabachohan] We do the exact same check in transaction manager and from
the thrift client for checking the status. The only think I can think of is that the transaction
manager failed after the last status check was done. 

Did you make another status check after the client reported failure while running the query?
Did that check also report the status as running?

> Status for transaction manager reports as running through CLI when down
> -----------------------------------------------------------------------
>                 Key: TEPHRA-153
>                 URL: https://issues.apache.org/jira/browse/TEPHRA-153
>             Project: Tephra
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: Poorna Chandra
>              Labels: phoenix
> Using the {{tephra status}} command reports the service as running even when its not
as evident from logs:
> {code}
> ERROR [nsactionServer-rpc-2] thrift.ProcessFunction - Internal error processing startShort
> java.lang.IllegalStateException: Transaction Manager is not running.
> 	at com.google.common.base.Preconditions.checkState(Preconditions.java:149)
> 	at co.cask.tephra.TransactionManager.ensureAvailable(TransactionManager.java:707)
> 	at co.cask.tephra.TransactionManager.startTx(TransactionManager.java:766)
> {code}

This message was sent by Atlassian JIRA

View raw message