Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] Maximum number of shards reached

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] Maximum number of shards reached


Chronological Thread 
    < Chronological >      < Thread >
  • From: Tristan Sullivan <>
  • To: "" <>
  • Subject: [perfsonar-user] Maximum number of shards reached
  • Date: Tue, 29 Aug 2023 16:56:37 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=uvic.ca; dmarc=pass action=none header.from=uvic.ca; dkim=pass header.d=uvic.ca; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=Zc8//S5nAucXsD3CpU6glXykowW9aXRDpVOSZEt+C3g=; b=HGOG+TAx35BJt2+G4Zofl575yQTYuP8Xt9EYHSZWB0ZXoGPB8SU5TBrS4XVTOulfRpfMQPaVYpVF/chUidJwvmWnvM9Uk652MUzT8EhrTJELFyE4qmO/SwxNGqCMYfKT9YeMtcGkRXJSN28iDwwEPnDDuUUkdj17Riu5L9fYWg93pdQqv4Ezcl95oSu/RuFwtJb6TWSCTf6WcXcvLBONv+RXv5ZPqoxCjJHVWcx+xPOXetDj3xDk5XMhnZqO003a7B4zE83kn/FWWwRIllUV03AnmgcBwbt4yObzdrR0LF0z7V2+kMtyOVMvOGUE8n64ca5JwtARAidZFz4KnAelTA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=nNrEYa0lafXW76UxIhdQSE+IfbweDDKKBRUa0xZRfeSqNeP4dbMT55C1aAOIl6BEhTFgFaPVS/8GuZztDtyuLzg9eIGLlAPm9M/YDFqa8W+DF6Ki/zk4rzgX5wDAVP6nZkKq+B5iOIatKJOrVnUeoIfsyhoJYKm+SOH0WedaK28JpGwDNxPotR6iadgRG07BxVyI93LsK3zSpygSXkkrvHmbvcl/NQL1UFPoSusI35MV/FrJjp3xtx02rHjaMSP345whGvwIeLHu6wl1bBvUeiqh/5i3kKwMTRMs1b2rKKD6d3evIOQji7+hmAC47lmkvKL2gcI5FwP8KNfTfTMo6A==
  • Msip_labels:
Hello,

I have three perfsonar boxes running the latest version of perfsonar on Centos 7. A few days ago, all the results disappeared from the web interfaces on all three boxes. On all of them, I found many entries in /var/log/logstash/logstash-plain.log containing this: "this action would add [2] total shards, but this cluster currently has [1000]/[1000] maximum shards open;"

I listed the shards in the DB, and indeed there were 1,000 of them. I increased the maximum number of shards to 2,000, and test results are appearing again, but I'm not sure that's really the best solution. In particular, I was wondering what the default is for deleting old data now; I found the cronjob that used to do it for esmond, but I couldn't find one for opensearch. I only have about four months of data, so it seems like other people should be having this problem too, unless they changed the default maximum number of shards.

Any insight is appreciated.

Thank you and regards,

Tristan

Archive powered by MHonArc 2.6.24.

Top of Page