Hi There, I’Ve Run Into The Following Error When Trying To Enqueue A New Task:

Answered

Hi there, I’ve run into the following error when trying to enqueue a new task:

Error: Action failed <500/100: tasks.enqueue/v1.0 (General data error (TransportError(429, 'cluster_block_exception', 'index [queue_metrics_d1bd9abababa] blocked by: [TOO_MANY_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block];')))> (queue=b5b8485fababab, task=e5ccf7caabababababab, verify_watched_queue=False)

I realized I was just archiving things and not deleting them. I’ve gone and tried to delete things and one or two things have deleted successfully but most of the things I try to delete fail to delete. Any idea how I can recover from this??

  				
Posted 
	2 days ago

					More
				  		
  Report
		
					FantasticGorilla16
				
					0
					 × 1

Votes Newest

Answers 3

Yes im working with my admin to figure this out. But assuming that’s the case, what can I do to recover if eg I can’t allocate more disk space? Can I manually delete items somehow?

  				
Posted 
	one day ago

					More
				  		
  Report
		
					FantasticGorilla16
				
					0
					 × 1

Hi @<1745616566117994496:profile|FantasticGorilla16> , it looks like this error coming from the Elastic, can you check the disk space you allocated and check if its full?

  				
Posted 
	one day ago

					More
				  		
  Report
		
					RoundElephant20
				
					0

Hi @<1745616566117994496:profile|FantasticGorilla16> , you can always increase disk space on the machine running the server. Another option is to manually delete indices in Elastic, although it would be highly unadvised.

You could also probably clear up space in the file server if it has been heavily used.

  				
Posted 
	one day ago

					More
				  		
  Report
		
					CostlyOstrich36
				
					0

Write your answer

10 Views

3 Answers

2 days ago

10 hours ago