All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Shelton <ben.shelton@ni.com>
To: bitbake-devel@lists.openembedded.org
Subject: Getting bitbake_prserv database contents to persist across power loss
Date: Fri, 26 Sep 2014 17:01:53 -0500	[thread overview]
Message-ID: <20140926220153.GA29668@bshelton-desktop> (raw)

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?

Thanks,
Ben


             reply	other threads:[~2014-09-26 22:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26 22:01 Ben Shelton [this message]
2014-09-29 15:22 ` Getting bitbake_prserv database contents to persist across power loss Konrad Scherer
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=20140926220153.GA29668@bshelton-desktop \
    --to=ben.shelton@ni.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.