When thresholds are reached, that Memtable is flushed to a disk in a format called SSTable. Cassandra write operations are occurred on a commit log on disk and then to an in-memory table structure called Memtable. But before changing commit log destination it would be better to know it gives performance boost. So if you find something is not working or facing any issues, please do not hesitate to contact me :)ĭedicated Commit Log Disk: I think this is the first tune-up you may want to try as it gives you a significant performance improvement. Note: For privacy purpose, I had to modify several lines on this post from my original post. Once its working for you, you can try other options (highly encouraged) and see how it works for you. That's pretty much it! This is the very basic AWS Load Balancer example with minimum configuration of Tomcat + Session Stickiness. So wait few minutes until you see "Status: N of N instances in service". It takes some time and it waits for the result of the next health check. Remember, "Status" section under "Description" tab of your load balancer does not get updated instantly. If you find that each of the instance is up and running, you can try removing them from your load balancer and add them again. In that case, best way to quickly test is to check each of the instance where tomcat is running and check whether you can access them individually (e.g. Some considerations: Sometimes you might see your load balancer is down or the link is not working or shows no page. For my case, now I'm able to successfully authenticate to my application. After you enable it, you should be able to test your session stickiness.
0 kommentar(er)
