Infinispan for Ninja Developers

Transcription

1

2 Infinispan for Ninja Developers Mircea Markus, Red Hat R&D

3 Who s this guy? R&D RedHat/Clustering Infinispan developer - day 1 Founder Radargun JBoss clustering: jgroups, JBossCache..

4 Agenda Transactions xa or not recovery locking, deadlock detection Client server access Querying and indexing Consistency and topology changes Distribution topology-aware virtual nodes

5 Transactions JTA transactions known API Multiple options full xa (XAResource) less strict (Synchronization) Configurable same client API

6 XA or not? XA proper distributed transactions recovery enabled or not (default) Synchronization cache backed by a data store Transaction more efficient 1PC optimisation TM not writing logs Hibernate 2LC

7 Recovery When is needed? prepare successful, commit fails inconsistent state! How to handle it TM informs SysAdmin JMX tooling exposed to force commit force rollback

8 Tx & Locking MVCC lock free reads Lazy locking locks acquired at prepare time Eager locking on each write

9 Deadlocks Deadlock Tx1: a -> b Tx2: b -> a right timing Bad for system throughput threads blocked until (one) tx timeouts lockacquisitiontimeout defaults to 10 seconds! a,b are locked during this time -> potentially more deadlocks

10 What s to be done? Order key e.g. lexicographically Tx1: a -> b Tx2: a -> b not always possible Use deadlock detection fail fast one tx succeeds

11 Dld can make wonders!

12 At low cost!

13 Peer To Peer Architecture

14 Client/Server Architecture Supported Protocols REST Memcached Hot Rod

15 Hotrod?! Wire protocol for client server communications Open Language independent Built-in failover and load balancing Smart routing

16 Server Endpoint Comparison Protocol Client Libraries Clustered? Smart Routing Load Balancing/ Failover REST Text N/A Yes No Any HTTP load balancer Memcached Text Plenty Yes No Only with predefined server list Hot Rod Binary Currently only Java Yes Yes Dynamic

17 Client/Server - when? Client not affected by server topology changes Multiple apps share the same grid Tier management incompatible JVM tuning security Non-JVM clients

18 Querying and indexing Querying based Lucene and Hibernate Search tech preview 4.1 functional 5.0 API (5.0)

19 Local indexes

20 Shared indexes

21 Consistency and topology changes E.g. node leaves what happens with ongoing transactions? are reads consistent? Ongoing transactions only some tx are affected (dist) transparent failover Infinispan is strong consistent! eventual consistency might be added...

22 Distribution Based on consistent hash horizontal scalability pluggable hash function Topology aware consistent hash since improved consistency Virtual Nodes it s all about performance! added in 5.0

23 Topology aware consistent hash Each node aware about cluster topology Machine, rack, site Distribute backups as far as possible other site, rack, machine Collocated nodes higher chance to fail together cheaper access

24 Topology aware consistent hash - configuration Each node statically configured Used for inter-site replication go to Bela s the summit!

25 Consistent Hash distribution uneven load on cluster nodes bad for performance!

26 Virtual nodes Physical node = multiple virtual nodes configurable per node Solve the problem of uneven distribution even for small clusters More powerful nodes can take more load configure more virtual nodes

27 Questions? #infinispan #judcon irc #infinispan on FreeNode

28 More at the summit... Highly Scalable Data Grids and Distributed Caching with Infinispan (Manik Surtani) Infinispan Optimizing Performance & Consistency at the Chicago Board Options Exchange (Shane Johnson, Craig Bomba) JPA on Infinispan: When PaaS Persistence Meets Java EE (Emmanuel Bernard, Sanne Grinovero)