???????????? rebuild in the new DC always failed

2017-12-16 Thread Peng Xiao
pache.org> : ???? rebuild in the new DC always failed That NPE in gossip is probably a missing endpointstate, which is probably fixed by the gossip patch (#13700) in 2.1.19 I??m not sure it??s related to the rebuild failing - I??m not actually sure if that??s a server failure or jmx timing

Re: 回复: rebuild in the new DC always failed

2017-12-16 Thread Jeff Jirsa
1c0355a.jpg> > > Thanks > -- 原始邮件 -- > 发件人: "Jeff Jirsa";<jji...@gmail.com>; > 发送时间: 2017年12月17日(星期天) 上午8:13 > 收件人: "user"<user@cassandra.apache.org>; > 主题: Re: rebuild in the new DC always failed > > What’s the rest of th

?????? rebuild in the new DC always failed

2017-12-16 Thread Peng Xiao
Hi Jeff, This is the only informaiton we found from system.log Thanks -- -- ??: "Jeff Jirsa";<jji...@gmail.com>; : 2017??12??17??(??) 8:13 ??: "user"<user@cassandra.apache.org>; : Re: reb

Re: rebuild in the new DC always failed

2017-12-16 Thread Jeff Jirsa
What’s the rest of the stack beneath the null pointer exception? -- Jeff Jirsa > On Dec 16, 2017, at 4:11 PM, Peng Xiao <2535...@qq.com> wrote: > > Hi there, > > We need to rebuild a new DC,but the stream is always failed with the > following errors. > we are using C* 2.1.18.Could anyone

rebuild in the new DC always failed

2017-12-16 Thread Peng Xiao
Hi there, We need to rebuild a new DC,but the stream is always failed with the following errors. we are using C* 2.1.18.Could anyone please advise? error: null -- StackTrace -- java.io.EOFException at java.io.DataInputStream.readByte(DataInputStream.java:267) at