Jeff N wrote:
It was part of a manual repair. We had a namenode crash and recovery failed. The process of moving the hdfs data out and importing into another table left the original table in a weird state. The recovery data had 0B and was throwing EOF exceptions.
EOF on WALs with no data was something that we changed in "recent" versions (maybe 1.6.2 and 1.7.0?). We should skip over a WAL with no data in it. That might help your situation should you ever be so unfortunate to run into it again.
----- -- View this message in context: http://apache-accumulo.1065345.n5.nabble.com/Weird-table-state-tp14279p14281.html Sent from the Developers mailing list archive at Nabble.com.
