tephra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (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 22:31:20 GMT

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

James Taylor commented on TEPHRA-153:
-------------------------------------

What does running {{tephra status}} do, [~poornachandra]? Does it interact with the transaction
manager in the same way that a transactional client would? For example, does it open a new
transaction?

> 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
(v6.3.4#6332)

Mime
View raw message