SHOW INDEXES does not work after creating new indexes

Issue: After creating new indexes in graph, SHOW INDEXES query has stopped returning output, It runs indefinitely

  • neo4j version: 4.2.1

Description:
There are two ways to check for existing indexes in a Graph:
1- SHOW INDEXES - not returning any result
2- CALL db.indexes() - runs within milli second and lists all the indexes as seen in Screenshot:

  • Created these new Indexes:

/** ==================================================================================== */
/*
PRIMARY KEY CONSTRAINT ON ASSESSMENT RESULT
*/
CREATE CONSTRAINT result_nk IF NOT EXISTS ON (result:`Assessment Result`)
ASSERT(
result.communityId,
result.appId,
result.nativeType
) IS NODE KEY;

/* Not null (Existence) constraint : Assessment Result  */
CREATE CONSTRAINT result_application_identifier_req IF NOT EXISTS ON (result:`Assessment Result`)
ASSERT exists(result.`Application Identifier`);

CREATE CONSTRAINT result_control_id_req IF NOT EXISTS ON (result:`Assessment Result`)
ASSERT exists(result.`Control Id`);

CREATE CONSTRAINT result_purpose_req IF NOT EXISTS ON (result:`Assessment Result`)
ASSERT exists(result.`Task Purpose`);

/* Index for Search APIs -default b-tree index  */
CREATE INDEX result_idx IF NOT EXISTS FOR (n:`Assessment Result`)
ON (
n.communityId,
n.appId,
n.nativeType,
n.`Task Purpose`,
n.`Application Identifier`,
n.`Control Id`);
  • attached logs:

2025-06-10 07:13:12.500+0000 INFO  Query started: id:2063680 - 0 ms: 0 B - bolt-session	bolt	neo4j-browser/v4.2.0		client/x.x.x.x:60979	server/x.x.x.x:7687>	<none> - neo4j - CALL dbms.routing.getRoutingTable($context, $database) - {context: {address: 'x.x.x.x:7687'}, database: 'cfx-graph-dev-docker'} - runtime=null - {}
2025-06-10 07:13:12.502+0000 INFO  id:2063680 - 1 ms: -1 B - bolt-session	bolt	neo4j-browser/v4.2.0		client/x.x.x.x:60979	server/x.x.x.x:7687>	system - neo4j - CALL dbms.routing.getRoutingTable($context, $database) - {context: {address: 'x.x.x.x:7687'}, database: 'cfx-graph-dev-docker'} - runtime=system - {}
2025-06-10 07:13:12.605+0000 INFO  Query started: id:2063681 - 0 ms: 0 B - bolt-session	bolt	neo4j-browser/v4.2.0		client/x.x.x.x:60979	server/x.x.x.x:7687>	<none> - neo4j - SHOW INDEXES - {} - runtime=null - {type: 'user-direct', app: 'neo4j-browser_v4.2.0'}
2025-06-10 07:13:12.606+0000 ERROR id:2063681 - 1 ms: -1 B - bolt-session	bolt	neo4j-browser/v4.2.0		client/x.x.x.x:60979	server/x.x.x.x:7687>	cfx-graph-dev-docker - neo4j - SHOW INDEXES - {} - runtime=schema - {type: 'user-direct', app: 'neo4j-browser_v4.2.0'} - Queue full

Q1 - What is Queue full as seen in logs?
Q2- How can I debug further?

@david_allen / @michael.hunger Can you help ?

@poemdaga

@david_allen is no longer working directly with Neo4j.

You state you are using Neo4j 4.2.1. If so, it should be noted per Neo4j 4.2.1 - Graph Database & Analytics and this was released 26 November 2020. Some 4.5+ yrs ago. Any chance to upgrade?