Hi, Before increasing the memory size, there's few info we need to find out:
- JVM memory allocation (need the Zanata 3.9.6 url to get access to the info) - Ian, do you have the log file (stack trace) of when the error occur? Also, which Zanata you were using to test 3.9.6? https://translate-dev.openstack.org is not upgraded yet. I suspect its the JVM allocation which might need some tweak. But its best it I can access to the 3.9.6-dev and try to replicate the error from there. --------------------------------------------- Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com On Mon, Jan 16, 2017 at 8:01 AM, Alex Eng <a...@redhat.com> wrote: > How much memory do we think will be necessary? The current instance is >> an 8GB RAM instance. As long as we have quota for it, there should not >> be a problem redeploying on a bigger instance. > > > Can we look at 10GB? and run the same test again to make sure its running > alright. > I assume mysql DB is running on separate server? > > >> I have commented on this change. I would prefer we not backup the dev >> server and only backup the production server. We don't treat our dev >> servers as permanent or reliable installs as they may need to be >> reloaded for various reasons to aid development and testing. Also we >> should set up backups similar to how we do the other services (I left a >> comment on this change with a link to an example). > > > Agree. I would suggest if possible, sync DB data from prod to dev weekly. > This would help on allowing us to debug if there's any issue in prod. > > This is something that can be discussed with the infra team, typically >> we would give access to someone assisting with implementation to the >> -dev server while keeping the production server as infra-root only. I >> will make sure fungi sees this. > > > Again, if we can constantly sync prod to dev instance, we will only need > root access to dev server. > > > > --------------------------------------------- > > Alex Eng > Senior Software Engineer > Globalisation Tools Engineering > DID: +61 3514 8262 <callto:+61+3514+8262> > Mobile: +614 2335 3457 <callto:+614+2335+3457> > > Red Hat, Asia-Pacific Pty Ltd > Level 1, 193 North Quay > Brisbane 4000 > Office: +61 7 3514 8100 <callto:+61+7+3514+8100> > Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> > Website: www.redhat.com > > On Sat, Jan 14, 2017 at 7:31 AM, Clark Boylan <cboy...@sapwetik.org> > wrote: > >> On Thu, Jan 12, 2017, at 02:36 PM, Ian Y. Choi wrote: >> > - I18n team completed tests with current Zanata (3.7.3) with Xenial [1], >> > but found one error >> > mentioned in [2]. It seems that more memory size allocation for >> > Zanata with Java 8 is needed. >> > Could you upgrade the memory size for translate-dev server first to >> > test again? >> >> How much memory do we think will be necessary? The current instance is >> an 8GB RAM instance. As long as we have quota for it, there should not >> be a problem redeploying on a bigger instance. >> >> > - I remember that newer version of openstackid needs to be tested with >> > translate-dev. >> > So I have just uploaded this patch: >> > https://review.openstack.org/#/c/419667/ . >> > I18n team needs more tests, but I think it is a good time to change >> > to openstackid-dev for such testing. >> > Please ping me after openstackid-dev test with translate-dev is >> > completed with no error :) >> > >> > - On last I18n team meeting, I18n team recognized that the backup would >> > be so important. >> > Is there more disks for such backup on translate-dev and >> > translate.o.o server? >> > And the approach implementing like [3] looks quite a good idea I >> > think. Thanks, Frank! >> >> I have commented on this change. I would prefer we not backup the dev >> server and only backup the production server. We don't treat our dev >> servers as permanent or reliable installs as they may need to be >> reloaded for various reasons to aid development and testing. Also we >> should set up backups similar to how we do the other services (I left a >> comment on this change with a link to an example). >> >> > - Can I have root access to translate-dev and translate server? >> >> This is something that can be discussed with the infra team, typically >> we would give access to someone assisting with implementation to the >> -dev server while keeping the production server as infra-root only. I >> will make sure fungi sees this. >> >> Hope this helps, >> Clark >> >> >
_______________________________________________ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
