Support Questions
Find answers, ask questions, and share your expertise
Check out our newest addition to the community, the Cloudera Innovation Accelerator group hub.

Kudu table consistency on tablet servers using impala JDBC

New Contributor



I've an issue with updating an impala kudu table by cloudera impala JDBC driver version: 2.5.43


The case:

1. Application updates some kudu table by setting new value to some column.

2. Immediately after updating the application invokes sql request that query this table along with others

3. This application suppose that this table is updated however sometimes the query returns an old data.


The replication factor is 3 so I think that updating has happened on one tablet server but query has gone to other tablet server. The application works right if it waits for a couple of seconds between point 1 and 2.


Is it possible somehow to avoid such kind of inconsistency?



Rising Star
Impala doesn't provide "read your writes" consistency by default. In order to enable it, you need to reconfigure your Impala daemons with --kudu_read_mode=READ_AT_SNAPSHOT.

See for more information.