[CORE] bug report: collision of resource profile id

[rterror]

Spark's default resource profile id is 0. In stage level resource profile, the first returned resource id is also 0 which would lead to a collision.

  val UNKNOWN_RESOURCE_PROFILE_ID = -1
  val DEFAULT_RESOURCE_PROFILE_ID = 0

  private lazy val nextProfileId = new AtomicInteger(0)

spark/core/src/main/scala/org/apache/spark/resource/ResourceProfile.scala

Line 365 in f883693

private lazy val nextProfileId = new AtomicInteger(0)

spark/core/src/main/scala/org/apache/spark/resource/ResourceProfile.scala

Line 363 in f883693

val DEFAULT_RESOURCE_PROFILE_ID = 0

[ybapat]

I've opened a PR to fix this: #57566

The root cause is that nextProfileId starts at AtomicInteger(0), so the first custom profile gets ID 0 — identical to DEFAULT_RESOURCE_PROFILE_ID. The fix starts the counter at 1 and adds a regression test.