The following is a complete listing of fixes for V8.0 with the most recent fix at the top.
This comprehensive document will guide you through every last detail of Infinispan.
Using Infinispan is better than using a simple Concurrent Hash Map, since it has additional useful features such as expiration and eviction.
If you want to be able to scale your caching layer independently from your application, or you need to make your data available to different applications, possibly even using different languages / platforms, use Infinispan Server and its various clients.
To protect existing HBase installations from new vulnerabilities, please do not use JIRA to report security-related bugs.
Instead, send your report to the mailing list [email protected], which allows anyone to send messages, but restricts who can read them.
Infinispan is a distributed in-memory key/value data store with optional schema, available under the Apache License 2.0.
The primary use for Infinispan is to provide a fast in-memory cache of frequently accessed data.
Suppose you have a slow data source (database, web service, text file, etc): you could load some or all of that data in memory so that it’s just a memory access away from your code.
First off, distributed systems are hard; making a distributed system hum requires a disparate skillset that spans systems (hardware and software) and networking.
Your cluster’s operation can hiccup because of any of a myriad set of reasons from bugs in HBase itself through misconfigurations — misconfiguration of HBase but also operating system misconfigurations — through to hardware problems whether it be a bug in your network card drivers or an underprovisioned RAM bus (to mention two recent examples of hardware issues that manifested as "HBase is slow").