Skip to main content

Scaling pains changing ldap to mysql was like changing engine of a nascar during race

When you have a big customer base then you get lots of interesting problems like :
  1. Customers trying to store 400K files in one folder
  2. Customers trying to dump 100+ TB of files in one account
  3. Customers with more than half of their data in Trash
  4. Customers wanting to create> 64K users in an account
  5. Customers with 25K+ users trying to do search/load/sort on users listing
Our startup used to use LDAP to store users and customer metadata and Mysql to store files/folder metadata. 

Lately we had been hit by #4 and #5 item and that is causing scaling issues because no matter what we do ldap write performance sucks when we go beyond some million users.  Earlier ldap used to scale because we had 30-40 ldaps but to reduce ops management issues we consolidated then to 4 per DC and it worked initially but lately with #4 and #5 its not scaling fine.  Ldap is an alien to most programmers, there are only 2-3 guys in the team that knows a little bit about it so most of the times it remains orphan and being involved in every prod issue regarding ldap is not fun.

So we started on a project to replace ldap with mysql but problem is that ldap was in the company from day one so replacing it isnt that easy.  We use SOA and there are many moving parts that uses ldap, converting ldap to mysql required upgrading all services in all data centers at same time which sounds both risky and a hard sell to ops/management team.  So how do you change an engine of a running race car?

Well thats where interface based programming and feature flags comes into picture.

We have all our code related to ldap in one layer implementing DirectoryService Interface



To move to mysql we introduced two fields on each customer ldap_url and mysql_url and prepopulated ldap_url for all customers. We then created RoutingDirectoryService that for each request will determine whether customer is on ldap or mysql and routes the call accordingly to LdapDirectoryService or SqlDirectoryService.

We had to follow the same pattern in all other services and some were written in python so we had to duplicate the effort.

But luckily we were able to achieve the objective with less disruption to release process and we released the code in sleeper mode to prod one service at a time. The code was in sleeper mode because no customers were moved to mysql until we upgraded all services to use router logic.

Last night we migrated 100 customers to mysql and so far we saw only one issue.  We would continue to migrate more customer over the month  and eventually when ldap is gone we would remove RoutingDirectoryService.

4 years ago if we had done this then it would have been easy as no of customers were less but now we have so many customers that  we need to go feature flag way. Also customers rely on us 24X7 so we cant take risk of changing the engines of all car in a running race at the same time so we are now doing one car at a time :) and putting them back on race track.

Comments

Popular posts from this blog

Haproxy and tomcat JSESSIONID

One of the biggest problems I have been trying to solve at our startup is to put our tomcat nodes in HA mode. Right now if a customer comes, he lands on to a node and remains there forever. This has two major issues: 1) We have to overprovision each node with ability to handle worse case capacity. 2) If two or three high profile customers lands on to same node then we need to move them manually. 3) We need to cut over new nodes and we already have over 100+ nodes.  Its a pain managing these nodes and I waste lot of my time in chasing node specific issues. I loath when I know I have to chase this env issue. I really hate human intervention as if it were up to me I would just automate thing and just enjoy the fruits of automation and spend quality time on major issues rather than mundane task,call me lazy but thats a good quality. So Finally now I am at a stage where I can put nodes behing HAProxy in QA env. today we were testing the HA config and first problem I immediat...

Spring 3.2 quartz 2.1 Jobs added with no trigger must be durable.

I am trying to enable HA on nodes and in that process I found that in a two test node setup a job that has a frequency of 10 sec was running into deadlock. So I tried upgrading from Quartz 1.8 to 2.1 by following the migration guide but I ran into an exception that says "Jobs added with no trigger must be durable.". After looking into spring and Quartz code I figured out that now Quartz is more strict and earlier the scheduler.addJob had a replace parameter which if passed to true would skip the durable check, in latest quartz this is fixed but spring hasnt caught up to this. So what do you do, well I jsut inherited the factory and set durability to true and use that public class DurableJobDetailFactoryBean extends JobDetailFactoryBean {     public DurableJobDetailFactoryBean() {         setDurability(true);     } } and used this instead of JobDetailFactoryBean in the spring bean definition     <bean i...

Adding Jitter to cache layer

Thundering herd is an issue common to webapp that rely on heavy caching where if lots of items expire at the same time due to a server restart or temporal event, then suddenly lots of calls will go to database at same time. This can even bring down the database in extreme cases. I wont go into much detail but the app need to do two things solve this issue. 1) Add consistent hashing to cache layer : This way when a memcache server is added/removed from the pool, entire cache is not invalidated.  We use memcahe from both python and Java layer and I still have to find a consistent caching solution that is portable across both languages. hash_ring and spymemcached both use different points for server so need to read/test more. 2) Add a jitter to cache or randomise the expiry time: We expire long term cache  records every 8 hours after that key was added and short term cache expiry is 2 hours. As our customers usually comes to work in morning and access the cloud file server it ...