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 > <mailto: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 > <mailto: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 > <mailto:burstein....@gmail.com>> wrote: > Yes. > > On Mon, May 6, 2019, 23:23 Nitan Kainth <nitankai...@gmail.com > <mailto:nitankai...@gmail.com>> wrote: > Roy, > > You mean all nodes show corruption when you add a node to cluster?? > > > Regards, > Nitan > Cell: 510 449 9629 <tel:510%20449%209629> > > On May 6, 2019, at 2:48 PM, Roy Burstein <burstein....@gmail.com > <mailto: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
