maybe print out value into the logfile and that should lead to some clue where it might be the problem?
On Tue, May 7, 2019 at 4:58 PM Paul Chandler <p...@redshots.com> wrote: > > Roy, We spent along time trying to fix it, but didn’t find a solution, it was > a test cluster, so we ended up rebuilding the cluster, rather than spending > anymore time trying to fix the corruption. We have worked out what had caused > it, so were happy it wasn’t going to occur in production. Sorry that is not > much help, but I am not even sure it is the same issue you have. > > Paul > > > > On 7 May 2019, at 07:14, Roy Burstein <burstein....@gmail.com> wrote: > > I can say that it happens now as well ,currently no node has been > added/removed . > Corrupted sstables are usually the index files and in some machines the > sstable even does not exist on the filesystem. > On one machine I was able to dump the sstable to dump file without any issue > . Any idea how to tackle this issue ? > > > On Tue, May 7, 2019 at 12:32 AM Paul Chandler <p...@redshots.com> wrote: >> >> Roy, >> >> I have seen this exception before when a column had been dropped then re >> added with the same name but a different type. In particular we dropped a >> column and re created it as static, then had this exception from the old >> sstables created prior to the ddl change. >> >> Not sure if this applies in your case. >> >> Thanks >> >> Paul >> >> On 6 May 2019, at 21:52, Nitan Kainth <nitankai...@gmail.com> wrote: >> >> can Disk have bad sectors? fccheck or something similar can help. >> >> Long shot: repair or any other operation conflicting. Would leave that to >> others. >> >> On Mon, May 6, 2019 at 3:50 PM Roy Burstein <burstein....@gmail.com> wrote: >>> >>> It happens on the same column families and they have the same ddl (as >>> already posted) . I did not check it after cleanup >>> . >>> >>> On Mon, May 6, 2019, 23:43 Nitan Kainth <nitankai...@gmail.com> wrote: >>>> >>>> This is strange, never saw this. does it happen to same column family? >>>> >>>> Does it happen after cleanup? >>>> >>>> On Mon, May 6, 2019 at 3:41 PM Roy Burstein <burstein....@gmail.com> wrote: >>>>> >>>>> Yes. >>>>> >>>>> On Mon, May 6, 2019, 23:23 Nitan Kainth <nitankai...@gmail.com> wrote: >>>>>> >>>>>> Roy, >>>>>> >>>>>> You mean all nodes show corruption when you add a node to cluster?? >>>>>> >>>>>> >>>>>> Regards, >>>>>> Nitan >>>>>> Cell: 510 449 9629 >>>>>> >>>>>> On May 6, 2019, at 2:48 PM, Roy Burstein <burstein....@gmail.com> wrote: >>>>>> >>>>>> It happened on all the servers in the cluster every time I have added >>>>>> node >>>>>> . >>>>>> This is new cluster nothing was upgraded here , we have a similar cluster >>>>>> running on C* 2.1.15 with no issues . >>>>>> We are aware to the scrub utility just it reproduce every time we added >>>>>> node to the cluster . >>>>>> >>>>>> We have many tables there >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org For additional commands, e-mail: user-h...@cassandra.apache.org
