search

xichen2020 / eventdb

Storage for discrete events such as log events or tracing events
Apache License 2.0
9 stars 1 forks source link

Data unavailable for in-memory segment error #108

Closed notbdu closed 5 years ago

notbdu commented 5 years ago

Seeing this error in the logingester query logs: 

21:01:44.548013[W] error executing query: received HTTP status: 500 Internal Server Error. body: {"state":"Error","error":"error performing grouped query {rtapi 1549486904543668347 1549573304543668347 [] [[@timestamp]] [{[] COUNT}] [] 10 0x874db0 map[12889413958949747480:{[@timestamp] map[1:map[double:{} string:{} time:{} null:{} bool:{} int:{}] 0:map[time:{}]]}]} against database namespace rtapi: data unavaible for in-memory only segment"

Judging from the comment below, this should not happen. Dig into this.

if dataLocation == inMemoryOnly {
        // We have fields that are in the in-memory metadata hash, and the actual data
        // is not in memory, and yet the location indicates all data are in memory. This
        // is a logical error and should never happen.
        cleanup()
        return nil, errDataNotAvailableInInMemoryOnlySegment
}
notbdu commented 5 years ago

After some digging, this is related to #107.

notbdu commented 5 years ago

Attempting to write a reproducible functional test case for both.

notbdu commented 5 years ago

Have working functional test case that repros the problem. Attempting to fix.