voldemort.store.InvalidMetadataException

Client accessing key belonging to partitions [31] not present at Node server-096p3 Id:6 in zone 0 partitionList:[43, 7, 14, 42]

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web17

  • via Google Groups by Miguel Ausó, 6 months ago
    Client accessing key belonging to partitions [31] not present at Node server-096p3 Id:6 in zone 0 partitionList:[43, 7, 14, 42]
  • Client accessing key belonging to partitions [31] not present at Node server-096p3 Id:6 in zone 0 partitionList:[43, 7, 14, 42]
  • client attempt accessing key belonging to partition:[3, 4] at Node:Node0 partitionList:[0, 1]
  • Stack trace

    • voldemort.store.InvalidMetadataException: Client accessing key belonging to partitions [31] not present at Node server-096p3 Id:6 in zone 0 partitionList:[43, 7, 14, 42] at sun.reflect.GeneratedConstructorAccessor2.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at voldemort.utils.ReflectUtils.callConstructor(ReflectUtils.java:116) at voldemort.utils.ReflectUtils.callConstructor(ReflectUtils.java:103) at voldemort.store.ErrorCodeMapper.getError(ErrorCodeMapper.java:76) at voldemort.client.protocol.vold.VoldemortNativeClientRequestFormat.checkException(VoldemortNativeClientRequestFormat.java:298) at voldemort.client.protocol.vold.VoldemortNativeClientRequestFormat.readGetResponse(VoldemortNativeClientRequestFormat.java:114) at voldemort.store.socket.clientrequest.GetClientRequest.parseResponseInternal(GetClientRequest.java:63) at voldemort.store.socket.clientrequest.GetClientRequest.parseResponseInternal(GetClientRequest.java:31) at voldemort.store.socket.clientrequest.AbstractClientRequest.parseResponse(AbstractClientRequest.java:74) at voldemort.store.socket.clientrequest.BlockingClientRequest.parseResponse(BlockingClientRequest.java:74) at voldemort.store.socket.clientrequest.ClientRequestExecutor.read(ClientRequestExecutor.java:248) at voldemort.common.nio.SelectorManagerWorker.run(SelectorManagerWorker.java:105) at voldemort.common.nio.SelectorManager.run(SelectorManager.java:214) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.