ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From soroka21 <sorok...@gmail.com>
Subject Re: using JDBC with Ignite cluster, configured with persistent storage
Date Thu, 07 Dec 2017 14:41:26 GMT
Here is what happened:
1) I've configured standalone cluster of 5 nodes with persistent storage
enabled in data storage part.
Following is the section of my configuration file:

<property name="dataStorageConfiguration"> 
  <bean class="org.apache.ignite.configuration.DataStorageConfiguration"> 
    <property name="dataRegionConfigurations"> 
      <list> 
        <bean
class="org.apache.ignite.configuration.DataRegionConfiguration">                      
      
             <property name="name" value="500MB_Region"/> 
             <property name="initialSize" value="#{100L * 1024 * 1024}"/> 
             <property name="maxSize" value="#{500L * 1024 * 1024}"/> 
             <property name="persistenceEnabled" value="true"/> 
        </bean> 
      </list> 
  </property> 
</bean> 
</property> 


2) I'd like to create Table using JDBC driver using following DDL statement
CREATE TABLE MY_TABLE
    (_id varchar,F00 varchar,F01 bigint,F02 double,F03 timestamp,F04
varchar,F05 bigint,
     F06 double,F07 timestamp,F08 varchar,F09 bigint, PRIMARY KEY(_id)) 
WITH "cache_name=MyCacheName, value_type=MyValueTpye";

I'm using SQLLine to run this statement. 
As a result of DDL execution I'm getting following exception:

Error: Failed to handle JDBC request because node is stopping.
(state=50000,code=0)
java.sql.SQLException: Failed to handle JDBC request because node is
stopping.
        at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:671)
        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)

What should be done to avoid this exception?

Alexey




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Mime
View raw message