From owner-freebsd-current@freebsd.org Tue Jan 9 00:02:31 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D5DCCE6CF1C; Tue, 9 Jan 2018 00:02:31 +0000 (UTC) (envelope-from mikej@mikej.com) Received: from mx2.paymentallianceintl.com (mx2.paymentallianceintl.com [216.26.158.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx2.paymentallianceintl.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9CAA57C30D; Tue, 9 Jan 2018 00:02:31 +0000 (UTC) (envelope-from mikej@mikej.com) Received: from firewall.mikej.com (f [162.230.214.65]) by mx2.paymentallianceintl.com (8.15.2/8.15.2) with ESMTPS id w08NfLDi035577 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 8 Jan 2018 18:41:22 -0500 (EST) (envelope-from mikej@mikej.com) X-SenderID: Sendmail Sender-ID Filter v1.0.0 mx2.paymentallianceintl.com w08NfLDi035577 Authentication-Results: mx2.paymentallianceintl.com; sender-id=pass header.from=mikej@mikej.com; spf=pass smtp.mfrom=mikej@mikej.com X-Authentication-Warning: mx2.paymentallianceintl.com: Host f [162.230.214.65] claimed to be firewall.mikej.com Received: from mail.mikej.com (firewall [192.168.6.63]) by firewall.mikej.com (8.15.2/8.15.2) with ESMTP id w08NfKAh043314; Mon, 8 Jan 2018 18:41:20 -0500 (EST) (envelope-from mikej@mikej.com) X-Authentication-Warning: firewall.mikej.com: Host firewall [192.168.6.63] claimed to be mail.mikej.com MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 08 Jan 2018 18:41:20 -0500 From: Michael Jung To: John Baldwin Cc: freebsd-current@freebsd.org, owner-freebsd-current@freebsd.org Subject: Re: witness_lock_list_get: witness exhausted In-Reply-To: <1684681.MCyL5Ev91y@ralph.baldwin.cx> References: <6eecc842ba7a37af6b2ffe146dfd91da@mikej.com> <1684681.MCyL5Ev91y@ralph.baldwin.cx> Message-ID: <54018b1b2feaab3b05d7ed406eb8273c@mikej.com> X-Sender: mikej@mikej.com User-Agent: Roundcube Webmail/1.3.3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2018 00:02:31 -0000 On 2018-01-08 13:39, John Baldwin wrote: > On Tuesday, November 28, 2017 02:46:03 PM Michael Jung wrote: >> Hi! >> >> I've recently up'd my processor count on our poudriere box and have >> started noticing the error >> "witness_lock_list_get: witness exhausted" on the console. The kernel >> *DOES NOT* crash but I >> thought the report may be useful to someone. >> >> $ uname -a >> FreeBSD poudriere 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r325999: Sun >> Nov >> 19 18:41:20 EST 2017 >> mikej@poudriere:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 >> >> The machine is pretty busy running four poudriere build instances. >> >> last pid: 76584; load averages: 115.07, 115.96, 98.30 >> >> up 6+07:32:59 14:44:03 >> 763 processes: 117 running, 581 sleeping, 2 zombie, 63 lock >> CPU: 59.0% user, 0.0% nice, 40.7% system, 0.1% interrupt, 0.1% idle >> Mem: 12G Active, 2003M Inact, 44G Wired, 29G Free >> ARC: 28G Total, 11G MFU, 16G MRU, 122M Anon, 359M Header, 1184M Other >> 25G Compressed, 32G Uncompressed, 1.24:1 Ratio >> >> Let me know what additional information I might supply. > > This just means that WITNESS stopped working because it ran out of > pre-allocated objects. In particular the objects used to track how > many locks are held by how many threads: > > /* > * XXX: This is somewhat bogus, as we assume here that at most 2048 > threads > * will hold LOCK_NCHILDREN locks. We handle failure ok, and we should > * probably be safe for the most part, but it's still a SWAG. > */ > #define LOCK_NCHILDREN 5 > #define LOCK_CHILDCOUNT 2048 > > Probably the '2048' (max number of concurrent threads) needs to scale > with > MAXCPU. 2048 threads is probably a bit low on big x86 boxes. Thank you for you explanation. We are expanding our ESXi cluster and even though with standard edition I can only assign 64 vCPU's to a guest and as much RAM as I want, I do like to help with edge cases if I can make them occur pushing boundaries as I can towards additianional improvements in FreeBSD. --mikej