Skip to main content

High Scalability:Denomalizing data for Billions of files for scaling snapshot times

We store metadata about billions of files in Mysql shards and each shard has Folder,File and version table. The schema looked like  this.



Now each file can have n versions and some customers want infinite versions. Problem with scaling snapshot query is that the file system snapshot required information about latest version only. To get latest version you need to join folder, file, version table and discard older rows. I had described the consistent scaling challenge and the improvements we had done to improve snapshot times for our cloud file system in http://neopatel.blogspot.com/2014/02/a-journey-of-scaling-generation-of-file.html.

The latest improvement we did is to denormalize the information about latest entry on to file table itself.
 

Now to generate a snapshot we just need to join Folder and File table. And the improvements are huge. We use box ananometer to log slow queries over all databases and the second query is normalized query and third query is denormalized query. Across all databases we are tracking the time has reduced 3 times  (486 sec to 159 sec), also no of rows examined and rows sent has reduced by half.







Here is the normalized query graph



Here is the denormalized query graph
 
Now denormalizing billions of rows have unique challenges and you need to do it without impacting customers. We spread billions of rows across 28 master and there are 28 slaves for these masters. 

To do performance testing we took the biggest database with customers having 27M rows and imported it in a test environment and migrated it.

27M versions snapshot times before denormalization = 1.2 hours
27M versions snapshot times from denormalized tables = 6.5 minutes constant with or without caching

Off course as we are doubling the data we need to optimize the database tables after denormalization else we were running into row chaining problem.

For production go live as usual we started with feature flags and we added 2 flags latest_entry_migrated and latest_entry_active field on customer model. Then we wrote code that on basis of latest_entry_active flag would execute normalized or denormalized query. Once the code was live in all services then we began migration for few workgroups to test for any bugs. We migrated each data centre every weekend and within a month we had all databases upgraded with denormalized rows and snapshot queries have even gone from slow query logs from many databases.

One sideeffect of this denormalization as this opens up gateway for us to implement infinite versions because now we can sub shard versions on different tables and even in different databases.


Comments

Post a Comment

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...
Post a Comment
Read more

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 ...
Post a Comment
Read more

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...
7 comments
Read more