You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by GitBox <gi...@apache.org> on 2018/05/15 21:22:45 UTC

[GitHub] hlgp opened a new issue #486: 1.8 Master marks bulk import as failed when it could still be successful

hlgp opened a new issue #486: 1.8 Master marks bulk import as failed when it could still be successful
URL: https://github.com/apache/accumulo/issues/486
 
 
   Using default configurations for bulk.timeout, bulk.retry.max, the master will sometimes mark a bulk import as failed even though it was successful.  Sample timings:
   
   11:18:08 master asks tserver1 to import
   11:18:08 tserver1 gets request
   11:23:08 master marks attempt 1 failed (SocketTimeoutException)
   11:23:08 master asks tserver2 to import
   11:23:08 tserver2 gets request
   11:25:27 tserver1 finishes calculating overlapping tablets
   11:25:27 tserver1 completes import
   11:28:08 master marks attempt 2 failed (SocketTimeoutException)
   11:28:22 tserver2 finishes calculating overlapping tablets
   11:28:11 tserver2 successfully completes import
   etc until marked completely failed.
   
   Include examination of map files in tserver timeout?  Check isActive between master reattempts? Other?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services