Great, that worked, thanks for your time.
On Thu, Mar 10, 2011 at 4:57 PM, Jonathan Ellis wrote:
> Drop the index, then restart once more. It shouldn't try to rebuild
> the index after that.
>
> On Thu, Mar 10, 2011 at 3:36 PM, Matt Kennedy
> wrote:
> > Sorry, I wasn't clear on the timeline of
Drop the index, then restart once more. It shouldn't try to rebuild
the index after that.
On Thu, Mar 10, 2011 at 3:36 PM, Matt Kennedy wrote:
> Sorry, I wasn't clear on the timeline of events. I started the index build
> and then posted this message to the list. Once I read the links you poste
Sorry, I wasn't clear on the timeline of events. I started the index build
and then posted this message to the list. Once I read the links you posted,
I did expect the cluster to crash, but I let it run until it blew up anyway,
since I didn't really know how to stop the index build.
Which is sort
If you read the bugs I linked, you would see that this is expected
behavior with 0.7.3 once you get more data than you can index
in-memory.
You should wait for the next Hudson build (which will include 2295)
and use that. Or, create your indexes before adding the data.
On Thu, Mar 10, 2011 at 12
Well it looks like the index creation job crashed the cluster. All of the
nodes were down having dumped out .hprof files. I brought the cluster back
up and when I do "describe keyspace ks" it looks like the index build
process has started over again. Is it safe to attempt to stop that by
running
