Clustering with the JDBC Data source<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Create a MID Server cluster. Assign a MID server which is part of this cluster to the data source. ‘MID Server Cluster Management’ Business rule assigns one of the available mid servers based on the state of the current MID Server. This ensures data source picks an available mid server if the assigned mid server is down. If the MID server fails while importing the data If the MID server fails during the data upload process, scheduled job transforms the already loaded data to target tables. Scheduled job will run at the next scheduled time. For an example, if the MID server fails while loading 100K records from 1M records. It processes the loaded 100K records for current execution and starts a new scheduled import at next scheduled time. In this case, we expect transform map coalesce fields are set to correct value so that it won’t create any duplicate records. If the ServiceNow instance node which started the scheduled import job fails while importing data If the scheduled job node fails while loading the data, there is no further processing on the currently loading import set. This means all loaded data to import set is in pending state and data in ecc_queue is also in the same state. After node restarts, scheduled job automatically restarts and pulls data from the beginning with a new import set. If the data is finished loaded (i.e import set in loaded state and start running), by the time ServiceNow node fails and com.glide.handling_idle_running_importset property is set to continue, after about 60 minutes import set get transformed. In the case of last update time is set, it won’t update the time until the import set goes to loaded state. Therefore, if the node fails before all data is loaded, once the node restarts data is pull from the original point. If the scheduled import has loaded all data, last update time is set and once the node restarts, scheduled import will take data from there. As pointed there, in this case loaded data are transformed.