Yeah, I'd guess that this is a Hive issue, although it could be a combination.. maybe if you're doing queries and then closing your thrift connection before reading all results, Hive doesn't know what to do and leaves the connection open? Once the west coast folks wake up, they might have a better answer for you than I do.
On Mon, Jan 25, 2010 at 9:06 AM, Andy Kent <[email protected]> wrote: > On 25 Jan 2010, at 13:59, Jay Booth wrote: > > > That's the datanode port.. if I had to guess, Hive's connecting to DFS > directly for some reason (maybe for "select *" queries?) and not finishing > their reads or closing the connections after. > > > Thanks for the response. > > That's what I was suspecting. I have triple checked and our Ruby code and > it is defiantly closing it's thrift connections properly. > > I'll try running some different queries and see if I can suss out some > examples of which ones are leaky. Is this something that I should post to > Jira or is it a known issue? I can't believe other people haven't noticed > this?
