RUNNING PETABYTE-SIZED CLUSTERS

Transcription

1 1

2 RUNNING PETABYTE-SIZED CLUSTERS CASE STUDIES FROM THE REAL WORLD 2

3 GROWTH OF UNSTRUCTURED DATA 80% 74% 67% EB Total Capacity Shipped, Worldwide 71 EB 133 EB Source: IDC Unstructured Data

4 DIGITAL UNIVERSE Consumer generated Internet of things Emerging markets Created by devices Double every two years

5 THE PETABYTE CLUB How many are already a member of the Petabyte Club? within the next 3 years?

6 Customer Reference - Kaltura EMC Isilon powers massive growth of online video provider Challenge Revenue increasing hundreds of percent annually Limited storage scalability threatening to restrict company from taking on new accounts Solution EMC Isilon NL Series SmartConnect Applications Kaltura MediaSpace, Kaltura Management Console, Microsoft Exchange, MySQL, Vmware ELAD AVRAHAMI Sr. Director of Operations Isilon is unlike any of the other solutions we considered, because it grows to an extremely large scale very quickly and seamlessly. We continue to buy Isilon because of the solution's excellent price/performance and the business strength that EMC brings to the table. Results Increased competitive advantage with rapid storage scalability Improved performance by 25 percent Lowered TCO by $3,300 per month Reduced storage administration resources 50%

7 THREE PRINCIPAL CONSIDERATIONS FILE SYSTEMS SSD DEVICES CAPACITY

8 CONSIDERATION: FILE SYSTEMS

9 FILE SYSTEM CHALLENGES Sizing for device and data characteristics Sequential backup operations Lock contention Lack the economies of storage tiering Missing flexible recovery service levels

10 DIRECTORY LAYOUT Square vs Narrow/Deep vs Shallow/Wide 10K files (No SSD), 100K files (SSD) Directory locking Large number of creates Large number of deletes Flexibility Snapshots, SyncIQ Parallelism in NDMP backups, SyncIQ deltas

11 TIERING Sensible tiering If application supports it Tier by path If interactive users, maintain metadata acceleration across tiers to maintain consistent experience Don t mix node types in the same tier Inconsistent performance SSD vs No SSD Different SSD strategies

12 DATA PROTECTION Set the appropriate data protection levels ~10 nodes = +2 ~15 nodes = +3 >20 nodes = % Ability to pin directories to specific pools/rules Reduce failure domains Flexible protection levels Different metadata strategies Performance guarantees FAILED FAILED 100% 100% 100% 100% 100% 100% 100%

13 CONSIDERATION: SSD DEVICES

14 DISK DEVICE CHALLENGES Keeping pace with workflow requirements Protecting user experience Improving RPO/RTO Handling metadata Improving file system analytics

15 WHY DO I NEED SSD? Improved workflow performance Data on SSD Metadata acceleration Read Only or Read Write L3 cache (Default as of OneFS 7.1.1) Improved user experience Large directories return faster in listing (Windows Explorer, ls) DRAM SmartFlash Hard Drive Node 1 Node 2 Node 3 Node 4 Up to 37 TB Up to 1 PB Up to 20 PB

16 MORE REASONS FOR SSD Improved data analytics and protection performance Faster data protection/balancing version of the job SSD driven jobs to improve HDD availability for serving data SSD driven FSAnalyze for quicker analytics results Improved RPO/RTO doing NDMP backup/restore or SyncIQ replication

17 CONSIDERATION: CAPACITY

18 CAPACITY CHALLENGES Disruptive storage expansion Planning cluster expansion Maximizing utilization, minimizing latency

19 STREAMLINED CAPACITY MANAGEMENT ISILON AUTOBALANCE BALANCED EMPTY FULL BALANCED EMPTY Capacity in 60 seconds Additional capacity is available in less than a minute after adding node to cluster. FULL BALANCED EMPTY FULL BALANCED EMPTY FULL BALANCED AutoBalance Automated data balancing across nodes reduces costs, complexity, and risks for scaling storage EMPTY

20 CLUSTER UTILIZATION Do not run cluster/pools at 100% full 3 stages of utilization to take note of 85% - Start drawing up options for growth 90% - Performance degradation 95% - Severe performance degradation and data protection at risk

21 LATENCY LATENCY INCREASES AT HIGH UTILIZATION RATES

22 CONSIDERATION: PERFORMANCE

23 Cluster sizing Once you determine: Throughput desired I/O pattern (random/sequential) Block size It s a matter of building up the blocks

24 PERFORMANCE OneFS > Linear with scale S-Nodes X-Nodes NL-Nodes CAPACITY

25 SUMMARY

26 BEST PRACTICES Always include SSDs if possible Always have sufficient free space to allow for data protection (White Paper available soon!) Take restripe activity into account when adding nodes Allow free ports on IB switch for node refreshes

27 TAKE THE NEXT STEP! Are you confident you are able to manage a Petabyte-sized cluster? Engage RMS for OneFS upgrades Engage the services of a TAM for operational assistance

28