ctubbsii commented on issue #2362: URL: https://github.com/apache/accumulo/issues/2362#issuecomment-1034197306
> I was running a test with a slightly older version of 2.1.0-SNAPSHOT w/o #2442 changes. A tablet ran into the following error when trying to split and it left the tablet in a really bad state. I think this is a different manifestation of this bug and I am hoping that pulling in #2442 will fix my problem. @ctubbsii curious if you think this is the same bug and your changes in #2442 will avoid the problem? If your not sure, don't worry about it I will be spinning up a new test w/ latest code. > > ``` > 2022-02-09T18:40:20,070 [tserver.TabletServer] ERROR: Unknown error on split: > java.lang.IllegalArgumentException: Unknown runnable type io.opentelemetry.context.Context$$Lambda$376/0x0000000840441040 > at org.apache.accumulo.tserver.compactions.InternalCompactionExecutor$InternalJob.lambda$cancel$0(InternalCompactionExecutor.java:134) ~[accumulo-tserver-2.1.0-SNAPSHOT.jar:2.1.0-SNAPSHOT] > at java.util.concurrent.PriorityBlockingQueue.bulkRemove(PriorityBlockingQueue.java:1064) ~[?:?] > at java.util.concurrent.PriorityBlockingQueue.removeIf(PriorityBlockingQueue.java:1024) ~[?:?] > ``` I'm not 100% certain, but I do believe it is another manifestation that was fixed in #2442 . Specifically, note the changes around the `removeIf`. I remember that the problem wasn't just with the comparators unwrapping things, but also any time we tried to directly manipulate the blocking queues and we expected a type any more specific than "Runnable". -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
