Estimate on the PROD migration finish is in about 24 hours from now. STG
was seamless, so I'm not expecting any troubles here either.
On Wed, Jan 25, 2017 at 10:47 AM, Josef Skladanka
wrote:
> STG is done (took about 15 hours), starting the archive migration for
> PROD, and I'll start figuring w
STG is done (took about 15 hours), starting the archive migration for PROD,
and I'll start figuring way to merge the data. Probably tomorrow.
On Tue, Jan 24, 2017 at 5:49 PM, Josef Skladanka
wrote:
> So I started the data migration for the STG archives - should be done in
> about 15 hours from n
So I started the data migration for the STG archives - should be done in
about 15 hours from now (running for cca six hours already) - estimated on
the number of results that were already converted.
If that goes well, I'll start the PROD archives migration tomorrow, and
start working on merging the
So, as we discussed during meeting, I have offloaded the data (for stg)
older than half a year to another database. This is how I did it (probably
could have been done more efficiently, but hey, this worked, and I'm not
postgres expert...):
$ pg_dump -Fc resultsdb_stg > resultsdb_stg.dump # dump t
On Mon, Dec 5, 2016 at 4:25 PM, Tim Flink wrote:
> Is there a way we could export the results as a json file or something
> similar? If there is (or if it could be added without too much
> trouble), we would have multiple options:
>
Sure, adding some kind of export should be doable
>
> 1. Dump
On Fri, 25 Nov 2016 13:01:51 +0100
Josef Skladanka wrote:
> So, I have performed the migration on DEV - there were some problems
> with it going out of memory, so I had to tweak it a bit (please have
> a look at D1059, that is what I ended up using by hot-fixing on DEV).
>
> There still is a sli
- Original Message -
> From: "Kamil Paral"
> To: "Fedora QA Development"
> Sent: Friday, November 25, 2016 2:58:03 PM
> Subject: Re: ResultsDB 2.0 - DB migration on DEV
>
>
>
>
> So, I have performed the migration on DEV - there were so
> So, I have performed the migration on DEV - there were some problems with it
> going out of memory, so I had to tweak it a bit (please have a look at
> D1059, that is what I ended up using by hot-fixing on DEV).
> There still is a slight problem, though - the migration of DEV took about 12
> hou
So, I have performed the migration on DEV - there were some problems with
it going out of memory, so I had to tweak it a bit (please have a look at
D1059, that is what I ended up using by hot-fixing on DEV).
There still is a slight problem, though - the migration of DEV took about
12 hours total,