You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@phoenix.apache.org by ka...@barclays.com on 2016/01/28 20:04:24 UTC
Phoenix Query exception on few tables
We have started seeing PhoenixIOException exception from select query on few of our tables. The same query worked before.
The query is simple select query and the exception is below:
org.apache.phoenix.exception.PhoenixIOException: org.apache.phoenix.exception.PhoenixIOException: The system cannot find the path specified
If I run the scan command from HBase shell on the same table, it works fine.
It appears that Phoenix metadata for these tables might have been corrupted. What could be the problem and how do we fix it?
Thanks for your help.
Regards
Kannan.
_______________________________________________
This message is for information purposes only, it is not a recommendation, advice, offer or solicitation to buy or sell a product or service nor an official confirmation of any transaction. It is directed at persons who are professionals and is not intended for retail customer use. Intended for recipient only. This message is subject to the terms at: www.barclays.com/emaildisclaimer.
For important disclosures, please see: www.barclays.com/salesandtradingdisclaimer regarding market commentary from Barclays Sales and/or Trading, who are active market participants; and in respect of Barclays Research, including disclosures relating to specific issuers, please see http://publicresearch.barclays.com.
_______________________________________________
RE: Phoenix Query exception on few tables
Posted by ka...@barclays.com.
Thanks Ankit, trying your suggestions.
From: Ankit Singhal [mailto:ankitsinghal59@gmail.com]
Sent: Friday, January 29, 2016 10:43
To: user@phoenix.apache.org
Subject: Re: Phoenix Query exception on few tables
can you check HBase master page and see if some regions are in transition or failing in opening/closing?
If yes, then restart your master or try to assign region with assign ‘REGION_NAME’.
And run hbck to detect any consistency and fix them.
http://hbase.apache.org/book.html#hbck.in.depth
you said that scan on HBase is succeeding , are you running it with limit if yes , then it's not touching all the regions and giving result from the opened regions only but with phoenix if you are running query like count(*) which is touching all regions ,will not complete until all region responded. so you need to fix the region assignments first and check hbase master page to be clean before running queries.
Regards,
Ankit Singhal
On Fri, Jan 29, 2016 at 8:28 PM, <ka...@barclays.com>> wrote:
Can someone please help? It’s very sporadic and not sure where to start looking into this issue. Many thanks.
From: Ramanathan, Kannan: IT (NYK)
Sent: Thursday, January 28, 2016 14:04
To: user@phoenix.apache.org<ma...@phoenix.apache.org>
Subject: Phoenix Query exception on few tables
We have started seeing PhoenixIOException exception from select query on few of our tables. The same query worked before.
The query is simple select query and the exception is below:
org.apache.phoenix.exception.PhoenixIOException: org.apache.phoenix.exception.PhoenixIOException: The system cannot find the path specified
If I run the scan command from HBase shell on the same table, it works fine.
It appears that Phoenix metadata for these tables might have been corrupted. What could be the problem and how do we fix it?
Thanks for your help.
Regards
Kannan.
_______________________________________________
This message is for information purposes only, it is not a recommendation, advice, offer or solicitation to buy or sell a product or service nor an official confirmation of any transaction. It is directed at persons who are professionals and is not intended for retail customer use. Intended for recipient only. This message is subject to the terms at: www.barclays.com/emaildisclaimer<http://www.barclays.com/emaildisclaimer>.
For important disclosures, please see: www.barclays.com/salesandtradingdisclaimer<http://www.barclays.com/salesandtradingdisclaimer> regarding market commentary from Barclays Sales and/or Trading, who are active market participants; and in respect of Barclays Research, including disclosures relating to specific issuers, please see http://publicresearch.barclays.com.
_______________________________________________
_______________________________________________
This message is for information purposes only, it is not a recommendation, advice, offer or solicitation to buy or sell a product or service nor an official confirmation of any transaction. It is directed at persons who are professionals and is not intended for retail customer use. Intended for recipient only. This message is subject to the terms at: www.barclays.com/emaildisclaimer<http://www.barclays.com/emaildisclaimer>.
For important disclosures, please see: www.barclays.com/salesandtradingdisclaimer<http://www.barclays.com/salesandtradingdisclaimer> regarding market commentary from Barclays Sales and/or Trading, who are active market participants; and in respect of Barclays Research, including disclosures relating to specific issuers, please see http://publicresearch.barclays.com.
_______________________________________________
_______________________________________________
This message is for information purposes only, it is not a recommendation, advice, offer or solicitation to buy or sell a product or service nor an official confirmation of any transaction. It is directed at persons who are professionals and is not intended for retail customer use. Intended for recipient only. This message is subject to the terms at: www.barclays.com/emaildisclaimer.
For important disclosures, please see: www.barclays.com/salesandtradingdisclaimer regarding market commentary from Barclays Sales and/or Trading, who are active market participants; and in respect of Barclays Research, including disclosures relating to specific issuers, please see http://publicresearch.barclays.com.
_______________________________________________
Re: Phoenix Query exception on few tables
Posted by Ankit Singhal <an...@gmail.com>.
can you check HBase master page and see if some regions are in transition
or failing in opening/closing?
If yes, then restart your master or try to assign region with * assign
‘REGION_NAME’.*
And run *hbck *to detect any consistency and fix them.
http://hbase.apache.org/book.html#hbck.in.depth
you said that scan on HBase is succeeding , are you running it with *limit*
if yes , then it's not touching all the regions and giving result from the
opened regions only but with phoenix if you are running query like count(*)
which is touching all regions ,will not complete until all region
responded. so you need to fix the region assignments first and check hbase
master page to be clean before running queries.
Regards,
Ankit Singhal
On Fri, Jan 29, 2016 at 8:28 PM, <ka...@barclays.com> wrote:
> Can someone please help? It’s very sporadic and not sure where to start
> looking into this issue. Many thanks.
>
>
>
> *From:* Ramanathan, Kannan: IT (NYK)
> *Sent:* Thursday, January 28, 2016 14:04
> *To:* user@phoenix.apache.org
> *Subject:* Phoenix Query exception on few tables
>
>
>
> We have started seeing PhoenixIOException exception from select query on
> few of our tables. The same query worked before.
>
>
>
> The query is simple select query and the exception is below:
>
>
>
> org.apache.phoenix.exception.PhoenixIOException:
> org.apache.phoenix.exception.PhoenixIOException: The system cannot find the
> path specified
>
>
>
> If I run the scan command from HBase shell on the same table, it works
> fine.
>
>
>
> It appears that Phoenix metadata for these tables might have been
> corrupted. What could be the problem and how do we fix it?
>
>
>
> Thanks for your help.
>
>
>
> Regards
>
> Kannan.
>
> _______________________________________________
>
> This message is for information purposes only, it is not a recommendation,
> advice, offer or solicitation to buy or sell a product or service nor an
> official confirmation of any transaction. It is directed at persons who are
> professionals and is not intended for retail customer use. Intended for
> recipient only. This message is subject to the terms at:
> www.barclays.com/emaildisclaimer.
>
> For important disclosures, please see:
> www.barclays.com/salesandtradingdisclaimer regarding market commentary
> from Barclays Sales and/or Trading, who are active market participants; and
> in respect of Barclays Research, including disclosures relating to specific
> issuers, please see http://publicresearch.barclays.com.
>
> _______________________________________________
>
> _______________________________________________
>
> This message is for information purposes only, it is not a recommendation,
> advice, offer or solicitation to buy or sell a product or service nor an
> official confirmation of any transaction. It is directed at persons who are
> professionals and is not intended for retail customer use. Intended for
> recipient only. This message is subject to the terms at:
> www.barclays.com/emaildisclaimer.
>
> For important disclosures, please see:
> www.barclays.com/salesandtradingdisclaimer regarding market commentary
> from Barclays Sales and/or Trading, who are active market participants; and
> in respect of Barclays Research, including disclosures relating to specific
> issuers, please see http://publicresearch.barclays.com.
>
> _______________________________________________
>
RE: Phoenix Query exception on few tables
Posted by ka...@barclays.com.
Can someone please help? It's very sporadic and not sure where to start looking into this issue. Many thanks.
From: Ramanathan, Kannan: IT (NYK)
Sent: Thursday, January 28, 2016 14:04
To: user@phoenix.apache.org
Subject: Phoenix Query exception on few tables
We have started seeing PhoenixIOException exception from select query on few of our tables. The same query worked before.
The query is simple select query and the exception is below:
org.apache.phoenix.exception.PhoenixIOException: org.apache.phoenix.exception.PhoenixIOException: The system cannot find the path specified
If I run the scan command from HBase shell on the same table, it works fine.
It appears that Phoenix metadata for these tables might have been corrupted. What could be the problem and how do we fix it?
Thanks for your help.
Regards
Kannan.
_______________________________________________
This message is for information purposes only, it is not a recommendation, advice, offer or solicitation to buy or sell a product or service nor an official confirmation of any transaction. It is directed at persons who are professionals and is not intended for retail customer use. Intended for recipient only. This message is subject to the terms at: www.barclays.com/emaildisclaimer<http://www.barclays.com/emaildisclaimer>.
For important disclosures, please see: www.barclays.com/salesandtradingdisclaimer<http://www.barclays.com/salesandtradingdisclaimer> regarding market commentary from Barclays Sales and/or Trading, who are active market participants; and in respect of Barclays Research, including disclosures relating to specific issuers, please see http://publicresearch.barclays.com.
_______________________________________________
_______________________________________________
This message is for information purposes only, it is not a recommendation, advice, offer or solicitation to buy or sell a product or service nor an official confirmation of any transaction. It is directed at persons who are professionals and is not intended for retail customer use. Intended for recipient only. This message is subject to the terms at: www.barclays.com/emaildisclaimer.
For important disclosures, please see: www.barclays.com/salesandtradingdisclaimer regarding market commentary from Barclays Sales and/or Trading, who are active market participants; and in respect of Barclays Research, including disclosures relating to specific issuers, please see http://publicresearch.barclays.com.
_______________________________________________