Details
-
Test Case
-
Status: Released (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
Pre Test
- Create 3000/4000/5000 jobs and jobchain object
- Deploy jobscheduler object to the jobscheduler
- Shutdown one cluster member
- set -Xmx512m in sos.ini JAVA_OPTIONS
Test
- start cluster member after deploying 3000/4000/5000 jobs and jobchain object
Checks
- Jobscheduler cluster member should be up and running
- Check JOC
- Check scheduler.log
Expected outcome
| Sr. No | Testing step | expected result | result |
|---|---|---|---|
| 1 | start cluster member after deploying 3000 jobs and jobchain object | Jobscheduler cluster member should be up and running and check in scheduler.log that engine is writing the heartbeat message
insert into scheduler_clusters ...... |
/Passed |
| 2 | start cluster member after deploying 4000 jobs and jobchain object | Jobscheduler cluster member should be up and running and check in scheduler.log that engine is writing the heartbeat message
insert into scheduler_clusters ...... |
/Passed |
Attachments
Issue Links
- tests
-
JS-1225 If the JobScheduler is a cluster member and it needs more than 2 minutes to load the configuration files then it terminates because the heartbeat comes too late
-
- Released
-