Add LogContext to VPJ timeout executor and bump thread pool to 2

Pass LogContext with store name to DaemonThreadFactory so monitor
threads carry context in log lines. Bump pool from single thread to 2
so timeout and kill-check monitors don't contend.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: pthirun

clients/venice-push-job/src/main/java/com/linkedin/venice/hadoop/VenicePushJob.java

@@ -152,6 +152,7 @@
 import com.linkedin.venice.utils.DictionaryUtils;
 import com.linkedin.venice.utils.EncodingUtils;
 import com.linkedin.venice.utils.LatencyUtils;
+import com.linkedin.venice.utils.LogContext;
 import com.linkedin.venice.utils.PartitionUtils;
 import com.linkedin.venice.utils.ReflectUtils;
 import com.linkedin.venice.utils.RegionUtils;
@@ -291,8 +292,12 @@ public VenicePushJob(String jobId, Properties vanillaProps, D2Client d2Client) {
     this.jobId = jobId;
     this.externalD2Client = d2Client;
     this.props = getVenicePropsFromVanillaProps(Objects.requireNonNull(vanillaProps, "VPJ props cannot be null"));
-    this.timeoutExecutor = Executors
-        .newSingleThreadScheduledExecutor(new DaemonThreadFactory(this.getClass().getName() + "-VPJTimeoutExecutor"));
+    String storeName = this.props.getString(VENICE_STORE_NAME_PROP);
+    LogContext logContext =
+        LogContext.newBuilder().setComponentName("VenicePushJob").setInstanceName(storeName).build();
+    this.timeoutExecutor = Executors.newScheduledThreadPool(
+        2,
+        new DaemonThreadFactory(this.getClass().getName() + "-VPJTimeoutExecutor", logContext));
     LOGGER.info("Constructing {}: {}", VenicePushJob.class.getSimpleName(), props.toString(true));
     this.sslProperties = Lazy.of(() -> {
       try {