Meeting the challenges of OLTP Big Data with Scylla
•
0 likes•664 views
Scylla has emerged as the most cost-effective way to serve large amounts of data. In this keynote we will cover what makes Scylla such a great match for big data applications, what we’ve done over the past year, and our plans for the near future: performance, reliability, manageability, and above all, making Scylla easier to consume in the modern cloud environment.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Meeting the challenges of OLTP Big Data with Scylla
Similar to Meeting the challenges of OLTP Big Data with Scylla (20)
More from ScyllaDB
More from ScyllaDB (20)
Recently uploaded
Recently uploaded (20)
Meeting the challenges of OLTP Big Data with Scylla
- 1. Meeting the Challenges of Big Data with Scylla Avi Kivity
- 2. Avi Kivity CTO, ScyllaDB Original author, Linux KVM. Working on Seastar and ScyllaDB to make distributed systems as efficient as they can be. 2
- 3. The Speaker’s camera displays here A suite of solutions 3 Monitorin g Operator Cloud Enterprise Manager Alternator Drivers
- 7. Performance has many facets 7 ▪ Direct cost of sustaining the workload ▪ Ability to sustain workload • While scaling up • While performing maintenance operations ▪ Handling varied query types ▪ Managing dense nodes
- 8. Our bread and butter ▪ Continuing to make the most out of your hardware • Utilize all cores • Utilize all memory for caching • Make good use of fast solid state storage ▪ Recent improvements • B+tree in cache • Reactor stall elimination • C++ coroutines 8
- 9. Controlling Space Amplification 9 ▪ New Incremental Compaction feature: space_amplification_goal • When enabled, Scylla works towards minimizing duplication due to overwrites and deletions
- 10. Handling more query types ▪ Point queries inside large partitions ▪ Time Window Compaction Strategy optimizations 10
- 11. Workload isolation improvements ▪ I/O scheduler update • Better isolation of compaction • Improved support of medium-speed disks 11
- 13. Improving Elasticity 13 ▪ Repair based node operations ▪ Incremental bootstrap and decommission ▪ Multinode growth 7 nodes 8 nodes 9 nodes6 nodes 20 ms 7 nodes 8 nodes 9 nodes6 nodes
- 14. Reshard and reshape ▪ Redistribute data during startup if needed • Changes in core count • Changes in compaction strategy ▪ Reshape data during repair/bootstrap • Reduces read amplification 14
- 15. Streaming nodetool refresh ▪ Currently, nodetool refresh only loads local data • Non-local data is discarded • Increases restore/migrate time on large clusters ▪ Will stream non-local data • Full replication from backup • Speeds up data migration 15
- 17. Improving Consistency 17 ▪ Raft as a common consistency protocol ▪ Raft for Schema Management ▪ Raft for Topology ▪ Raft for Tables
- 18. Adopting Raft across the board ▪ Raft emerges as the industry’s favorite consistency protocol • Easy(ier) to understand • Formal proofs • Better performance than Paxos ▪ Single implementation, multiple use cases • Increases reliability 18
- 19. Raft for Schema Management ▪ Eliminate inherent race conditions in DDL statements ▪ Example: dropping a type 19 DROP TYPE my_type; CREATE TABLE tab ( id int PRIMARY KEY, value my_type );
- 20. Raft for Topology ▪ Eliminate edge cases where operator intervention is required ▪ Enable scaling out to multiple new nodes in parallel ▪ Enable incremental scaling ▪ Prepare the groundwork for strongly consistent tables 20
- 21. Raft for Tables ▪ Strongly consistent mode to complement Eventual Consistency ▪ Higher consistency guarantees ▪ Better guarantees for indexes, materialized views, change data capture ▪ No performance loss ▪ But: reduced availability during failover 21
- 22. Tablets ▪ A different way to split data among nodes • Incremental scaling • Requires better coordination • Raft to the rescue 22
- 24. Change Data Capture 24 ▪ Generally available in Scylla 4.3+ ▪ Using good old CQL syntax and protocols • Standard drivers • Easy to integrate ▪ Also comes with Alternator (as Streams)
- 25. Use cases for CDC ▪ Duplicate data from Scylla to another database ▪ Analyze data in semi-real-time ▪ Feed data into a message queue (Kafka) 25
- 26. CDC Example 26 cqlsh:ks1> CREATE TABLE tab (pk int, ck int, v text, PRIMARY KEY (pk, ck)) WITH CDC = {'enabled': true, 'preimage': true}; cqlsh:ks1> INSERT INTO tab (pk, ck, v) VALUES (100, 1, 'aaa'); cqlsh:ks1> INSERT INTO tab (pk, ck, v) VALUES (100, 2, 'bbb'); cqlsh:ks1> UPDATE tab SET v = 'ccc' WHERE pk = 100 AND ck = 2; cqlsh:ks1> DELETE FROM tab WHERE pk = 100 AND ck = 1; cqlsh:ks1> SELECT * FROM tab_scylla_cdc_log; cdc$stream_id | cdc$time | cdc$batch_seq_no | cdc$deleted_v | cdc$end_of_batch | cdc$operation | cdc$ttl | ck | pk | v ------------------------------------+--------------------------------------+------------------+---------------+------------------+---------------+---------+----+-----+---- -- 0x1a300000000000005e73bc01cc000901 | 863df074-4e9b-11eb-a4b4-60ce0fb4996e | 0 | null | True | 2 | null | 1 | 100 | aaa 0x1a300000000000005e73bc01cc000901 | 8a75010a-4e9b-11eb-cbb1-632edb5255c4 | 0 | null | True | 2 | null | 2 | 100 | bbb 0x1a300000000000005e73bc01cc000901 | 93a10f1c-4e9b-11eb-2b6f-8b927b1c45bd | 0 | null | null | 0 | null | 2 | 100 | bbb 0x1a300000000000005e73bc01cc000901 | 93a10f1c-4e9b-11eb-2b6f-8b927b1c45bd | 1 | null | True | 1 | null | 2 | 100 | ccc 0x1a300000000000005e73bc01cc000901 | 9a40f5ee-4e9b-11eb-3b1f-63a99732aa00 | 0 | null | null | 0 | null | 1 | 100 | aaa 0x1a300000000000005e73bc01cc000901 | 9a40f5ee-4e9b-11eb-3b1f-63a99732aa00 | 1 | null | True | 3 | null | 1 | 100 | null
- 28. ▪ Bare metal / on premises ▪ Virtualized on Public Cloud ▪ Containerized, w/ container engine ▪ Kubernetes ▪ AWS Outposts ▪ Scylla Cloud ▪ Scylla Cloud - Bring Your Own Account ▪ Embedded So many environments... 28
- 29. Challenges ▪ Many Operating Systems ▪ Many Hardware configs ▪ Internet connectivity ▪ Root access ▪ Centralized administration and monitoring ▪ Third party agents Bare metal 29 Solutions ▪ Unified .rpm/.deb/.tar ▪ iotune, installer ▪ Prepackaged dependencies ▪ Tarball install ▪ Scylla Manager and Monitoring ▪ Helper slice
- 30. Challenges ▪ Exploit uniformity ▪ Simplify deployment ▪ Multiple vendors Public Cloud deployment Solutions ▪ Pre-configured images ▪ CloudFormation templates ▪ New! GCP machine image 30
- 31. Challenges ▪ State-intensive system ▪ Complex administration ▪ Reduced control over host Containers and Kubernetes Solutions ▪ Use StatefulSets ▪ Scylla Operator ▪ Work with Kubernetes APIs to regain control 31
- 32. Challenges ▪ Want, but cannot use Public Cloud ▪ DynamoDB not available on Outposts AWS Outposts Solutions ▪ Use Outposts ▪ Use ScyllaDB (with or without Alternator) 32
- 33. Challenges ▪ Managing a distributed database is hard ▪ Repair, backup, scaling ▪ Minimize latency and cost ▪ Multiple Public Clouds Scylla Cloud Solutions ▪ Hand that over to the experts ▪ Automated solution ▪ VPC Peering ▪ AWS, GCP supported 33
- 34. Challenges ▪ Financial or regulatory barriers to using a SaaS database ▪ Security ▪ Complex setup Bring Your Own Account Solutions ▪ Run Scylla Cloud using your own public cloud account ▪ Principle of Least Privilege, audit ▪ Scylla Cloud Automation 34
- 35. Challenge ▪ Non-Cloud product needs a database ▪ Embedded environments are constrained and “special” Embedded Scylla Solution ▪ Embed Scylla in your product ▪ Scylla is frugal; work with our team to maximize utilization 35
- 37. Monitoring and observability 37 ▪ Increased refinement and simplification of the dashboards ▪ Advisor section: actionable advice ▪ More detailed tracing ▪ Access metrics and perform operations from CQL
- 38. Detailed tracing example 38 select * from t where p = 7; activity | timestamp | source | source_elapsed | client -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+-----------+----------------+----------- Execute CQL3 query | 2020-08-07 13:25:04.363000 | 127.0.0.1 | 0 | 127.0.0.1 Parsing a statement [shard 0] | 2020-08-07 13:25:04.363310 | 127.0.0.1 | -- | 127.0.0.1 Processing a statement [shard 0] | 2020-08-07 13:25:04.363384 | 127.0.0.1 | 74 | 127.0.0.1 Creating read executor for token 1634052884888577606 with all: {127.0.0.1} targets: {127.0.0.1} repair decision: NONE [shard 0] | 2020-08-07 13:25:04.363450 | 127.0.0.1 | 139 | 127.0.0.1 read_data: querying locally [shard 0] | 2020-08-07 13:25:04.363455 | 127.0.0.1 | 145 | 127.0.0.1 Start querying singular range {{1634052884888577606, pk{000400000007}}} [shard 0] | 2020-08-07 13:25:04.363461 | 127.0.0.1 | 151 | 127.0.0.1 Querying cache for range {{1634052884888577606, pk{000400000007}}} and slice {(-inf, +inf)} [shard 0] | 2020-08-07 13:25:04.363490 | 127.0.0.1 | 180 | 127.0.0.1 Range {{1634052884888577606, pk{000400000007}}} not found in cache [shard 0] | 2020-08-07 13:25:04.363494 | 127.0.0.1 | 183 | 127.0.0.1 Reading key {{1634052884888577606, pk{000400000007}}} from sstable /home/sarna/.ccm/scylla-1/node1/data/ks/t-f7b7a9b0d89f11eab650000000000000/mc-1-big-Data.db [shard 0] | 2020-08-07 13:25:04.363522 | 127.0.0.1 | 211 | 127.0.0.1 /home/sarna/.ccm/scylla-1/node1/data/ks/t-f7b7a9b0d89f11eab650000000000000/mc-1-big-Index.db: scheduling bulk DMA read of size 16 at offset 0 [shard 0] | 2020-08-07 13:25:04.363546 | 127.0.0.1 | 235 | 127.0.0.1 /home/sarna/.ccm/scylla-1/node1/data/ks/t-f7b7a9b0d89f11eab650000000000000/mc-1-big-Index.db: finished bulk DMA read of size 16 at offset 0, successfully read 16 bytes [shard 0] | 2020-08-07 13:25:04.364406 | 127.0.0.1 | 1095 | 127.0.0.1 /home/sarna/.ccm/scylla-1/node1/data/ks/t-f7b7a9b0d89f11eab650000000000000/mc-1-big-Data.db: scheduling bulk DMA read of size 56 at offset 0 [shard 0] | 2020-08-07 13:25:04.364445 | 127.0.0.1 | 1134 | 127.0.0.1 /home/sarna/.ccm/scylla-1/node1/data/ks/t-f7b7a9b0d89f11eab650000000000000/mc-1-big-Data.db: finished bulk DMA read of size 56 at offset 0, successfully read 56 bytes [shard 0] | 2020-08-07 13:25:04.364599 | 127.0.0.1 | 1288 | 127.0.0.1 Querying is done [shard 0] | 2020-08-07 13:25:04.364685 | 127.0.0.1 | 1375 | 127.0.0.1 Done processing - preparing a result [shard 0] | 2020-08-07 13:25:04.364719 | 127.0.0.1 | 1408 | 127.0.0.1 Request complete | 2020-08-07 13:25:04.36442
- 39. Drivers 39
- 40. Driver updates 40 ▪ New Rust driver ▪ Revamped C++ driver ▪ Updates to existing drivers (Java/Go/Python) • Shard awareness • CDC optimizations
- 42. Download Scylla Open Source: scylladb.com/download Talk to an expert: scylladb.com/consultation Take a test drive: scylladb.com/test-drive The Speaker’s camera displays here Experience Scylla for Yourself 42