Major maven_repo_640 is a 640 Gbyte repository created based on replications of four-10 Gbyte repositories from Central. Test consisted on hardlink migration with no elastic search (6 hours completed successfully), followed by a task: repository-rebuild index, whiuch was started at 18:00:01. Schedule task failed after 9m with the following log:
'Hardlink migration no ES' [repository.rebuild-index] state change WAITING -> RUNNING
2016-05-09 18:00:51,291-0400 INFO [quartz-2-thread-1] *TASK org.sonatype.nexus.repository.search.SearchFacetImpl - Rebuilding index of repository maven_repo_640
2016-05-09 18:00:51,350-0400 INFO elasticsearch[B50997FF-9F459BB7-1E61240C-1E562E58-79A87DD5]clusterService#updateTaskT#1 org.elasticsearch.cluster.metadata - [B50997FF-9F459BB7-1E61240C-1E562E58-79A87DD5] [dcce44c0cc6b2349fa68bacb48cf73e166f24fae] creating index, cause [api], templates [], shards [5]/[1], mappings [component]
2016-05-09 18:00:51,421-0400 INFO elasticsearch[B50997FF-9F459BB7-1E61240C-1E562E58-79A87DD5]clusterService#updateTaskT#1 org.elasticsearch.cluster.routing.allocation - [B50997FF-9F459BB7-1E61240C-1E562E58-79A87DD5] Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[dcce44c0cc6b2349fa68bacb48cf73e166f24fae][4]] ...]).
2016-05-09 18:00:52,724-0400 INFO elasticsearch[B50997FF-9F459BB7-1E61240C-1E562E58-79A87DD5]clusterService#updateTaskT#1 org.elasticsearch.cluster.metadata - [B50997FF-9F459BB7-1E61240C-1E562E58-79A87DD5] [dcce44c0cc6b2349fa68bacb48cf73e166f24fae] update_mapping [component]
2016-05-09 18:00:52,736-0400 INFO elasticsearch[B50997FF-9F459BB7-1E61240C-1E562E58-79A87DD5]clusterService#updateTaskT#1 org.elasticsearch.cluster.metadata - [B50997FF-9F459BB7-1E61240C-1E562E58-79A87DD5] [dcce44c0cc6b2349fa68bacb48cf73e166f24fae] update_mapping [component]
2016-05-09 18:07:46,306-0400 WARN [elasticsearch[B50997FF-9F459BB7-1E61240C-1E562E58-79A87DD5][management]T#2] org.elasticsearch.cluster - [B50997FF-9F459BB7-1E61240C-1E562E58-79A87DD5] Failed to execute IndicesStatsAction for ClusterInfoUpdateJob
java.lang.OutOfMemoryError: GC overhead limit exceeded
2016-05-09 18:07:46,306-0400 WARN [elasticsearch[B50997FF-9F459BB7-1E61240C-1E562E58-79A87DD5][scheduler]T#1] org.elasticsearch.index.translog - [B50997FF-9F459BB7-1E61240C-1E562E58-79A87DD5] [73ae44bc066b6a7a33b4435641d8229b9b66495a][2] unexpected error while checking whether the translog needs a flush. rescheduling
java.lang.OutOfMemoryError: GC overhead limit exceeded
2016-05-09 18:07:46,306-0400 WARN [elasticsearch[B50997FF-9F459BB7-1E61240C-1E562E58-79A87DD5][[ttl_expire]]] org.elasticsearch.indices.ttl - [B50997FF-9F459BB7-1E61240C-1E562E58-79A87DD5] failed to execute ttl purge
java.lang.OutOfMemoryError: GC overhead limit exceeded
2016-05-09 18:07:50,394-0400 WARN [elasticsearch[B50997FF-9F459BB7-1E61240C-1E562E58-79A87DD5][index]T#4] org.elasticsearch.index.engine - [B50997FF-9F459BB7-1E61240C-1E562E58-79A87DD5] [dcce44c0cc6b2349fa68bacb48cf73e166f24fae][4] failed engine [already closed by tragic event on the index writer]
java.lang.OutOfMemoryError: GC overhead limit exceeded