From: Konrad Scherer <konrad.scherer@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: Re: Getting bitbake_prserv database contents to persist across power loss
Date: Mon, 29 Sep 2014 11:22:02 -0400 [thread overview]
Message-ID: <5429791A.3010405@windriver.com> (raw)
In-Reply-To: <20140926220153.GA29668@bshelton-desktop>
On 09/26/2014 06:01 PM, Ben Shelton wrote:
> Hi all,
>
> We're currently running a shared PR server that is used by all the
> OpenEmbedded build machines on our intranet (both for developers'
> machines and for nightly build machines).
>
> We recently ran into an issue where the blade that the shared PR server
> runs on was shut down unexpectedly and the PR history since the PR
> server was last restarted was not committed to disk. Looking at the
> commit 'prserv: Ensure data is committed', it looks like the only times
> the transactions are committed is when the PR server process is shut
> down.
>
> What would be your guidance in this case? Should we just shut down /
> restart the PR server nightly to save off the data? If we wrote a patch
> to the PR server to commit the data to the database at runtime-specified
> intervals, would that be something we could upstream?
It occurred to me a while ago, that it may be possible to recreate PR server
data from an sstate-cache. The sstate file for the deploy-rpm task contains the
rpms and each rpm contains the PR number. The rest of the PR server fields like
checksum can be retrieved from the sstate filename or siginfo. Unfortunately I
have not written the script or I would be happy to share it with you.
Has anyone tried this? Am I missing something important? A script that does this
would help in situations like this.
--
Konrad Scherer, MTS, Linux Products Group, Wind River
next prev parent reply other threads:[~2014-09-29 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 22:01 Getting bitbake_prserv database contents to persist across power loss Ben Shelton
2014-09-29 15:22 ` Konrad Scherer [this message]
2014-09-29 16:55 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5429791A.3010405@windriver.com \
--to=konrad.scherer@windriver.com \
--cc=bitbake-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.