On Tue, Nov 25, 2014 at 6:40 AM, Ankit Patel <ankit7...@gmail.com> wrote:

> The JIRA https://issues.apache.org/jira/browse/CASSANDRA-4446 refers to
> the problem after we've invoked drain. However, we did not invoke drain or
> flush. We are running one node cassandra within one data center and it is
> being replicated with another node in another data center. We are using the
> thrift API in java application to retrieve and modify the data from the
> primary node only. We are not using the other node in the other data center
> for any operations. The data loss well exceeds the commit log sync period.
>

Right, what I meant by "the era of CASSANDRA-4446" is that around that time
there were reports of weird behavior around the commit log. Not your
particular weird behavior, but similar enough that I am not *overly*
surprised to hear it. Unfortunately no one is likely to want to fix your by
now quite old version, especially as a re-write of the commit log occurred
in (IIRC) 1.1.x series.

I recommend upgrading at least to the HEAD of 1.1.x ASAP.

=Rob
PS - I understand and sympathize, the above is not a terribly satisfying
answer in the face of data loss. :/

Reply via email to