From oracle g1gc blog and technical article
And what does full GC mean?
For G1GC, any object that is larger than half the size of the area is considered a " Humongous object ". Such an object stands out directly in the old generation in the " Humongous region s". These Humongous regions are a contiguous set of regions.
Dead Humongous objects are freed at the end of the labeling cycle during the cleaning phase as well as during the complete garbage collection cycle.
In order to reduce copying overhead, Humongous objects are not paused for evacuation. Complete garbage collection cycles. Own facilities in place.
Usually Full GC cleans the whole bunch - both Young and Retained Spaces (old gene)
On the other hand, you need to worry about how long the "application threads" were stopped regardless of the type of GC: Young GC or Full GC, etc.
Is it a pause, is it parallelized?
YounGC is parallelized but not FullGC
Full GC: Currently G1 full gc is single threaded and very slow, , we should try to avoid full gcs as much as possible (From oracle )
What GC algorithm is used?
Do you mean Young GC / Major GC / Full GC? From your magazines, this is the full GC for the last line and YounGC for the first line.
Why did G1 decide to use it?
Explained in response to the first request.
Regarding fine-tuning G1GC, take a look at the oracle article and related question SE