Hello!
I have just checked your configuration and the latest code base (Apache
Ignite master) and it works as expected.
In case of an inactive cluster, sqlline should report something like as
follows:
class org.apache.ignite.IgniteException: Can not perform the operation
because the cluster is inactive.
Note, that the cluster is considered inactive by default if Ignite
Persistent Store is used to let all the nodes join the cluster. To activate
the cluster call Ignite.active(true). (state=50000,code=0)
java.sql.SQLException: class org.apache.ignite.IgniteException: Can not
perform the operation because the cluster is inactive. Note, that the
cluster is considered inactive by default if Ignite Persistent Store is used
to let all the node
s join the cluster. To activate the cluster call Ignite.active(true).
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:648)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:130)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:299)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
So, it seems to me, that your issue does not relate to
activation/deactivation of the cluster.
Could you please reproduce the problem and provide us with the log files
from all participated nodes, especially from the node which is used by the
JDBC thin driver?
Thanks!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
