Tag Archives: migration.

Timeout issue resolved

Hello. As you may be aware, we have been having an intermittent timeout issue that was affecting some transactions since we migrated the Folksy stack.

After a great deal of investigation with our host’s support people, we have found the issue, and resolved it earlier this morning.
We’re continuing to monitor any errors generated to see if any trace of the problem remains, but so far it’s looking good for it being fixed.
We’re sorry for anybody that has been inconvenienced by this issue, and we thank everybody for bearing with us whilst we fixed the teething problems arising from the migration to new hosts.
Thanks,
Doug.

Tagged ,

Nameserver propagation seems to have caught up.

Hi — we’ve been watching the access logs on the old servers, and all we’ve seen on there is traffic from load-balancer checks and spiders for a while, so it looks like the DNS has finally propagated everywhere it should have.

We’ll keep looking into why it took as long as it did with our registrar, but for now it feels reasonably safe to say that everybody should be seeing Folksy on the new servers.

I’d like to take the opportunity to thank everybody for being so patient with us whilst we undertook this vital work. This migration means that we are now better placed to pay back some of that patience and understanding by evolving the whole Folksy platform.

Thanks again,

   Doug.

Tagged , , ,

Some people still seeing the maintenance page

We’re just waiting for the DNS server to propagate, and unfortunately it sounds like the nameserver changes are taking longer to propagate to some ISPs than others. We’re still waiting for an estimate from Gandi (our Domain Name Registrar) on how long this will take and we’ll let you know as soon as we have any updates.

In the meantime, some people have found that using 3G (their phone) to access the site works whilst they’re waiting.

And once again, we’re really sorry for all the people who can’t access the site, still.

   Doug.

Tagged , ,

Some people not able to access Folksy or the Forums, still

Hi. Some people are not seeing either Folksy or the forums, this morning.
It looks like this is because the changes to the nameservers that we made a couple of nights ago haven’t propagated everywhere, yet, so some people are still seeing the old servers (which are either in maintenance mode, or no longer serving).
We expected that this propagation to take 6 to 24 hours, but it’s looking like we should have given it a day or so more.
Some people have reported being able to access the site after clearing their internet cache, but if that doesn’t work, it will be a matter of waiting.
I apologise to anyone still unable to access the site. We’re raising a ticket with our nameserver hosts, but aside from that, there’s really not anything we can do except wait for the nameserver changes to propagate fully.
So I am really sorry about that. I’ll update the maintenance page displaying, now, to point at this status post, and in the meantime, can only offer my apologies to anyone affected.
Thanks,
Doug.

Tagged , ,

Some people not able to access Folksy or the Forums, still

Hi. Some people are not seeing either Folksy or the forums, this morning.
It looks like this is because the changes to the nameservers that we made a couple of nights ago haven’t propagated everywhere, yet, so some people are still seeing the old servers (which are either in maintenance mode, or no longer serving).
We expected that this propagation to take 6 to 24 hours, but it’s looking like we should have given it a day or so more.
Some people have reported being able to access the site after clearing their internet cache, but if that doesn’t work, it will be a matter of waiting.
I apologise to anyone still unable to access the site. We’re raising a ticket with our nameserver hosts, but aside from that, there’s really not anything we can do except wait for the nameserver changes to propagate fully.
So I am really sorry about that. I’ll update the maintenance page displaying, now, to point at this status post, and in the meantime, can only offer my apologies to anyone affected.
Thanks,
Doug.

Tagged , ,

Folksy running on new host, forums catching up

Hi — so the migration has finished, and Folksy seems to be running well on EC2.

Obviously, this is the wee hours, so we’ll keep monitoring to make sure that everything is behaving as well and in as performant a manner as it should.

Currently, it looks like the DNS records for the forums haven’t caught up, sorry. I expect that to be resolved within the next hour or so.

I’ll keep watch for a while longer tonight, then will be checking back in with the team tomorrow.

In the meantime, thanks very much once again for bearing with us whilst we performed this work. We’ll try our level best to minimise any issues that arise tomorrow (today) as the new deployment beds in.

Cheers,

   Doug.

Tagged , ,

Maintenance mode at 23:00 for a few hours

Hi — just a reminder that we’ll be going into maintenance mode to migrate Folksy to a new host, at 23:00, or thereabouts. And that it will take a few hours, at least.

I’ll keep you posted here as to progress.

Cheers,

   Doug.

Tagged , ,

Changing Folksy’s nameservers

Hi — in preparation for the migration work planned for tomorrow night, we’re changing Folksy’s nameservers tonight. These are what allow us to map the name folksy.com to our servers, so are a pretty vital part of the infrastructure!

It should be a straightforwards change from one set of nameservers to another, but I thought I’d best let you know what we’re up to, here, just in case there was any weirdness.

Cheers,

   Doug.

Tagged , ,

A few hours downtime on Wednesday night (23:00), and possible issues the following day

Hello. We’re going to be transferring Folksy to be hosted on the EC2 platform, this week. This is something that we’ve been working on for quite some time, and has taken a large amount of re-engineering of Folksy’s architecture. There are many reasons for making this move, but chief amongst them are the unparalleled opportunities EC2 offers for scaling Folksy up to meet a steadily growing demand, for adapting quickly to spikes in that demand, and for easing the transition of Folksy from a ‘traditional’ monolithic web application to a more distributed set of dynamic services.
It’s a pretty big job that involves taking all of Folksy’s services (web apps, databases, search indices, etc.), with their rebuilt relationships, and transferring them across to the new platform.
We expect to be ready to make the move over to the new platform late on Wednesday night / Thursday morning. We’ve chosen that time to minimise the unavoidable interruption to the service. The actual migration itself could take a few hours, and Folksy will be unavailable for the duration. Naturally, we’ll be working to get everything up and running in time for the next day’s business, and we’ll keep you all posted as to progress on the status blog.
We would be remiss if we did not offer one final note of caution:
Once we’ve got Folksy up and running under full demand again the next day, it’s possible that problems may arise that our testing could not lead us to anticipate. Hopefully, we’d be able to deal with any such issues as they occur, with a minimum of inconvenience to users. In the worst case scenarios, however, they could take time to fix, leading to performance issues, and even service outages whilst they were dealt with.
We have, of course, done our level best to ensure that the migration is a pain-free as possible.
Happily, this sort of large-scale migration event is pretty rare, and once it is completed, it puts us in a great position to get back on with developing and deploying the new features that will take Folksy to the next stage, and beyond.
In the meantime thanks for bearing with us, as ever.
Doug.

Tagged , ,
Advertisements