TRL 1.17.0 Adds Mistral Large 4 Training on a Single 8xB300 Node and Makes Score Centering the Default AsyncGRPO Objective
Hugging Face's TRL v1.17.0 adds a single-node LoRA example for Mistral Large 4, changes the AsyncGRPO default objective to score centering and makes GRPOConfig raise on top_p or min_p without top_k when vLLM importance sampling is on.
Overview
Hugging Face’s TRL post-training library published v1.17.0 on October 29, 2026, with a patch release, v1.17.1, the next day, according to the v1.17.0 release page. The release notes lead with support for Mistral Large 4 and list two changes that alter default behavior for existing users: a new default objective for AsyncGRPO and a new validation rule for GRPO runs that use vLLM. The Herald covered the previous TRL 1.15.0 release separately.
What Changed
Mistral Large 4 on one node
The notes say TRL now supports mistralai/Mistral-Large-4-1T-A52B, described as “1T parameters, 52B active”. A new LoRA example fine-tunes it with SFTTrainer “on a single 8×B300 node, on top of its FP8 weights”. According to the release notes, the experts are split eight ways with token dispatch, everything else is sharded across the eight GPUs at load time by transformers’ DistributedConfig, and LoRA trains attention and the dense and shared-expert MLPs.
The project reports a measurement of “32.7k tokens per step in ~8 s, 142 GiB per GPU”, with packing and assistant-only loss on reasoning conversations. This is the project’s own figure from its example. The same notes list the minimum versions the example needs: transformers>=5.22.0, peft>=0.21.0 and accelerate>=1.15.0.
Score centering becomes the AsyncGRPO default
The notes explain that AsyncGRPO’s old log-probabilities come from the vLLM sampler, so its ratio “mixes staleness with the numerical mismatch between the server and the trainer”. With an FP8 sampler and a bf16 trainer, the project says the clipped objective collapses: reward goes “from 0.60 to 0.34 (FP8 weights) or 0.10 (FP8 weights + KV cache) by step 300, against 0.71 with a bf16 sampler”.
Score centering with masked importance sampling is now the default, with score_centering=True, importance_sampling_min=0.5 and importance_sampling_max=5.0. The project reports that with it the FP8 sampler trains like the bf16 one (0.72), at a cost of 15–20% of generation throughput. Per the release notes, AsyncGRPO runs now train with a different objective by default, tokens whose ratio to the sampler falls outside [0.5, 5.0] are dropped, and users can set score_centering=False to keep the clipped objective.
Importance-sampling fix for top-k, top-p and min-p
The release notes state that vLLM normalizes its log-probabilities over the tokens left after top_k, top_p and min_p filtering, while the trainer normalized over the whole vocabulary. The result was a biased vLLM importance-sampling ratio, “around 1e-4 instead of 1 with top_p=0.9”. The trainers now normalize over the candidate set each token was sampled from.
One consequence is a new error. With vLLM and the importance-sampling correction on, which is the default, GRPOConfig now raises when top_p < 1.0 or min_p > 0.0 is set without top_k > 0. The notes give two ways out: set top_k (for example top_k=512) or set vllm_importance_sampling_correction=False. The GRPO change applies to vLLM colocate mode with vLLM 0.28 or later, and the notes say server mode “will follow”.
Other Items in the Release
- Tree attention for linear-attention hybrids. Tree packing, introduced in v1.16, now supports the Gated DeltaNet hybrids Qwen3.5, Qwen3.6, Qwen3-Next and OLMo-Hybrid, according to the release notes.
- AMD GPUs. The notes say TRL’s trainers now run on AMD Instinct GPUs through PyTorch’s ROCm build, with a guide and an AMD CI job.
- vLLM 0.32.0. The release adds support for vLLM 0.32.0, which the Herald reported on separately.
- Removals and floors. The experimental TPO trainer is removed, and the minimum versions rise to
torch>=2.6.0,accelerate>=1.11.0andpeft>=0.17.0.
The Patch Release
The v1.17.1 notes list a single change: keeping a parenthesis inside an LFM2.5 tool-call argument from closing the call.
What We Don’t Know
The throughput, memory and reward figures above come from the TRL maintainers’ own release notes, and no independent measurement is cited here. The notes also do not say how many existing AsyncGRPO users run FP8 samplers and are therefore affected by the new default.