[ISSUE] (TEPHRA-153) Status for transaction manager reports as running through CLI when down

[James Taylor (JIRA)]

James Taylor created an issue

Tephra / TEPHRA-153 Status for transaction manager reports as running through CLI when down Issue Type: Bug Assignee: Poorna Chandra Created: 10/Dec/15 5:35 PM Priority: Major Reporter: James Taylor Using the tephra status command reports the service as running even when its not as evident from logs: 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) Add Comment

This message was sent by Atlassian JIRA (v6.1.5#6160-sha1:a61a0fc)

[James Taylor (JIRA)]

James Taylor updated an issue

Tephra / TEPHRA-153 Status for transaction manager reports as running through CLI when down

Change By: James Taylor Labels: phoenix

Add Comment

[James Taylor (JIRA)]

James Taylor commented on an issue

Re: Status for transaction manager reports as running through CLI when down More info here: https://issues.apache.org/jira/browse/PHOENIX-2504 TLDR; We need a reliable way of knowing that the transaction manager is up. Is there some workaround today? Starting a tx is probably not ideal as it increases the number of inflight transactions, but maybe that's the best we can do for now? I suppose if we only ping 1/min or 1/5mins it wouldn't matter.

Add Comment

Tephra / TEPHRA-153 Status for transaction manager reports as running through CLI when down

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)

...

[Poorna Chandra (JIRA)]

Poorna Chandra commented on an issue

Re: Status for transaction manager reports as running through CLI when down

James Taylor I'm assuming you are talking about the status method on TransactionSystemClient. Is there a CLI interface from where you can make this call? status method on TransactionSystemClient checks whether transaction manager's state is "running" using the thrift interface. So, it basically does the same state check that is failing in the stack trace above. Is this status check happening every now and then? If so, is it possible that transaction manager failed after the last status check?

Add Comment

[James Taylor (JIRA)]

James Taylor commented on an issue

Re: Status for transaction manager reports as running through CLI when down

Yes (details are in the Phoenix JIRA), but we're using tephra status as our CLI to monitor that the transaction manager.

Add Comment

[James Taylor (JIRA)]