You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Romain Hardouin <ro...@yahoo.fr> on 2016/02/01 15:21:47 UTC
Re: missing rows while importing data using sstable loader
Did you run "nodetool flush" on the source node? If not, the missing rows could be in memtables.
Re: missing rows while importing data using sstable loader
Posted by Jack Krupansky <ja...@gmail.com>.
I sent a message to DataStax Docs to add this nodetool flush suggestion to
the doc for sstableloader.
-- Jack Krupansky
On Fri, Feb 5, 2016 at 3:35 AM, Romain Hardouin <ro...@yahoo.fr> wrote:
> > What is the best practise to create sstables?
>
> When you run a "nodetool flush" Cassandra persists all the memtables on
> disk, i.e. it produces sstables.
> (You can create sstables by yourself thanks to CQLSSTableWriter, but I
> don't think it was the point of your question.)
>
Re: missing rows while importing data using sstable loader
Posted by Romain Hardouin <ro...@yahoo.fr>.
> What is the best practise to create sstables?
When you run a "nodetool flush" Cassandra persists all the memtables on disk, i.e. it produces sstables.
(You can create sstables by yourself thanks to CQLSSTableWriter, but I don't think it was the point of your question.)
Re: missing rows while importing data using sstable loader
Posted by Arindam Choudhury <ar...@ackstorm.com>.
What is the best practise to create sstables?
On 1 February 2016 at 15:21, Romain Hardouin <ro...@yahoo.fr> wrote:
> Did you run "nodetool flush" on the source node? If not, the missing rows
> could be in memtables.
>