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.
----- -- 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.
