ok...I get it. But how come all went through (at the end) the second time. Same db size....and eventually the master went out of initializing and the slave started.
Also....what happens if the db is real large and it needs to start from backup....I mean larger than what is now (and it will be). how will it manage those start times without being considered "dead". Is this normal for a 4GB snapshot to take 30minutes or so to launch on mysql...? apparently not since at the second startup it took much less.... On Dec 24, 3:41 pm, Alex Kovalyov <[email protected]> wrote: > In your log: Instance 'i-31a11a58' did not send 'hostUp' event in 2400 > seconds after launch. Considering it broken. Terminating instance. > > So master isn't starting actually. > It's because your database is very big. It successfully downloads the > snapshot but doesn't have enough time to upload it back. > > 24-12-2008 06:40:34 WARN PollerProcess Instance 'i-31a11a58' did not > send 'hostUp' event in 2400 seconds after launch. Considering it > broken. Terminating instance. > > 24-12-2008 06:38:53 DEBUG i-31a11a58/mysql-init.sh Locking tables and > creating data snapshot. > > 24-12-2008 06:38:50 DEBUG i-31a11a58/mysql-init.sh Bundling MySQL > data. > > 24-12-2008 06:38:47 DEBUG i-31a11a58/mysql-init.sh Locked MySQL data > bundle creation (PID: 2422). > > 24-12-2008 06:31:00 INFO i-31a11a58/mysql-init.sh Snapshot > successfully extracted. > > 24-12-2008 06:27:32 INFO i-31a11a58/mysql-init.sh Extracting MySQL > data snapshot. > > 24-12-2008 06:27:30 INFO i-31a11a58/mysql-init.sh Successfully fetched > snapshot from s3://farm-923-918348349691/farm-mysql/mysql- > snapshot.tar. > > Increase timeouts on role settings. > > On 24 дек, 14:52, afishler <[email protected]> wrote: > > > Seems like strange behavior continues....mysql master started, slave > > did not. I am not sure if this is reasonable performance but the > > master took 30 minutes to recover the 4GB snapshot that was stored as > > backup. > > > It finished starting successfully, I could connect to mysql but > > suddenly it went down and now a new instance is starting....all this > > time no sign of the slave. Mysql role is configured for min and max of > > 2 instances on my farm > > > On Dec 24, 2:03 pm, Max <[email protected]> wrote: > > > > I also noticed instance not launching. > > > > But I created farm with only load balancer. > > > I thought it is not launching because I have not added app roles. > > > > On Dec 24, 2:00 pm, afishler <[email protected]> wrote: > > > > > well they finally appeared...after about 10 minutes? Why was it so > > > > slowwwww? > > > > > On Dec 24, 1:53 pm, afishler <[email protected]> wrote: > > > > > > I am starting a fram and as usual I get a confirmation window for the > > > > > number of instances about to be launched. > > > > > > Still NO INSTANCES ARE LAUNCHED! They do not appear in the instance > > > > > view, nor in the Elasticfox....I repeated this twice. did not see > > > > > anything in the logs.... > > > > > > What's going on? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
