Hi Jonathan, We too have exactly this issue as of a couple of days ago.
This is in 1.7.2, zookeeper 3.4.5 and from a cluster that has been shut down for a long time. Accumulo writes the root_tablet/lastlocation node with the name of the tserver, concatenated with the ephemeral owner form zookeeper. For us, this hex value is now a negative 64-bit long which parseLong throws an exception on. Note that parseUnsignedLong would have work. Also, note that, at least, in Accumulo 2.0, the code to do the same was changed to parse strings, not longs, avoiding the whole issue. Is there not some way/hack to reset the session id to something reasonable somewhere in zookeeper? Regards, On Fri, Apr 22, 2022 at 12:30 PM Wonders, Jonathan (Serco NA) < jonathan.wond...@serco-na.com> wrote: > Serco Business > > Greetings, > > > > The team I work with is encountering an issue when starting an Accumulo > 1.7.x cluster and when running troubleshooting commands such as > bin/accumulo admin checkTablets. The primary symptom is a > NumberFormatException thrown within ZookeeperLockChecker that occurs when > parsing the tablet server session id (Long.parseLong) for an input string > “ff804d767efe0004” (which is out of range when interpreting as a positive > signed long). > > > > From what I can gather, our zookeeper cluster has been running for such a > long time that the epoch component of the session id has grown to the point > where interpreting the session id as a signed long would be a negative > value. Within the ZooKeeper code, the session id is treated as an unsigned > long (e.g., Long.toHexString) which leads me to think that the Accumulo > code is not parsing the value correctly. This discrepancy is present in all > versions since the introduction of the ZookeeperLockChecker class. > > > > There does not appear to be an easy way to work around this problem. > Currently, our best idea of how to recover the data from this cluster is to > set up a separate zookeeper cluster, migrate the data we have in zookeeper > to the new cluster, and then swap over configuration to point to the new > zookeeper cluster. I would appreciate any ideas or suggestions from the > community. > > > > Thanks, > > Jonathan > > > > > > > > > -- Josef Roehrl Professional Services Solutions Architect *I recognize that my working hours may not be the same as yours.Please feel free to respond only during your working hours.Has it really been 45+ years programming?So little time. So much to learn and do.* *PHEMI Systems* 777 Hornby Street, Suite 600 Vancouver, BC V6Z 1S4 604-336-1119 Website <http://www.phemi.com/> Twitter <https://twitter.com/PHEMISystems> Linkedin <http://www.linkedin.com/company/3561810?trk=tyah&trkInfo=tarId%3A1403279580554%2Ctas%3Aphemi%20hea%2Cidx%3A1-1-1>
