key not found: com.twitter.querulous.query.QueryClass #43

Open
cowboyrushforth opened this Issue Mar 17, 2011 · 4 comments

4 participants

@cowboyrushforth

Hello,
Having some trouble getting flock going here on a mac. Using osx 10.6. Thrift 0.5.0, sbt 0.7.4.

Everything goes ok, including the tests that sbt runs (says all 239 pass), until I actually try to write to it. Selecting from it seems to work ok, although it never returns anything since writing always fails. Using the latest ruby client via irb. Running:

flockdb = Flock.new 'localhost:7915, :graphs => { :follows => 1, :blocks => 2 }
flockdb.add(1, :follows, 2)

produces in flocks' development.log:

INF [20110317-00:07:48.042] w3c: - - - 1300345668041 1 - - - - - - - - - - - - - - - - - - - - - - - FlockDB:execute ExecuteOperations(operations:[ExecuteOperation(operation_type:Add,_term:QueryTerm(source_id:1,_graph_id:1,_is_forward:true,_destination_ids:02_00_00_00_00_00_00_00))],_priority:High)
ERR [20110317-00:07:48.053] scheduler: Error in Job: )> - scala.MatchError: scala.MatchError: scala.MatchError: java.util.NoSuchElementException: key not found: com.twitter.querulous.query.QueryClass@6167436c
ERR [20110317-00:07:48.053] scheduler: scala.MatchError: scala.MatchError: scala.MatchError: java.util.NoSuchElementException: key not found: com.twitter.querulous.query.QueryClass@6167436c
ERR [20110317-00:07:48.053] scheduler:     at com.twitter.gizzard.proxy.SqlExceptionWrappingProxyFactory$$anonfun$$init$$2.apply(SqlExceptionWrappingProxy.scala:33)
ERR [20110317-00:07:48.053] scheduler:     at com.twitter.gizzard.proxy.SqlExceptionWrappingProxyFactory$$anonfun$$init$$2.apply(SqlExceptionWrappingProxy.scala:31)
ERR [20110317-00:07:48.053] scheduler:     at com.twitter.gizzard.proxy.ExceptionHandlingProxyFactory$$anonfun$apply$2.apply(ExceptionHandlingProxy.scala:53)
ERR [20110317-00:07:48.053] scheduler:     at com.twitter.gizzard.proxy.ExceptionHandlingProxyFactory$$anonfun$apply$2.apply(ExceptionHandlingProxy.scala:47)
ERR [20110317-00:07:48.053] scheduler:     at com.twitter.gizzard.proxy.ProxyFactory$$anon$3.invoke(Proxy.scala:93)
ERR [20110317-00:07:48.053] scheduler:     at $Proxy7.optimistically(Unknown Source)
ERR [20110317-00:07:48.053] scheduler:     at com.twitter.flockdb.jobs.single.Single.apply(Single.scala:81)
ERR [20110317-00:07:48.053] scheduler:     at com.twitter.gizzard.scheduler.NestedJob.apply(NestedJob.scala:19)
ERR [20110317-00:07:48.053] scheduler:     at com.twitter.gizzard.scheduler.NestedJob.apply(NestedJob.scala:19)
ERR [20110317-00:07:48.053] scheduler:     at com.twitter.gizzard.scheduler.ReplicatingJob.apply(ReplicatingJob.scala:85)
ERR [20110317-00:07:48.053] scheduler:     at com.twitter.gizzard.scheduler.JobScheduler$$anonfun$process$1.apply(JobScheduler.scala:147)
ERR [20110317-00:07:48.053] scheduler:     at com.twitter.gizzard.scheduler.JobScheduler$$anonfun$process$1.apply(JobScheduler.scala:142)
ERR [20110317-00:07:48.053] scheduler:     at scala.Option.foreach(Option.scala:185)
ERR [20110317-00:07:48.053] scheduler:     at com.twitter.gizzard.scheduler.JobScheduler.process(JobScheduler.scala:142)
ERR [20110317-00:07:48.053] scheduler:     at com.twitter.gizzard.scheduler.JobScheduler.processWork(JobScheduler.scala:138)
ERR [20110317-00:07:48.053] scheduler:     at com.twitter.gizzard.scheduler.JobScheduler$$anon$1.runLoop(JobScheduler.scala:131)
ERR [20110317-00:07:48.053] scheduler:     at com.twitter.ostrich.BackgroundProcess.run(BackgroundProcess.scala:81)

I have tried older versions of flock, went all the way back to the 1.6.3 tag, and did a fresh sbt update / package-dist. each time after getting it up was stuck in same place with similar error as above.

Also for the heck of it tried using thrift to re-generate the gen-rb files in the ruby client to make sure its current with the FlockDB.thrift file, but also same results.

Searched around a bit but can not seem to find any clues. Any tips would be great! Thanks!

@plockaby

I'm also having this exact same error. Did anyone solve this?

@plockaby

Anyone?

@tmountain

Same issue here as well using Ubuntu 10.04.

@ksauzz

The patch is this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment