You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Alice Chen (JIRA)" <ji...@apache.org> on 2015/07/22 20:14:31 UTC

[jira] [Created] (TRAFODION-178) LP Bug: 1274932 - Getting Trafodian internal error from mxosrvr due to Zookeeper

Alice Chen created TRAFODION-178:
------------------------------------

             Summary: LP Bug: 1274932 - Getting Trafodian internal error from mxosrvr due to Zookeeper
                 Key: TRAFODION-178
                 URL: https://issues.apache.org/jira/browse/TRAFODION-178
             Project: Apache Trafodion
          Issue Type: Bug
          Components: connectivity-dcs
            Reporter: Guy Groulx
            Assignee: Tharak Capirala
             Fix For: 0.6 (pre-incubation)


Running atomic suite.
As part of a purgedata command on  a table (not implemented in Trafodion), I created a JRUBY script which does a truncate on the table and recreates it with the same partition layout as before. 

However, I have found that if I try to connect to trafodion immediately after running this script, the mxosrvr returns an internal error.

Trafodian Internal error: Zookeeper entry not in connecting state for 21016. Current state is AVAILABLE
Trafodian Internal error: Zookeeper entry not in connecting state for 21016. Current state is AVAILABLE
com.hp.jdbc.HPT4Exception: Trafodian Internal error: Zookeeper entry not in connecting state for 21016. Current state is AVAILABLE
	at com.hp.jdbc.HPT4Messages.throwSQLException(HPT4Messages.java:172)
	at com.hp.jdbc.InterfaceConnection.initDiag(InterfaceConnection.java:587)
	at com.hp.jdbc.InterfaceConnection.secureLogin(InterfaceConnection.java:706)
	at com.hp.jdbc.InterfaceConnection.connect(InterfaceConnection.java:900)
	at com.hp.jdbc.InterfaceConnection.<init>(InterfaceConnection.java:172)
	at com.hp.jdbc.HPT4Connection.makeConnection(HPT4Connection.java:1609)
	at com.hp.jdbc.HPT4Connection.<init>(HPT4Connection.java:1562)
	at com.hp.jdbc.HPT4DataSource.getConnection(HPT4DataSource.java:128)
	at com.hp.jdbc.HPT4DataSource.getConnection(HPT4DataSource.java:172)
	at com.hp.jdbc.HPT4Driver.connect(HPT4Driver.java:182)
	at java.sql.DriverManager.getConnection(DriverManager.java:579)
	at java.sql.DriverManager.getConnection(DriverManager.java:221)
	at Measrtn.MeasrtnInit(Measrtn.java:100)
	at JDBCAtomics.main(JDBCAtomics.java:2630)

WORKAROUND:   I've added a sleep 5 seconds after running the utility.   Seems that Zookeeper is then available.

Suggest that this error be retried at least once in our code.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)