From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 26E0438432D4; Tue, 10 Jan 2023 14:35:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 26E0438432D4 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1673361335; bh=EafPWLA1t0HFHIi0c1O2G5aFbTtW5/bmC24tDt4E5kE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=R4ohtIAyB6EwZRW3qqOFFZaLJaId6II1pxgyRcj4O8V+6VtdJrop039loXBFH8p0l 0hW6Ohz3CsGoia/92PQuJJGRnxBi54zuqPrsUWfcQNjqxJmjSOE5tmTVeESp/Brsot 5Q+1KJrDA8Yq27QlfJiAtqpMSSzfyOyl7X8TKrHg= From: "fche at redhat dot com" To: elfutils-devel@sourceware.org Subject: [Bug debuginfod/29982] sqlite errors when searching Date: Tue, 10 Jan 2023 14:35:34 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: elfutils X-Bugzilla-Component: debuginfod X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fche at redhat dot com X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29982 --- Comment #9 from Frank Ch. Eigler --- Perhaps a complete highly verbose trace (-vvv) would help identify the caus= e. Scanning threads should not be able to lock each other out for O(1sec) from sqlite operations in normal circumstances. OTOH, one can rest assured that= in case of such sqlite problems, debuginfod just treats them as transient and retries the related scan operation later. Webapi service threads do not contend with the others at all, so clients don't see these transient errors. --=20 You are receiving this mail because: You are on the CC list for the bug.=