The exception is composed this way (see AsyncProcess):
return new RetriesExhaustedWithDetailsException(new
ArrayList<Throwable>(throwables),
new ArrayList<Row>(actions), new ArrayList<String>(addresses));
In your case there were 10456 UnknownHostException's.
Was there any other clue in client side log ?
I think one improvement we can do is selectively logging which host(s) was
involved in the UnknownHostException's.
BTW was hbase-site.xml on the classpath of your client ?
On Tue, May 23, 2017 at 3:28 PM, jeff saremi <[email protected]> wrote:
> We get errors like below which are not helping at all.
>
> For instance in this case we have no clue what server/region it is talking
> about
>
> Is there a setting we missed or somehow we could augment this information
> to help us? We're using hbase 1.2.5
>
>
> Failed 10456 actions: UnknownHostException: 10456 times,
> Stack Trace:
> org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException:
> Failed 10456 actions: UnknownHostException: 10456 times,
> at org.apache.hadoop.hbase.client.AsyncProcess$
> BatchErrors.makeException(AsyncProcess.java:258)
> at org.apache.hadoop.hbase.client.AsyncProcess$
> BatchErrors.access$2000(AsyncProcess.java:238)
> at org.apache.hadoop.hbase.client.AsyncProcess.
> waitForAllPreviousOpsAndReset(AsyncProcess.java:1817)
> at org.apache.hadoop.hbase.client.BufferedMutatorImpl.
> backgroundFlushCommits(BufferedMutatorImpl.java:240)
> at org.apache.hadoop.hbase.client.BufferedMutatorImpl.
> mutate(BufferedMutatorImpl.java:146)
> at org.apache.hadoop.hbase.client.HTable.put(HTable.java:1028)
>
> thanks
>
>
>
>
