[ECODP-dev] ODP-293

Mon Sep 30 08:29:48 UTC 2013

Hi Bert,

What is the capacity of that disk?

As I described in my email with subject "Production database size", the
current database is at least 1 order of magnitude larger than it should be,
and the paster commands that were provided in that email (and with the
previous release) should be used to remove a lot of this data (which should
really be done before the migration). The unused CKAN extensions should
also be removed.

I would not expect this update to significantly increase the amount of disk
space required, but if the disk it is close to the limit already then there
could be problems of course.

Regards,
John

On 30 September 2013 08:59, Bert Van Nuffelen <
bert.van.nuffelen at tenforce.com> wrote:

> Hi John,
>
> Can you have a look to this issue:  ODP-293
>
> This is the description:
>
> From INFRA team:
> #QA-PROBLEM during ckan migration:
> after 2 hours of execution the filesystem of the postgresql database was
> 100% full and the script stopped (see logfile “ckan_migration.log”)
> Please ask contractor how to recover from this situation, whether it’s
> possible to re-run the migration and what is the estimated disk space usage
> for the migration process.
>
> The reference db is the dump you looked at, last week.
>
> Bert
>
>
> --
> Bert Van Nuffelen
>
> Semantic Technologies Software Architect at TenForce
> www.tenforce.be
>
> Bert.Van.Nuffelen at tenforce.com
> Office: +32 (0)16 31 48 60
> Mobile:+32 479 06 24 26
> skype: bert.van.nuffelen
>
> _______________________________________________
> Ecodp-dev mailing list
> Ecodp-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ecodp-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.okfn.org/mailman/private/ecodp-dev/attachments/20130930/5e5e95cc/attachment.html>