progress: 361% does not look right (probably a bug). Can you check the corresponding messages on the other side of the stream? I.E. the system log for 192.168.10.8 around 18:02:06?
All the best, [image: datastax_logo.png] <http://www.datastax.com/> Sebastián Estévez Solutions Architect | 954 905 8615 | sebastian.este...@datastax.com [image: linkedin.png] <https://www.linkedin.com/company/datastax> [image: facebook.png] <https://www.facebook.com/datastax> [image: twitter.png] <https://twitter.com/datastax> [image: g+.png] <https://plus.google.com/+Datastax/about> <http://feeds.feedburner.com/datastax> <http://goog_410786983> <http://www.datastax.com/gartner-magic-quadrant-odbms> DataStax is the fastest, most scalable distributed database technology, delivering Apache Cassandra to the world’s most innovative enterprises. Datastax is built to be agile, always-on, and predictably scalable to any size. With more than 500 customers in 45 countries, DataStax is the database technology and transactional backbone of choice for the worlds most innovative companies such as Netflix, Adobe, Intuit, and eBay. On Sat, Feb 27, 2016 at 6:12 PM, Jason Kania <jason.ka...@ymail.com> wrote: > Hello, > > I am trying to get a node bootstrapped in 3.0.3, but just at the point > where the bootstrap process is to complete, a broken pipe exception occurs > so the bootstrap process hangs. Once I kill the bootstrap process, I can > execute "nodetool bootstrap resume" again and the same problem will occur > just at the end of the bootstrap exercise. Here is the tail of the log: > > [2016-02-27 18:02:05,898] received file > /home/cassandra/data/sensordb/listedAttributes-79256340bbbb11e59f707d76a8de8480/ma-30-big-Data.db > (progress: 357%) > [2016-02-27 18:02:06,479] received file > /home/cassandra/data/sensordb/notification-f7e3eaa0024b11e5bb310d2316086bf7/ma-38-big-Data.db > (progress: 361%) > [2016-02-27 18:02:06,884] session with /192.168.10.8 complete (progress: > 361%) > [2016-02-27 18:02:06,886] Stream failed > > I attempted to run nodetool repair, but get the following which I have > been told indicates that the replication factor is 1: > > root@bull:~# nodetool repair > [2016-02-27 18:04:55,083] Nothing to repair for keyspace 'sensordb' > > Thanks, > > Jason >
