BigData / Apache StreamPark Interview questions
What is the purpose of Yarn Queue Management in StreamPark?
Yarn Queue Management exists to stop a very common, very disruptive mistake: someone typing a YARN queue name (or queue and label) by hand when configuring a job, and getting it slightly wrong.
A typo can send a job to a non-existent queue, causing slow, confusing submission failures, or send it to the wrong real queue, which can eat another team's resources and destabilize their workloads. To prevent this, StreamPark lets an admin register the actual set of valid queues once, scoped to a team, so job configuration becomes a selection from a known-good list rather than free text.
Because the list is shared within a team, everyone submitting jobs for that team is drawing from the same validated set of destinations.
What problem does Yarn Queue Management primarily solve?
Registered queues in this feature are shared at what scope?
More Related questions...
