


Apache DolphinScheduler Restricts Timing Scheduling at the Second Level
Background
Apache DolphinScheduler's Timing Task Configuration uses a 7-position Crontab expression, corresponding to seconds, minutes, hours, day of the month, month, day of the week, and year.
In the daily development work of our team, the timing scheduling of workflows generally does not need to be detailed to the second level. However, there have been historical incidents of misconfiguration that led to failure times, such as workflows that should be executed every minute being mistakenly configured to execute every second, resulting in a large number of workflow instances being generated in a short period of time, affecting the availability of the Apache DolphinScheduler service and the Hadoop cluster where tasks are submitted.
Based on this, the team decided to restrict the Crontab expression in the timing task configuration module of DolphinScheduler, to prevent such incidents from happening at the platform level.
Solution
Our solution is to restrict the first position of the Crontab expression from both the front and back ends:
- The front end configuration does not provide the "every second" option
- The server-side interface returns an error when the first position is *
Front-end modification
In the front-end project, seconds, minutes, and hours are all unified templates (CrontabTime), so a new file is added: dolphinscheduler-ui/src/components/crontab/modules/second.tsx
Only two modes are retained: intervalTime and specificTime
/* * Licensed to the Apache Software Foundation (ASF) under one or more * contributor license agreements. See the NOTICE file distributed with * this work for additional information regarding copyright ownership. * The ASF licenses this file to You under the Apache License, Version 2.0 * (the "License"); you may not use this file except in compliance with * the License. You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */ import _ from 'lodash' import { defineComponent, onMounted, PropType, ref, toRefs, watch } from 'vue' import { NInputNumber, NRadio, NRadioGroup, NSelect } from 'naive-ui' import { useI18n } from 'vue-i18n' import { ICrontabI18n } from '../types' import { isStr, specificList } from '../common' import styles from '../index.module.scss' const props = { timeMin: { type: Number as PropType<number>, default: 0 }, timeMax: { type: Number as PropType<number>, default: 60 }, intervalPerform: { type: Number as PropType<number>, default: 5 }, intervalStart: { type: Number as PropType<number>, default: 3 }, timeSpecial: { type: Number as PropType<number | string>, default: 60 }, timeValue: { type: String as PropType<string>, default: '*' }, timeI18n: { type: Object as PropType<ICrontabI18n>, require: true } } export default defineComponent({ name: 'CrontabSecond', props, emits: ['update:timeValue'], setup(props, ctx) { const options = Array.from({ length: 60 }, (x, i) => ({ label: i.toString(), value: i })) const timeRef = ref() const radioRef = ref() const intervalStartRef = ref(props.intervalStart) const intervalPerformRef = ref(props.intervalPerform) const specificTimesRef = ref<Array<number>>([]) /** * Parse parameter value */ const analyticalValue = () => { const $timeVal = props.timeValue // Interval time const $interval = isStr($timeVal, '/') // Specific time const $specific = isStr($timeVal, ',') // Positive integer (times) if ( ($timeVal.length === 1 || $timeVal.length === 2 || $timeVal.length === 4) && _.isInteger(parseInt($timeVal)) ) { radioRef.value = 'specificTime' specificTimesRef.value = [parseInt($timeVal)] return } // Interval times if ($interval) { radioRef.value = 'intervalTime' intervalStartRef.value = parseInt($interval[0]) intervalPerformRef.value = parseInt($interval[1]) timeRef.value = `${intervalStartRef.value}/${intervalPerformRef.value}` return } // Specific times if ($specific) { radioRef.value = 'specificTime' specificTimesRef.value = $specific.map((item) => parseInt(item)) return } } // Interval start time(1) const onIntervalStart = (value: number | null) => { intervalStartRef.value = value || 0 if (radioRef.value === 'intervalTime') { timeRef.value = `${intervalStartRef.value}/${intervalPerformRef.value}` } } // Interval execution time(2) const onIntervalPerform = (value: number | null) => { intervalPerformRef.value = value || 0 if (radioRef.value === 'intervalTime') { timeRef.value = `${intervalStartRef.value}/${intervalPerformRef.value}` } } // Specific time const onSpecificTimes = (arr: Array<number>) => { specificTimesRef.value = arr if (radioRef.value === 'specificTime') { specificReset() } } // Reset interval time const intervalReset = () => { timeRef.value = `${intervalStartRef.value}/${intervalPerformRef.value}` } // Reset specific time const specificReset = () => { let timeValue = '0' if (specificTimesRef.value.length) { timeValue = specificTimesRef.value.join(',') } timeRef.value = timeValue } const updateRadioTime = (value: string) => { switch (value) { case 'intervalTime': intervalReset() break case 'specificTime': specificReset() break } } watch( () => timeRef.value, () => ctx.emit('update:timeValue', timeRef.value.toString()) ) onMounted(() => analyticalValue()) return { options, radioRef, intervalStartRef, intervalPerformRef, specificTimesRef, updateRadioTime, onIntervalStart, onIntervalPerform, onSpecificTimes, ...toRefs(props) } }, render() { const { t } = useI18n() return ( <NRadioGroup v-model:value={this.radioRef} onUpdateValue={this.updateRadioTime} > <div> <h3> Server-side </h3> <p>Add Crontab expression validation (there are two places: one is the new POST interface, and the other is the modified PUT interface), directly add a validation method for these two places to call:<br> </p> <pre class="brush:php;toolbar:false"> if (scheduleParam.getCrontab().startsWith("*")) { logger.error("The crontab must not start with *"); putMsg(result, Status.CRONTAB_EVERY_SECOND_ERROR); return result; }
This concludes the article.
The above is the detailed content of Apache DolphinScheduler Restricts Timing Scheduling at the Second Level. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Frequently Asked Questions and Solutions for Front-end Thermal Paper Ticket Printing In Front-end Development, Ticket Printing is a common requirement. However, many developers are implementing...

JavaScript is the cornerstone of modern web development, and its main functions include event-driven programming, dynamic content generation and asynchronous programming. 1) Event-driven programming allows web pages to change dynamically according to user operations. 2) Dynamic content generation allows page content to be adjusted according to conditions. 3) Asynchronous programming ensures that the user interface is not blocked. JavaScript is widely used in web interaction, single-page application and server-side development, greatly improving the flexibility of user experience and cross-platform development.

There is no absolute salary for Python and JavaScript developers, depending on skills and industry needs. 1. Python may be paid more in data science and machine learning. 2. JavaScript has great demand in front-end and full-stack development, and its salary is also considerable. 3. Influencing factors include experience, geographical location, company size and specific skills.

Discussion on the realization of parallax scrolling and element animation effects in this article will explore how to achieve similar to Shiseido official website (https://www.shiseido.co.jp/sb/wonderland/)...

Learning JavaScript is not difficult, but it is challenging. 1) Understand basic concepts such as variables, data types, functions, etc. 2) Master asynchronous programming and implement it through event loops. 3) Use DOM operations and Promise to handle asynchronous requests. 4) Avoid common mistakes and use debugging techniques. 5) Optimize performance and follow best practices.

The latest trends in JavaScript include the rise of TypeScript, the popularity of modern frameworks and libraries, and the application of WebAssembly. Future prospects cover more powerful type systems, the development of server-side JavaScript, the expansion of artificial intelligence and machine learning, and the potential of IoT and edge computing.

How to merge array elements with the same ID into one object in JavaScript? When processing data, we often encounter the need to have the same ID...

Explore the implementation of panel drag and drop adjustment function similar to VSCode in the front-end. In front-end development, how to implement VSCode similar to VSCode...
