Using mysql64 instance with LVM enabled is the right option for your
databases size. 32-bit instance could handle databases of up to 65G.

Feel free to edit MySQL settings file (/etc/mysql/my.cnf on Debian/
Ubuntu systems) but keep in mind that you need 'Sync to all' every
time settings were changed.

On Oct 2, 1:40 am, mikeytag <[EMAIL PROTECTED]> wrote:
> Nickolas,
> Let me ask you a quick question. I am getting ready to scp my
> databases over to scalr. Would it be better for me to use the mysql64
> instance? I currently am using about 80G for my databases.
>
> In addition, my current db server has several customizations to my.cnf
> like innodb_file_per_table, key_buffer size, etc. Is it ok for me to
> edit the my.cnf file whenever I can get a mysql scalr instance up and
> then synchronize to all with a new name? I guess I am wondering if me
> editing the /etc/my.cnf file could potentially break the cool features
> of automatic backup and such that scalr offers.
>
> Thanks,
> Mike
>
> On Oct 1, 10:18 am, Nickolas Toursky <[EMAIL PROTECTED]> wrote:
>
> > There was an error in MySQL initialization scripts.
> > It works now.
>
> > Thanks for patience.
>
> > On Oct 1, 2:14 am, mikeytag <[EMAIL PROTECTED]> wrote:
>
> > > Not sure how I could have caused this, but I cannot bring up a
> > > mysqllvm64 instance. I have not even logged into it or begun
> > > configuring it in anyway. Here are the pertinent log entries:
>
> > > 30-09-2008 16:59:13     WARN    PollerProcess   Disaster: No instances
> > > running in role mysqllvm64!
> > > 30-09-2008 16:58:29     ERROR   i-b3f456da/instance-down.sh     Failed to
> > > bundle MySQL data.
> > > 30-09-2008 16:58:20     INFO    i-b3f456da/instance-down.sh     Farm is 
> > > being
> > > halted. Performing MySQL data bundle.
> > > 30-09-2008 16:56:53     ERROR   i-b3f456da/instance-up.sh       
> > > /usr/local/aws/
> > > bin/mysql-init.sh failed. Exiting.
> > > 30-09-2008 16:56:51     ERROR   i-b3f456da/mysql-init.sh        Failed to 
> > > bundle
> > > MySQL data.
> > > 30-09-2008 16:56:48     ERROR   i-b3f456da/mysql-init.sh        Snapshot
> > > creation failed!
> > > 30-09-2008 16:56:33     INFO    i-b3f456da/mysql-init.sh        Snapshot
> > > successfully extracted.
> > > 30-09-2008 16:56:31     INFO    i-b3f456da/mysql-init.sh        
> > > Extracting MySQL
> > > data snapshot.
> > > 30-09-2008 16:56:28     INFO    i-b3f456da/mysql-init.sh        
> > > Successfully
> > > fetched snapshot from s3://FARM-517-261661395058/farm-mysql/mysql-
> > > snapshot.tar.
> > > 30-09-2008 16:56:22     INFO    i-b3f456da/mysql-init.sh        Trying to 
> > > fetch
> > > previous MySQL snapshot from s3://FARM-517-261661395058/farm-mysql/
> > > mysql-snapshot.tar (21688320 bytes).
> > > 30-09-2008 16:38:53     INFO    i-b3f456da/instance-init.sh     Host
> > > 10.250.103.207/mysql initialized. Awaiting authentication data.
> > > 30-09-2008 16:37:12     WARN    PollerProcess   Disaster: No instances
> > > running in role mysqllvm64!
>
> > > Any ideas?
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"scalr-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/scalr-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to