Re: How to persist data on system reboot

Jerry He <jerr...@...>

Good to know.

Manual flush on the table should not be required.
HBase keeps recent writes in memory. But they have been written to WAL logs as well.  When you reboot your system without properly shuts down HBase, HBase will start recover from the WAL after restart.
It may not work on the AWS instance for S3 for apparent reason.



On Tuesday, March 28, 2017 at 7:23:19 AM UTC-7, pikachu wrote:
It seems hbase automatically flushes to disk based on the flush interval and memstore size limit configuration. So Its not a problem. Everything working fine now.


On Tuesday, March 28, 2017 at 10:43:22 AM UTC+5:30, pikachu wrote:
Hi Jerry

Thanks for helping me out. 
When I manually run 'flush' on the table on the hbase shell, The data persists after system reboot in my local machine. Is there any command to flush the table in gremlin? 

Thanks again

On Tuesday, March 28, 2017 at 9:49:52 AM UTC+5:30, Jerry He wrote:
I am not sure what storage model you use for HBase on AWS.
There is a section 'Shutting Down and Restoring a Cluster Without Data Loss'.
Basically you want to flush the hbase table before you shut down the cluster.  This is specific to this storage model for HBase on AWS.
I don't see why it happens on your local machine. The above step is not really needed on a local machine.
Try bringing up the 'hbase shell' to see if the data is persisted by running a 'scan' or 'count' on the janusgraph table.  Run a 'flush' on the table.  Then see if it endures a reboot on you local machine.



On Monday, March 27, 2017 at 8:26:03 PM UTC-7, pikachu wrote:
Yes I am able to run all operations successfully. I tried on on both AWS server and my local machine. AWS server stores hbase data in s3, and I configured the local machine to point to a directory in /home.  
Is there anything I missed to persist data after reboots?

g.V() always returns empty after reboot

Join to automatically receive all group messages.