Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/7889#issuecomment-131287504
> @zsxwing hive had a configuration named
hive.server2.thrift.max.worker.threads which had already limit the concurrence.
> But my problem was not caused by trimSessionIfNecessary.
If so, could you help verify if #8185 fixes this issue?
I think the client won't send the `ExecuteStatement` request before
receiving the `OpenSession` response, so `onStatementStart` should happen after
`onSessionCreated` strictly.
`HiveThriftServer2Listener` was not thread-safe previously so that it's
status (such as, mutable.HashMap) could be corrupt due to concurrent requests,
which is a possible cause of this issue.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
