[druid-user] Master are taking time to comeup

Hi All,

i noticed that when we restart the master nodes i’m getting the below error messages

can any one pls guide me what i need to do

Caused by: org.skife.jdbi.v2.exceptions.UnableToExecuteStatementException: java.sql.BatchUpdateException: Batch entry 0 CREATE TABLE druid_segments (
id VARCHAR(255) NOT NULL,
dataSource VARCHAR(255) NOT NULL,
created_date VARCHAR(255) NOT NULL,
start VARCHAR(255) NOT NULL,
“end” VARCHAR(255) NOT NULL,
partitioned BOOLEAN NOT NULL,
version VARCHAR(255) NOT NULL,
used BOOLEAN NOT NULL,
payload BYTEA NOT NULL,
PRIMARY KEY (id)
) was aborted: ERROR: relation “druid_segments” already exists Call getNextException to see other errors in the batch. [statement:“null”, located:“null”, rewritten:“null”, arguments:null]
at org.skife.jdbi.v2.Batch.execute(Batch.java:131) ~[jdbi-2.63.1.jar:2.63.1]
at org.apache.druid.metadata.SQLMetadataConnector$2.withHandle(SQLMetadataConnector.java:201) ~[druid-server-0.20.1.jar:0.20.1]
at org.apache.druid.metadata.SQLMetadataConnector$2.withHandle(SQLMetadataConnector.java:191) ~[druid-server-0.20.1.jar:0.20.1]
at org.skife.jdbi.v2.DBI.withHandle(DBI.java:281) ~[jdbi-2.63.1.jar:2.63.1]
… 20 more
Caused by: java.sql.BatchUpdateException: Batch entry 0 CREATE TABLE druid_segments (
id VARCHAR(255) NOT NULL,
dataSource VARCHAR(255) NOT NULL,
created_date VARCHAR(255) NOT NULL,
start VARCHAR(255) NOT NULL,
“end” VARCHAR(255) NOT NULL,
partitioned BOOLEAN NOT NULL,
version VARCHAR(255) NOT NULL,
used BOOLEAN NOT NULL,
payload BYTEA NOT NULL,
PRIMARY KEY (id)
) was aborted: ERROR: relation “druid_segments” already exists Call getNextException to see other errors in the batch.
at org.postgresql.jdbc.BatchResultHandler.handleCompletion(BatchResultHandler.java:189) ~[?:?]
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:521) ~[?:?]
at org.postgresql.jdbc.PgStatement.internalExecuteBatch(PgStatement.java:851) ~[?:?]
at org.postgresql.jdbc.PgStatement.executeBatch(PgStatement.java:874) ~[?:?]
at org.apache.commons.dbcp2.DelegatingStatement.executeBatch(DelegatingStatement.java:345) ~[commons-dbcp2-2.0.1.jar:2.0.1]
at org.apache.commons.dbcp2.DelegatingStatement.executeBatch(DelegatingStatement.java:345) ~[commons-dbcp2-2.0.1.jar:2.0.1]
at org.skife.jdbi.v2.Batch.execute(Batch.java:121) ~[jdbi-2.63.1.jar:2.63.1]
at org.apache.druid.metadata.SQLMetadataConnector$2.withHandle(SQLMetadataConnector.java:201) ~[druid-server-0.20.1.jar:0.20.1]
at org.apache.druid.metadata.SQLMetadataConnector$2.withHandle(SQLMetadataConnector.java:191) ~[druid-server-0.20.1.jar:0.20.1]
at org.skife.jdbi.v2.DBI.withHandle(DBI.java:281) ~[jdbi-2.63.1.jar:2.63.1]
… 20 more
Caused by: org.postgresql.util.PSQLException: ERROR: relation “druid_segments” already exists
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2532) ~[?:?]
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2267) ~[?:?]
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:510) ~[?:?]
at org.postgresql.jdbc.PgStatement.internalExecuteBatch(PgStatement.java:851) ~[?:?]
at org.postgresql.jdbc.PgStatement.executeBatch(PgStatement.java:874) ~[?:?]
at org.apache.commons.dbcp2.DelegatingStatement.executeBatch(DelegatingStatement.java:345) ~[commons-dbcp2-2.0.1.jar:2.0.1]
at org.apache.commons.dbcp2.DelegatingStatement.executeBatch(DelegatingStatement.java:345) ~[commons-dbcp2-2.0.1.jar:2.0.1]
at org.skife.jdbi.v2.Batch.execute(Batch.java:121) ~[jdbi-2.63.1.jar:2.63.1]
at org.apache.druid.metadata.SQLMetadataConnector$2.withHandle(SQLMetadataConnector.java:201) ~[druid-server-0.20.1.jar:0.20.1]
at org.apache.druid.metadata.SQLMetadataConnector$2.withHandle(SQLMetadataConnector.java:191) ~[druid-server-0.20.1.jar:0.20.1]
at org.skife.jdbi.v2.DBI.withHandle(DBI.java:281) ~[jdbi-2.63.1.jar:2.63.1]
… 20 more
2021-12-22T09:04:19,272 INFO [DatabaseRuleManager-Exec–0] org.apache.druid.metadata.SQLMetadataRuleManager - Polled and found 1 rule(s) for 1 datasource(s)