Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Questions on the proper method(s) to clean up a HBase-backed Titan graph #1387

Open
CPorrot opened this issue Dec 4, 2017 · 0 comments
Open

Comments

@CPorrot
Copy link

CPorrot commented Dec 4, 2017

Hello.

I am working on a big data project using a Titan 1.0 graph backed by a HBase table. We are currently in the testing phase, and when we need to empty our graph for testing purposes, we use a groovy script which closes the graph, then executes the TitanCleanup.clear() method in order to empty the graph. However, due to the high number of elements in the graph (up to ~800k vertices after our performance tests), this script takes a large amount of time, which we would like to shorten as much as possible for the testers.

We found an alternative method, which is dropping and re-creating the titan table in Hbase, but we would like to avoid it if possible, as we do not know if this could cause issues, such as lingering locks.

  • Do direct actions on the HBase table, such as truncating or dropping/creating the table, present a risk for the stability of the graph database?
  • Are there valid alternatives, or steps to optimize the execution of the TitanCleanup.clear() method?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant