cassandra - Terminating sstableloader while waiting for secondary index build to complete -


After the above, it is safe to end the sstableloader process (SIGINT, etc.) while waiting for it to build secondary index Is doing it? That is, after the creation of the secondary index does the equipment perform any other important action? If I do not allow the device to come out of the self, then can the import be brought back?

If it is safe to end the sstableloader process, then has not created the secondary index of the previous example yet?

Finally, is there a way to make the index asynchronous so that the device will not wait to finish it before it ends?

EDIT:

If this is not safe to terminate the sstableloader process, can I at least stop the index creation process through 'Nodeset off INDEX_BUILD' Am I Will it cause the sstableloader to exit properly? Will the revised index be retried automatically in the background?

There will be no bad effect of the SSBLodder, by eliminating it, you can do it without worrying about data corruption Bar can run on the same set of SSTables.

The follow up on the SSTable index build is automatically in the background, you can increase the number of concurrent compaction threads. Multiple indexes can be created simultaneously.

Buildings take time to index and often take more time than ingest, but the data will be available for reading and writing.

If you manually index_build, I'm not sure that this will cause the SSTableLoader to exit (because I have never done this), but then you can use the cascand to re-create the index using the encoded Will be required.

Comments

Popular posts from this blog

Pass DB Connection parameters to a Kettle a.k.a PDI table Input step dynamically from Excel -

multithreading - PhantomJS-Node in a for Loop -

c++ - MATLAB .m file to .mex file using Matlab Compiler -