Thank you.
I will download and use hector 0.7.0-28.jar in my next check point.
Meanwhile here is a different issue i noticed.
For the same state of cassandra nodes, i am seeing different behavior
at Hector on separate machines using Hector. On 2 machines, i see the
transactions are going through just fine to cassandra (except for some
timeouts), but on the 3rd machine, hector is throwing a lot of these
exceptions below.
My question is how is it that one hector client is throwing exceptions
below while the other hector clients are running smooth with all 3
pushing the load to the cluster? Note that i am using the same hector
version hector 0.7.0-26.jar in all 3 clients.
Also i am assuming that " Retry burden pushed out to client." means
that the consumer of hector api now owns the responsibility to perform
a retry. If this is true, what would your recommendations be, for
cleaning up and retrying the transactions?
2011-02-22 18:59:09,894 [main] ERROR (CassandraService.java:2023) -
me.prettyprint.hector.api.exceptions.HectorException: All host pools
marked down. Retry burden pushed out to client.
2011-02-22 18:59:09,894 [main] ERROR (CassandraService.java:2023) -
me.prettyprint.hector.api.exceptions.HectorException: All host pools
marked down. Retry burden pushed out to client.
2011-02-22 18:59:09,895 [main] ERROR (CassandraService.java:2023) -
me.prettyprint.hector.api.exceptions.HectorException: All host pools
marked down. Retry burden pushed out to client.
2011-02-22 18:59:09,895 [main] ERROR (CassandraService.java:2023) -
me.prettyprint.hector.api.exceptions.HectorException: All host pools
marked down. Retry burden pushed out to client.
2011-02-22 18:59:09,895 [main] ERROR (CassandraService.java:2023) -
me.prettyprint.hector.api.exceptions.HectorException: All host pools
marked down. Retry burden pushed out to client.
2011-02-22 18:59:09,895 [main] ERROR (CassandraService.java:2023) -
me.prettyprint.hector.api.exceptions.HectorException: All host pools
marked down. Retry burden pushed out to client.
2011-02-22 18:59:09,895 [main] ERROR (CassandraService.java:2099) -
me.prettyprint.hector.api.exceptions.HectorException: All host pools
marked down. Retry burden pushed out to client.
me.prettyprint.hector.api.exceptions.HectorException: All host pools
marked down. Retry burden pushed out to client.
me.prettyprint.hector.api.exceptions.HectorException: All host pools
marked down. Retry burden pushed out to client.
2011-02-22 18:59:09,895 [main] ERROR (CassandraService.java:2099) -
me.prettyprint.hector.api.exceptions.HectorException: All host pools
marked down. Retry burden pushed out to client.
2011-02-22 18:59:09,896 [main] ERROR (CassandraService.java:582) -
me.prettyprint.hector.api.exceptions.HectorException: All host pools
marked down. Retry burden pushed out to client.
2011-02-22 18:59:09,896 [main] ERROR (CassandraService.java:582) -
me.prettyprint.hector.api.exceptions.HectorException: All host pools
marked down. Retry burden pushed out to client.
2011-02-22 18:59:09,896 [main] ERROR (CassandraService.java:2099) -
me.prettyprint.hector.api.exceptions.HectorException: All host pools
marked down. Retry burden pushed out to client.
2011-02-22 18:59:09,896 [main] ERROR (CassandraService.java:2099) -
me.prettyprint.hector.api.exceptions.HectorException: All host pools
marked down. Retry burden pushed out to client.
On Feb 23, 8:42 am, Nate McCall <
n...@datastax.com> wrote:
> Actually this is working as anticipated. The following line from the
> stack trace:
>
> me.prettyprint.cassandra.connection.HThriftClient.open(HThriftClient.java:
>
> indicates this is the host retry service (running in a background
> thread) attempting to connect to the downed host every 10 seconds (by
> default). What was just fixed in master and tip of 0.7.0 was an issue
> with incorrect handling of UnavailableException on a consistency level
> failure. This will be released at some point today (marked as
> 0.7.0-28).
>
> On looking at the above trace again, that error could probably be more
> clear about what is going on. I'll clean that up today as well.
>
> 2011/2/22 Patricio Echagüe <
patric...@gmail.com>:
>
> > hey I trying to find the code for that version.
> > I believe there was a fix for that.
> > Looking at the current code, it seems to addressed in the version .28
>
> > private boolean verifyConnection(CassandraHost cassandraHost) {
>
> > if ( cassandraHost == null ) {
>
> > return false;
>
> > }
>
> > boolean found = false;
>
> > HThriftClient client = new HThriftClient(cassandraHost);
>
> > try {
>
> > client.open();
>
> > found = client.getCassandra().describe_cluster_name() != null;
>
> > client.close();
>
> > } catch (HectorTransportException he) {
>
> > log.error("Downed {} host still appears to be down: {}",
> > cassandraHost, he.getMessage());
>
> > } catch (Exception ex) {
>
> > log.error("Downed Host retry failed attempt to verify
> > CassandraHost", ex);
>
> > }
>
> > return found;
>
> > }
>
> > 2011/2/22 Subrahmanya Harve <
subrahmanyaha...@gmail.com>
>
> >> Please find the configuration of CassandraHostConfigurator below.
>
> >> MaxActive=50
> >> MaxIdle=10
> >> MaxWaitTimeWhenExhausted=1000
> >> ThriftSocketTimeout=1000
> >> ExhaustedPolicy=WHEN_EXHAUSTED_FAIL
> >> LoadBalanceingPolicy=RoundRobinBalancingPolicy
> >> ConsistencyLevelPolicy=QuorumAllConsistencyLevelPolicy
> >> FailoverPolicy=ON_FAIL_TRY_ONE_NEXT_AVAILABLE
>
> >> 2011/2/22 Patricio Echagüe <
patric...@gmail.com>
>
> >>> Could you please provide your CassandraHostConfigurator values?
>