You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@impala.apache.org by "Montoya Blanco, A." <a....@accenture.com> on 2018/04/04 07:26:38 UTC
RE: [External] Re: errorMessage:Client session expired due
Hi,
Thanx for your response.
Its true that the configure set 3600 sec in idle_session_timeout because we don’t want consume Kluster resources.
I have a web application, and it is possible exist periods of inactivity. So, in the night, its possible more time.
So, how can i solve this issue?
I suppose that idle_session_timeout with 0 value maybe consume a lot of resources ... its true? Is it bad practice?
There are any form to remove this inactive sessions with Java client? I close my client connections when I finish a query....
If it is not possible,I have more questions...
Who is open this session? Is impala or is a client?
Is not there pool connection in Impala?
Do I need create a new connection every time communicate with BD?
Thanks in advance.
Un saludo.
Alejandro Montoya Blanco
Accenture Technology
a.montoya.blanco@accenture.com
-----Original Message-----
From: Matthew Jacobs [mailto:jacobs.mh@gmail.com]
Sent: martes, 3 de abril de 2018 18:21
To: user@impala.apache.org
Subject: [External] Re: errorMessage:Client session expired due
Hi Montoya,
This is likely due to the "idle_session_timeout" being set to 3600sec.
Can you check the coordinator web UI to get the configured "idle_session_timeout"?
https://urldefense.proofpoint.com/v2/url?u=http-3A__IMPALA-5FCOORDINATOR-5FHOST-3A25000_varz&d=DwIBaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=_tBrUBmJdo4LhYOf5xwULMsNDhup4vUMmd09TUTRlhM&m=XWbZ06Bre5x6j1-NnIzPBq09_mzYXToTGsn3RBXy3k0&s=5K9ZNZnEa-H5FKgaaL3GRrGlxh3k2Gc5R_AkzTCCu8g&e=
See this doc for more information on the configurable timeouts:
https://urldefense.proofpoint.com/v2/url?u=https-3A__impala.apache.org_docs_build_html_topics_impala-5Ftimeouts.html&d=DwIBaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=_tBrUBmJdo4LhYOf5xwULMsNDhup4vUMmd09TUTRlhM&m=XWbZ06Bre5x6j1-NnIzPBq09_mzYXToTGsn3RBXy3k0&s=2mE9_x6DU2zTkUx8iev3AcnoUMoEgJvKjUu4uZkGw-w&e=
Best,
Matt
On Tue, Apr 3, 2018 at 6:57 AM, Montoya Blanco, A.
<a....@accenture.com> wrote:
> Hi,
>
>
>
> I get this error:
>
>
>
> Caused by: java.sql.SQLException: [Simba][ImpalaJDBCDriver](500051)
> ERROR processing query/statement. Error Code: 0, SQL state:
> TStatus(statusCode:ERROR_STATUS, sqlState:HY000, errorMessage:Client
> session expired due to more than 3600s of inactivity .
>
>
>
> I use JDBC Spring Autoconfigure, and Spring must close the connections
> automaticatly , and i believe not is the problem because there are
> same bugs with manually close connection :
> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_IMPALA-2D1905&d=DwIBaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=_tBrUBmJdo4LhYOf5xwULMsNDhup4vUMmd09TUTRlhM&m=XWbZ06Bre5x6j1-NnIzPBq09_mzYXToTGsn3RBXy3k0&s=7G7jm5L2u9PaMDt_VC7NUFFrTT3jhYZzgotk54numLA&e=.
>
>
>
> I supose this error is cause because there are sessions inactive
> opens, so, Are there any form to close session Impala with JDBC java?
>
>
>
> it seems the bug has been fixed in Impala 2.0+, but I use driver
> impala
> 2.5.38.1 to connect Impala 2.10.0-cdh5.13.1
>
>
>
> Can you help me?
>
>
>
> Thanks in advance.
>
>
>
>
> ________________________________
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise confidential information. If you
> have received it in error, please notify the sender immediately and
> delete the original. Any other use of the e-mail by you is prohibited.
> Where allowed by local law, electronic communications with Accenture
> and its affiliates, including e-mail and instant messaging (including
> content), may be scanned by our systems for the purposes of
> information security and assessment of internal compliance with Accenture policy. Your privacy is important to us.
> Accenture uses your personal data only in compliance with data
> protection laws. For further information on how Accenture processes
> your personal data, please see our privacy statement at
> https://www.accenture.com/us-en/privacy-policy.
> ______________________________________________________________________
> ________________
>
> www.accenture.com
________________________________
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
______________________________________________________________________________________
www.accenture.com
Re: [External] Re: errorMessage:Client session expired due
Posted by Matthew Jacobs <ja...@gmail.com>.
Hi,
If your application closes queries after they're finished, you
shouldn't need to worry about other resource usage. When you're using
the jdbc client, just make sure to close the ResultSet, Statement, and
Connection objects.
https://docs.oracle.com/javase/7/docs/api/java/sql/Statement.html#close()
https://docs.oracle.com/javase/7/docs/api/java/sql/ResultSet.html#close()
https://docs.oracle.com/javase/7/docs/api/java/sql/Connection.html#close()
On Wed, Apr 4, 2018 at 12:26 AM, Montoya Blanco, A.
<a....@accenture.com> wrote:
> Hi,
>
> Thanx for your response.
>
> Its true that the configure set 3600 sec in idle_session_timeout because we don’t want consume Kluster resources.
>
> I have a web application, and it is possible exist periods of inactivity. So, in the night, its possible more time.
>
> So, how can i solve this issue?
>
> I suppose that idle_session_timeout with 0 value maybe consume a lot of resources ... its true? Is it bad practice?
It is good as long as you close Statements and ResultSets. If you
don't, then resources may be held for those queries. That is the
scenario where using the idle_session_timeout != 0 is helpful.
>
> There are any form to remove this inactive sessions with Java client? I close my client connections when I finish a query....
You can hold the connection if you'd like, just make sure to close the
Statement and ResultSet.
>
> If it is not possible,I have more questions...
>
> Who is open this session? Is impala or is a client?
Not sure what this means.
> Is not there pool connection in Impala?
Not sure what this means.
> Do I need create a new connection every time communicate with BD?
No, you can re-use the Connection object if you'd like - see above.
>
> Thanks in advance.
>
> Un saludo.
>
> Alejandro Montoya Blanco
> Accenture Technology
> a.montoya.blanco@accenture.com
>
>
> -----Original Message-----
> From: Matthew Jacobs [mailto:jacobs.mh@gmail.com]
> Sent: martes, 3 de abril de 2018 18:21
> To: user@impala.apache.org
> Subject: [External] Re: errorMessage:Client session expired due
>
> Hi Montoya,
>
> This is likely due to the "idle_session_timeout" being set to 3600sec.
> Can you check the coordinator web UI to get the configured "idle_session_timeout"?
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__IMPALA-5FCOORDINATOR-5FHOST-3A25000_varz&d=DwIBaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=_tBrUBmJdo4LhYOf5xwULMsNDhup4vUMmd09TUTRlhM&m=XWbZ06Bre5x6j1-NnIzPBq09_mzYXToTGsn3RBXy3k0&s=5K9ZNZnEa-H5FKgaaL3GRrGlxh3k2Gc5R_AkzTCCu8g&e=
>
> See this doc for more information on the configurable timeouts:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__impala.apache.org_docs_build_html_topics_impala-5Ftimeouts.html&d=DwIBaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=_tBrUBmJdo4LhYOf5xwULMsNDhup4vUMmd09TUTRlhM&m=XWbZ06Bre5x6j1-NnIzPBq09_mzYXToTGsn3RBXy3k0&s=2mE9_x6DU2zTkUx8iev3AcnoUMoEgJvKjUu4uZkGw-w&e=
>
> Best,
> Matt
>
> On Tue, Apr 3, 2018 at 6:57 AM, Montoya Blanco, A.
> <a....@accenture.com> wrote:
>> Hi,
>>
>>
>>
>> I get this error:
>>
>>
>>
>> Caused by: java.sql.SQLException: [Simba][ImpalaJDBCDriver](500051)
>> ERROR processing query/statement. Error Code: 0, SQL state:
>> TStatus(statusCode:ERROR_STATUS, sqlState:HY000, errorMessage:Client
>> session expired due to more than 3600s of inactivity .
>>
>>
>>
>> I use JDBC Spring Autoconfigure, and Spring must close the connections
>> automaticatly , and i believe not is the problem because there are
>> same bugs with manually close connection :
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_IMPALA-2D1905&d=DwIBaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=_tBrUBmJdo4LhYOf5xwULMsNDhup4vUMmd09TUTRlhM&m=XWbZ06Bre5x6j1-NnIzPBq09_mzYXToTGsn3RBXy3k0&s=7G7jm5L2u9PaMDt_VC7NUFFrTT3jhYZzgotk54numLA&e=.
>>
>>
>>
>> I supose this error is cause because there are sessions inactive
>> opens, so, Are there any form to close session Impala with JDBC java?
>>
>>
>>
>> it seems the bug has been fixed in Impala 2.0+, but I use driver
>> impala
>> 2.5.38.1 to connect Impala 2.10.0-cdh5.13.1
>>
>>
>>
>> Can you help me?
>>
>>
>>
>> Thanks in advance.
>>
>>
>>
>>
>> ________________________________
>>
>> This message is for the designated recipient only and may contain
>> privileged, proprietary, or otherwise confidential information. If you
>> have received it in error, please notify the sender immediately and
>> delete the original. Any other use of the e-mail by you is prohibited.
>> Where allowed by local law, electronic communications with Accenture
>> and its affiliates, including e-mail and instant messaging (including
>> content), may be scanned by our systems for the purposes of
>> information security and assessment of internal compliance with Accenture policy. Your privacy is important to us.
>> Accenture uses your personal data only in compliance with data
>> protection laws. For further information on how Accenture processes
>> your personal data, please see our privacy statement at
>> https://www.accenture.com/us-en/privacy-policy.
>> ______________________________________________________________________
>> ________________
>>
>> www.accenture.com
>
> ________________________________
>
> This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
> ______________________________________________________________________________________
>
> www.accenture.com