Could be a number of causes. If you are not using the proxy I'd ensure the
tserver is still hosting after a split. If you are you can get more info
from the exception.
In my CPP client I take failed mutations and requeue them depending on the
exception details. If the extent locations have changed I update. If a
security issue then I return an error.
On Tue, Feb 14, 2017, 11:11 AM z11373 <z11...@outlook.com> wrote:
> Hi,
> I have c++ client talking to Accumulo via Thrift.
> The client app is simply running in the loop, and inside the loop it
> creates
> batch writer, add mutation with random length of string data, call that
> batch writer flush() and close() methods. The code is running fine, except
> when running it with multiple instances, and after some number of
> iterations, some of the instances may start hitting this exception:
>
> org.apache.accumulo.core.client.MutationsRejectedException: # constraint
> violations : 0 security codes: {} # server errors 0 # exceptions 1
>
> Do you know what causing this exception? Does it have anything to do with
> the fact the client is accessing Accumulo via Thrift, or problem with the
> Thrift proxy itself?
>
>
> Thanks,
> Z
>
>
>
> --
> View this message in context:
> http://apache-accumulo.1065345.n5.nabble.com/exception-from-thrift-tp19919.html
> Sent from the Developers mailing list archive at Nabble.com.
>
