Query does not respond

bug

(Ted) #1

Hi there!

We have a pretty simple table called challenges which just has a few basic columns on it. When we run select * from challenges, crdb just hangs and the query is stuck in executing. When I run select * from challenges where id = 1, it executes immediately. If i run select * from challenges where id = 1 or id = 2 it hangs again. We are currently running v2.1.3 with 3 nodes if that is at all helpful.

Let me know if I can give any other info.

Thanks!

Ted


(Ted) #2

Quick update:

Each of the nodes were originally at 2g of memory usage. After restarting all of them it appears the query works again.


(Tim O'Brien) #3

Hey @tzilist,

It’s not surprising on its own that select * would stop queries - you’re going to have to touch every range in the table. I don’t know offhand why adding an or clause would make a query hang on its own.

If you’re still running into trouble, it’d be helpful to see the schema and EXPLAIN statements for both the filtered queries. How large is the table in question?