[MDEV-13565] In Galera HA mode, if one database is down unable to create table using 2nd db. Created: 2017-08-17  Updated: 2021-01-18  Resolved: 2017-09-15

Status: Closed
Project: MariaDB Server
Component/s: Galera SST
Affects Version/s: None
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Omkar Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: need_feedback


 Description   

I am using Galera cluster with mariadb to have HA. But if one database is down and I issue create table from hive, I get following error : 

Could not create "increment"/"table" value-generation container `SEQUENCE_TABLE` since autoCreate flags do not allow it.
 
org.datanucleus.exceptions.NucleusUserException: Could not create "increment"/"table" value-generation container `SEQUENCE_TABLE` since autoCreate flags do not allow it.
 
        at org.datanucleus.store.rdbms.valuegenerator.TableGenerator.createRepository(TableGenerator.java:261)
 
        at org.datanucleus.store.rdbms.valuegenerator.AbstractRDBMSGenerator.obtainGenerationBlock(AbstractRDBMSGenerator.java:162)
 
        at org.datanucleus.store.valuegenerator.AbstractGenerator.obtainGenerationBlock(AbstractGenerator.java:197)
 
        at org.datanucleus.store.valuegenerator.AbstractGenerator.next(AbstractGenerator.java:105)
 
        at org.datanucleus.store.rdbms.RDBMSStoreManager.getStrategyValueForGenerator(RDBMSStoreManager.java:2005)
 
        at org.datanucleus.store.AbstractStoreManager.getStrategyValue(AbstractStoreManager.java:1386)
 
        at org.datanucleus.ExecutionContextImpl.newObjectId(ExecutionContextImpl.java:3827)
 
        at org.datanucleus.state.JDOStateManager.setIdentity(JDOStateManager.java:2571)
 
        at org.datanucleus.state.JDOStateManager.initialiseForPersistentNew(JDOStateManager.java:513)
 
        at org.datanucleus.state.ObjectProviderFactoryImpl.newForPersistentNew(ObjectProviderFactoryImpl.java:232)
 
        at org.datanucleus.ExecutionContextImpl.newObjectProviderForPersistentNew(ExecutionContextImpl.java:1414)
 
        at org.datanucleus.ExecutionContextImpl.persistObjectInternal(ExecutionContextImpl.java:2218)
 
        at org.datanucleus.ExecutionContextImpl.persistObjectWork(ExecutionContextImpl.java:2065)
 
        at org.datanucleus.ExecutionContextImpl.persistObject(ExecutionContextImpl.java:1913)
 
        at org.datanucleus.ExecutionContextThreadedImpl.persistObject(ExecutionContextThreadedImpl.java:217)
 
        at org.datanucleus.api.jdo.JDOPersistenceManager.jdoMakePersistent(JDOPersistenceManager.java:727)
 
        at org.datanucleus.api.jdo.JDOPersistenceManager.makePersistent(JDOPersistenceManager.java:752)
 
        at org.apache.hadoop.hive.metastore.ObjectStore.createTable(ObjectStore.java:820)
 
        at sun.reflect.GeneratedMethodAccessor56.invoke(Unknown Source)



 Comments   
Comment by Elena Stepanova [ 2017-08-17 ]

This doesn't give us anything, as it doesn't come either from the server or from connector/j. Please look for error messages (a prt of the stack trace) issued by JDBC, they might contain the real error. Here is the first example that I found online:
https://community.hortonworks.com/content/supportkb/49581/hive-ddl-queries-fail-with-error-could-not-create.html

The root cause for you will be different, but the second stack shows how the useful messages look like.

Generated at Thu Feb 08 08:06:35 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.