status
stringclasses 1
value | repo_name
stringclasses 31
values | repo_url
stringclasses 31
values | issue_id
int64 1
104k
| title
stringlengths 4
233
| body
stringlengths 0
186k
⌀ | issue_url
stringlengths 38
56
| pull_url
stringlengths 37
54
| before_fix_sha
stringlengths 40
40
| after_fix_sha
stringlengths 40
40
| report_datetime
unknown | language
stringclasses 5
values | commit_datetime
unknown | updated_file
stringlengths 7
188
| chunk_content
stringlengths 1
1.03M
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-common/src/main/java/org/apache/dolphinscheduler/common/utils/FileUtils.java | public static final ThreadLocal<Logger> taskLoggerThreadLocal = new ThreadLocal<>();
private FileUtils() {
throw new UnsupportedOperationException("Construct FileUtils");
}
/**
* get file suffix
*
* @param filename file name
* @return file suffix
*/
public static String suffix(String filename) {
String fileSuffix = "";
if (StringUtils.isNotEmpty(filename)) {
int lastIndex = filename.lastIndexOf('.');
if (lastIndex > 0) {
fileSuffix = filename.substring(lastIndex + 1);
}
}
return fileSuffix;
}
/**
* get download file absolute path and name
*
* @param filename file name
* @return download file name
*/
public static String getDownloadFilename(String filename) {
String fileName = String.format("%s/download/%s/%s", DATA_BASEDIR, DateUtils.getCurrentTime(YYYYMMDDHHMMSS), filename);
File file = new File(fileName);
if (!file.getParentFile().exists()) { |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-common/src/main/java/org/apache/dolphinscheduler/common/utils/FileUtils.java | file.getParentFile().mkdirs();
}
return fileName;
}
/**
* get upload file absolute path and name
*
* @param tenantCode tenant code
* @param filename file name
* @return local file path
*/
public static String getUploadFilename(String tenantCode, String filename) {
String fileName = String.format("%s/%s/resources/%s", DATA_BASEDIR, tenantCode, filename);
File file = new File(fileName);
if (!file.getParentFile().exists()) {
file.getParentFile().mkdirs();
}
return fileName;
}
/**
* directory of process execution
*
* @param projectId project id
* @param processDefineId process definition id
* @param processInstanceId process instance id
* @param taskInstanceId task instance id
* @return directory of process execution
*/
public static String getProcessExecDir(int projectId, int processDefineId, int processInstanceId, int taskInstanceId) {
String fileName = String.format("%s/exec/process/%s/%s/%s/%s", DATA_BASEDIR, Integer.toString(projectId), |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-common/src/main/java/org/apache/dolphinscheduler/common/utils/FileUtils.java | Integer.toString(processDefineId), Integer.toString(processInstanceId), Integer.toString(taskInstanceId));
File file = new File(fileName);
if (!file.getParentFile().exists()) {
file.getParentFile().mkdirs();
}
return fileName;
}
/**
* directory of process instances
*
* @param projectId project id
* @param processDefineId process definition id
* @param processInstanceId process instance id
* @return directory of process instances
*/
public static String getProcessExecDir(int projectId, int processDefineId, int processInstanceId) {
String fileName = String.format("%s/exec/process/%s/%s/%s", DATA_BASEDIR, Integer.toString(projectId),
Integer.toString(processDefineId), Integer.toString(processInstanceId));
File file = new File(fileName);
if (!file.getParentFile().exists()) {
file.getParentFile().mkdirs();
}
return fileName;
}
/**
* @return get suffixes for resource files that support online viewing
*/
public static String getResourceViewSuffixs() {
return PropertyUtils.getString(RESOURCE_VIEW_SUFFIXS, RESOURCE_VIEW_SUFFIXS_DEFAULT_VALUE);
} |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-common/src/main/java/org/apache/dolphinscheduler/common/utils/FileUtils.java | /**
* create directory if absent
*
* @param execLocalPath execute local path
* @throws IOException errors
*/
public static void createWorkDirIfAbsent(String execLocalPath) throws IOException {
File execLocalPathFile = new File(execLocalPath);
if (execLocalPathFile.exists()) {
org.apache.commons.io.FileUtils.forceDelete(execLocalPathFile);
}
org.apache.commons.io.FileUtils.forceMkdir(execLocalPathFile);
String mkdirLog = "create dir success " + execLocalPath;
LoggerUtils.logInfo(Optional.ofNullable(logger), mkdirLog);
LoggerUtils.logInfo(Optional.ofNullable(taskLoggerThreadLocal.get()), mkdirLog);
}
/**
* write content to file ,if parent path not exists, it will do one's utmost to mkdir
*
* @param content content
* @param filePath target file path
* @return true if write success
*/
public static boolean writeContent2File(String content, String filePath) {
boolean flag = true;
BufferedReader bufferedReader = null;
BufferedWriter bufferedWriter = null;
try { |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-common/src/main/java/org/apache/dolphinscheduler/common/utils/FileUtils.java | File distFile = new File(filePath);
if (!distFile.getParentFile().exists() && !distFile.getParentFile().mkdirs()) {
FileUtils.logger.error("mkdir parent failed");
return false;
}
bufferedReader = new BufferedReader(new StringReader(content));
bufferedWriter = new BufferedWriter(new OutputStreamWriter(new FileOutputStream(distFile), StandardCharsets.UTF_8));
char[] buf = new char[1024];
int len;
while ((len = bufferedReader.read(buf)) != -1) {
bufferedWriter.write(buf, 0, len);
}
bufferedWriter.flush();
bufferedReader.close();
bufferedWriter.close();
} catch (IOException e) {
FileUtils.logger.error(e.getMessage(), e);
flag = false;
return flag;
} finally {
IOUtils.closeQuietly(bufferedWriter);
IOUtils.closeQuietly(bufferedReader);
}
return flag;
}
/**
* Writes a String to a file creating the file if it does not exist.
* <p>
* NOTE: As from v1.3, the parent directories of the file will be created
* if they do not exist. |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-common/src/main/java/org/apache/dolphinscheduler/common/utils/FileUtils.java | *
* @param file the file to write
* @param data the content to write to the file
* @param encoding the encoding to use, {@code null} means platform default
* @throws IOException in case of an I/O error
* @throws java.io.UnsupportedEncodingException if the encoding is not supported by the VM
* @since 2.4
*/
public static void writeStringToFile(File file, String data, Charset encoding) throws IOException {
writeStringToFile(file, data, encoding, false);
}
/**
* Writes a String to a file creating the file if it does not exist.
* <p>
* NOTE: As from v1.3, the parent directories of the file will be created
* if they do not exist.
*
* @param file the file to write
* @param data the content to write to the file
* @param encoding the encoding to use, {@code null} means platform default
* @throws IOException in case of an I/O error
* @throws java.io.UnsupportedEncodingException if the encoding is not supported by the VM
*/
public static void writeStringToFile(File file, String data, String encoding) throws IOException {
writeStringToFile(file, data, encoding, false);
}
/**
* Writes a String to a file creating the file if it does not exist.
*
* @param file the file to write |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-common/src/main/java/org/apache/dolphinscheduler/common/utils/FileUtils.java | * @param data the content to write to the file
* @param encoding the encoding to use, {@code null} means platform default
* @param append if {@code true}, then the String will be added to the
* end of the file rather than overwriting
* @throws IOException in case of an I/O error
* @since 2.3
*/
public static void writeStringToFile(File file, String data, Charset encoding, boolean append) throws IOException {
OutputStream out = null;
try {
out = openOutputStream(file, append);
IOUtils.write(data, out, encoding);
out.close();
} finally {
IOUtils.closeQuietly(out);
}
}
/**
* Writes a String to a file creating the file if it does not exist.
*
* @param file the file to write
* @param data the content to write to the file
* @param encoding the encoding to use, {@code null} means platform default
* @param append if {@code true}, then the String will be added to the
* end of the file rather than overwriting
* @throws IOException in case of an I/O error
* @throws UnsupportedCharsetException thrown instead of {@link UnsupportedEncodingException} in version 2.2 if the encoding is not
* supported by the VM
* @since 2.1
*/ |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-common/src/main/java/org/apache/dolphinscheduler/common/utils/FileUtils.java | public static void writeStringToFile(File file, String data, String encoding, boolean append) throws IOException {
writeStringToFile(file, data, Charsets.toCharset(encoding), append);
}
/**
* Writes a String to a file creating the file if it does not exist using the default encoding for the VM.
*
* @param file the file to write
* @param data the content to write to the file
* @throws IOException in case of an I/O error
*/
public static void writeStringToFile(File file, String data) throws IOException {
writeStringToFile(file, data, Charset.defaultCharset(), false);
}
/**
* Writes a String to a file creating the file if it does not exist using the default encoding for the VM.
*
* @param file the file to write
* @param data the content to write to the file
* @param append if {@code true}, then the String will be added to the
* end of the file rather than overwriting
* @throws IOException in case of an I/O error
* @since 2.1
*/
public static void writeStringToFile(File file, String data, boolean append) throws IOException {
writeStringToFile(file, data, Charset.defaultCharset(), append);
}
/**
* Opens a {@link FileOutputStream} for the specified file, checking and
* creating the parent directory if it does not exist.
* <p> |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-common/src/main/java/org/apache/dolphinscheduler/common/utils/FileUtils.java | * At the end of the method either the stream will be successfully opened,
* or an exception will have been thrown.
* <p>
* The parent directory will be created if it does not exist.
* The file will be created if it does not exist.
* An exception is thrown if the file object exists but is a directory.
* An exception is thrown if the file exists but cannot be written to.
* An exception is thrown if the parent directory cannot be created.
*
* @param file the file to open for output, must not be {@code null}
* @return a new {@link FileOutputStream} for the specified file
* @throws IOException if the file object is a directory
* @throws IOException if the file cannot be written to
* @throws IOException if a parent directory needs creating but that fails
* @since 1.3
*/
public static FileOutputStream openOutputStream(File file) throws IOException {
return openOutputStream(file, false);
}
/**
* Opens a {@link FileOutputStream} for the specified file, checking and
* creating the parent directory if it does not exist.
* <p>
* At the end of the method either the stream will be successfully opened,
* or an exception will have been thrown.
* <p>
* The parent directory will be created if it does not exist.
* The file will be created if it does not exist.
* An exception is thrown if the file object exists but is a directory.
* An exception is thrown if the file exists but cannot be written to. |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-common/src/main/java/org/apache/dolphinscheduler/common/utils/FileUtils.java | * An exception is thrown if the parent directory cannot be created.
*
* @param file the file to open for output, must not be {@code null}
* @param append if {@code true}, then bytes will be added to the
* end of the file rather than overwriting
* @return a new {@link FileOutputStream} for the specified file
* @throws IOException if the file object is a directory
* @throws IOException if the file cannot be written to
* @throws IOException if a parent directory needs creating but that fails
* @since 2.1
*/
public static FileOutputStream openOutputStream(File file, boolean append) throws IOException {
if (file.exists()) {
if (file.isDirectory()) {
throw new IOException("File '" + file + "' exists but is a directory");
}
if (!file.canWrite()) {
throw new IOException("File '" + file + "' cannot be written to");
}
} else {
File parent = file.getParentFile();
if (parent != null && !parent.mkdirs() && !parent.isDirectory()) {
throw new IOException("Directory '" + parent + "' could not be created");
}
}
return new FileOutputStream(file, append);
}
/**
* deletes a directory recursively
* |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-common/src/main/java/org/apache/dolphinscheduler/common/utils/FileUtils.java | * @param dir directory
* @throws IOException in case deletion is unsuccessful
*/
public static void deleteDir(String dir) throws IOException {
org.apache.commons.io.FileUtils.deleteDirectory(new File(dir));
}
/**
* Deletes a file. If file is a directory, delete it and all sub-directories.
* <p>
* The difference between File.delete() and this method are:
* <ul>
* <li>A directory to be deleted does not have to be empty.</li>
* <li>You get exceptions when a file or directory cannot be deleted.
* (java.io.File methods returns a boolean)</li>
* </ul>
*
* @param filename file name
* @throws IOException in case deletion is unsuccessful
*/
public static void deleteFile(String filename) throws IOException {
org.apache.commons.io.FileUtils.forceDelete(new File(filename));
}
/**
* Gets all the parent subdirectories of the parentDir directory
*
* @param parentDir parent dir
* @return all dirs
*/
public static File[] getAllDir(String parentDir) {
if (parentDir == null || "".equals(parentDir)) { |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-common/src/main/java/org/apache/dolphinscheduler/common/utils/FileUtils.java | throw new RuntimeException("parentDir can not be empty");
}
File file = new File(parentDir);
if (!file.exists() || !file.isDirectory()) {
throw new RuntimeException("parentDir not exist, or is not a directory:" + parentDir);
}
return file.listFiles(File::isDirectory);
}
/**
* Get Content
*
* @param inputStream input stream
* @return string of input stream
*/
public static String readFile2Str(InputStream inputStream) {
try {
ByteArrayOutputStream output = new ByteArrayOutputStream();
byte[] buffer = new byte[1024];
int length;
while ((length = inputStream.read(buffer)) != -1) {
output.write(buffer, 0, length);
}
return output.toString();
} catch (Exception e) {
logger.error(e.getMessage(), e);
throw new RuntimeException(e);
}
}
} |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-common/src/test/java/org/apache/dolphinscheduler/common/utils/FileUtilsTest.java | /*
* 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.
*/
package org.apache.dolphinscheduler.common.utils;
import static org.apache.dolphinscheduler.common.Constants.YYYYMMDDHHMMSS;
import org.apache.dolphinscheduler.common.Constants;
import java.io.File;
import java.io.FileInputStream;
import java.io.FileNotFoundException;
import org.junit.Assert;
import org.junit.Test;
import org.junit.runner.RunWith;
import org.powermock.api.mockito.PowerMockito;
import org.powermock.core.classloader.annotations.PrepareForTest;
import org.powermock.modules.junit4.PowerMockRunner;
@RunWith(PowerMockRunner.class) |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-common/src/test/java/org/apache/dolphinscheduler/common/utils/FileUtilsTest.java | @PrepareForTest(DateUtils.class)
public class FileUtilsTest {
@Test
public void suffix() {
Assert.assertEquals("java", FileUtils.suffix("ninfor.java"));
Assert.assertEquals("", FileUtils.suffix(null));
Assert.assertEquals("", FileUtils.suffix(""));
Assert.assertEquals("", FileUtils.suffix("ninfor-java"));
}
@Test
public void testGetDownloadFilename() {
PowerMockito.mockStatic(DateUtils.class);
PowerMockito.when(DateUtils.getCurrentTime(YYYYMMDDHHMMSS)).thenReturn("20190101101059");
Assert.assertEquals("/tmp/dolphinscheduler/download/20190101101059/test",
FileUtils.getDownloadFilename("test"));
}
@Test
public void testGetUploadFilename() {
Assert.assertEquals("/tmp/dolphinscheduler/aaa/resources/bbb",
FileUtils.getUploadFilename("aaa","bbb"));
}
@Test
public void testGetProcessExecDir() {
String dir = FileUtils.getProcessExecDir(1,2,3, 4);
Assert.assertEquals("/tmp/dolphinscheduler/exec/process/1/2/3/4", dir);
dir = FileUtils.getProcessExecDir(1,2,3);
Assert.assertEquals("/tmp/dolphinscheduler/exec/process/1/2/3", dir);
}
@Test |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-common/src/test/java/org/apache/dolphinscheduler/common/utils/FileUtilsTest.java | public void testCreateWorkDirIfAbsent() {
try {
FileUtils.createWorkDirIfAbsent("/tmp/createWorkDirAndUserIfAbsent");
Assert.assertTrue(true);
} catch (Exception e) {
Assert.assertTrue(false);
}
}
@Test
public void testSetValue() {
try {
PropertyUtils.setValue(Constants.DATASOURCE_ENCRYPTION_ENABLE,"true");
Assert.assertTrue(PropertyUtils.getBoolean(Constants.DATASOURCE_ENCRYPTION_ENABLE));
PropertyUtils.setValue(Constants.DATASOURCE_ENCRYPTION_ENABLE,"false");
Assert.assertFalse(PropertyUtils.getBoolean(Constants.DATASOURCE_ENCRYPTION_ENABLE));
} catch (Exception e) {
Assert.assertTrue(false);
}
}
@Test
public void testWriteContent2File() throws FileNotFoundException {
String filePath = "test/testFile.txt";
String content = "正正正faffdasfasdfas";
FileUtils.writeContent2File(content, filePath);
String fileContent = FileUtils.readFile2Str(new FileInputStream(new File(filePath)));
Assert.assertEquals(content, fileContent);
}
} |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | /*
* Licnsd o h Apach Sofwar Foundaion (ASF) undr on or mor
* conribuor licns agrmns. S h NOTICE fil disribud wih
* his work for addiional informaion rgarding copyrigh ownrship.
* Th ASF licnss his fil o You undr h Apach Licns, Vrsion 2.0
* (h "Licns"); you may no us his fil xcp in complianc wih
* h Licns. You may obain a copy of h Licns a
*
* hp://www.apach.org/licnss/LICENSE-2.0
*
* Unlss rquird by applicabl law or agrd o in wriing, sofwar
* disribud undr h Licns is disribud on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, ihr xprss or implid.
* S h Licns for h spcic languag govrning prmissions and
* limiaions undr h Licns.
*/
packag org.apach.dolphinschdulr.srvr.masr.runnr;
impor saic org.apach.dolphinschdulr.common.Consans.CMDPARAM_COMPLEMENT_DATA_END_DATE;
impor saic org.apach.dolphinschdulr.common.Consans.CMDPARAM_COMPLEMENT_DATA_START_DATE;
impor saic org.apach.dolphinschdulr.common.Consans.CMD_PARAM_RECOVERY_START_NODE_STRING;
impor saic org.apach.dolphinschdulr.common.Consans.CMD_PARAM_START_NODE_NAMES;
impor saic org.apach.dolphinschdulr.common.Consans.DEFAULT_WORKER_GROUP;
impor saic org.apach.dolphinschdulr.common.Consans.LOCAL_PARAMS;
impor saic org.apach.dolphinschdulr.common.Consans.SEC_2_MINUTES_TIME_UNIT;
impor org.apach.dolphinschdulr.common.Consans; |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | impor org.apach.dolphinschdulr.common.nums.CommandTyp;
impor org.apach.dolphinschdulr.common.nums.DpndRsul;
impor org.apach.dolphinschdulr.common.nums.Dirc;
impor org.apach.dolphinschdulr.common.nums.ExcuionSaus;
impor org.apach.dolphinschdulr.common.nums.FailurSragy;
impor org.apach.dolphinschdulr.common.nums.Flag;
impor org.apach.dolphinschdulr.common.nums.Prioriy;
impor org.apach.dolphinschdulr.common.nums.TaskDpndTyp;
impor org.apach.dolphinschdulr.common.graph.DAG;
impor org.apach.dolphinschdulr.common.modl.TaskNod;
impor org.apach.dolphinschdulr.common.modl.TaskNodRlaion;
impor org.apach.dolphinschdulr.common.procss.ProcssDag;
impor org.apach.dolphinschdulr.common.procss.Propry;
impor org.apach.dolphinschdulr.common.hrad.Soppr;
impor org.apach.dolphinschdulr.common.hrad.ThradUils;
impor org.apach.dolphinschdulr.common.uils.CollcionUils;
impor org.apach.dolphinschdulr.common.uils.CommonUils;
impor org.apach.dolphinschdulr.common.uils.DaUils;
impor org.apach.dolphinschdulr.common.uils.JSONUils;
impor org.apach.dolphinschdulr.common.uils.OSUils;
impor org.apach.dolphinschdulr.common.uils.ParamrUils;
impor org.apach.dolphinschdulr.common.uils.SringUils;
impor org.apach.dolphinschdulr.common.uils.VarPoolUils;
impor org.apach.dolphinschdulr.dao.niy.ProcssInsanc;
impor org.apach.dolphinschdulr.dao.niy.ProjcUsr;
impor org.apach.dolphinschdulr.dao.niy.Schdul;
impor org.apach.dolphinschdulr.dao.niy.TaskInsanc;
impor org.apach.dolphinschdulr.dao.uils.DagHlpr;
impor org.apach.dolphinschdulr.rmo.NyRmoingClin;
impor org.apach.dolphinschdulr.srvr.masr.config.MasrConfig; |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | impor org.apach.dolphinschdulr.srvr.uils.AlrManagr;
impor org.apach.dolphinschdulr.srvic.procss.ProcssSrvic;
impor org.apach.dolphinschdulr.srvic.quarz.cron.CronUils;
impor org.apach.dolphinschdulr.srvic.quu.PrTaskInsancPrioriyQuu;
impor org.apach.commons.io.FilUils;
impor java.io.Fil;
impor java.io.IOExcpion;
impor java.x.ParsExcpion;
impor java.uil.ArrayLis;
impor java.uil.Arrays;
impor java.uil.Collcion;
impor java.uil.Da;
impor java.uil.HashMap;
impor java.uil.Iraor;
impor java.uil.Lis;
impor java.uil.Map;
impor java.uil.S;
impor java.uil.concurrn.ConcurrnHashMap;
impor java.uil.concurrn.ExcuorSrvic;
impor java.uil.concurrn.Fuur;
impor java.uil.sram.Collcors;
impor org.slf4j.Loggr;
impor org.slf4j.LoggrFacory;
impor com.googl.common.collc.Liss;
/**
* masr xc hrad,spli dag
*/
public class MasrExcThrad implmns Runnabl {
/**
* loggr of MasrExcThrad |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | */
priva saic final Loggr loggr = LoggrFacory.gLoggr(MasrExcThrad.class);
/**
* runing TaskNod
*/
priva final Map<MasrBasTaskExcThrad, Fuur<Boolan>> acivTaskNod = nw ConcurrnHashMap<>();
/**
* ask xc srvic
*/
priva final ExcuorSrvic askExcSrvic;
/**
* procss insanc
*/
priva ProcssInsanc procssInsanc;
/**
* submi failur nods
*/
priva boolan askFaildSubmi = fals;
/**
* rcovr nod id lis
*/
priva Lis<TaskInsanc> rcovrNodIdLis = nw ArrayLis<>();
/**
* rror ask lis
*/
priva Map<Sring, TaskInsanc> rrorTaskLis = nw ConcurrnHashMap<>();
/**
* compl ask lis
*/
priva Map<Sring, TaskInsanc> complTaskLis = nw ConcurrnHashMap<>(); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | /**
* rady o submi ask quu
*/
priva PrTaskInsancPrioriyQuu radyToSubmiTaskQuu = nw PrTaskInsancPrioriyQuu();
/**
* dpnd faild ask map
*/
priva Map<Sring, TaskInsanc> dpndFaildTask = nw ConcurrnHashMap<>();
/**
* forbiddn ask map
*/
priva Map<Sring, TaskNod> forbiddnTaskLis = nw ConcurrnHashMap<>();
/**
* skip ask map
*/
priva Map<Sring, TaskNod> skipTaskNodLis = nw ConcurrnHashMap<>();
/**
* rcovr olranc faul ask lis
*/
priva Lis<TaskInsanc> rcovrTolrancFaulTaskLis = nw ArrayLis<>();
/**
* alr managr
*/
priva AlrManagr alrManagr;
/**
* h objc of DAG
*/
priva DAG<Sring, TaskNod, TaskNodRlaion> dag;
/**
* procss srvic |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | */
priva ProcssSrvic procssSrvic;
/**
* masr config
*/
priva MasrConfig masrConfig;
/**
*
*/
priva NyRmoingClin nyRmoingClin;
/**
* submi pos nod
*
* @param parnNodNam parn nod nam
*/
priva Map<Sring, Objc> propToValu = nw ConcurrnHashMap<Sring, Objc>();
/**
* consrucor of MasrExcThrad
*
* @param procssInsanc procssInsanc
* @param procssSrvic procssSrvic
* @param nyRmoingClin nyRmoingClin
*/
public MasrExcThrad(ProcssInsanc procssInsanc
, ProcssSrvic procssSrvic
, NyRmoingClin nyRmoingClin
, AlrManagr alrManagr
, MasrConfig masrConfig) {
his.procssSrvic = procssSrvic;
his.procssInsanc = procssInsanc; |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | his.masrConfig = masrConfig;
in masrTaskExcNum = masrConfig.gMasrExcTaskNum();
his.askExcSrvic = ThradUils.nwDamonFixdThradExcuor("Masr-Task-Exc-Thrad",
masrTaskExcNum);
his.nyRmoingClin = nyRmoingClin;
his.alrManagr = alrManagr;
}
@Ovrrid
public void run() {
(procssInsanc == null) {
loggr.info("procss insanc is no xiss");
rurn;
}
(procssInsanc.gSa().ypIsFinishd()) {
loggr.info("procss insanc is don : {}", procssInsanc.gId());
rurn;
}
ry {
(procssInsanc.isComplmnDaa() && Flag.NO == procssInsanc.gIsSubProcss()) {
xcuComplmnProcss();
} ls {
xcuProcss();
}
} cach (Excpion ) {
loggr.rror("masr xc hrad xcpion", );
loggr.rror("procss xcu faild, procss id:{}", procssInsanc.gId()); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | procssInsanc.sSa(ExcuionSaus.FAILURE);
procssInsanc.sEndTim(nw Da());
procssSrvic.updaProcssInsanc(procssInsanc);
} finally {
askExcSrvic.shudown();
posHandl();
}
}
/**
* xcu procss
*
* @hrows Excpion xcpion
*/
priva void xcuProcss() hrows Excpion {
prparProcss();
runProcss();
ndProcss();
}
/**
* xcu complmn procss
*
* @hrows Excpion xcpion
*/
priva void xcuComplmnProcss() hrows Excpion {
Map<Sring, Sring> cmdParam = JSONUils.oMap(procssInsanc.gCommandParam());
Da sarDa = DaUils.gSchdulDa(cmdParam.g(CMDPARAM_COMPLEMENT_DATA_START_DATE));
Da ndDa = DaUils.gSchdulDa(cmdParam.g(CMDPARAM_COMPLEMENT_DATA_END_DATE));
procssSrvic.savProcssInsanc(procssInsanc); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | in procssDfiniionId = procssInsanc.gProcssDfiniionId();
Lis<Schdul> schduls = procssSrvic.quryRlasSchdulrLisByProcssDfiniionId(procssDfiniionId);
Lis<Da> lisDa = Liss.nwLinkdLis();
(!CollcionUils.isEmpy(schduls)) {
for (Schdul schdul : schduls) {
lisDa.addAll(CronUils.gSlfFirDaLis(sarDa, ndDa, schdul.gCronab()));
}
}
Iraor<Da> iraor = null;
Da schdulDa = null;
(!CollcionUils.isEmpy(lisDa)) {
iraor = lisDa.iraor();
schdulDa = iraor.nx();
procssInsanc.sSchdulTim(schdulDa);
procssSrvic.updaProcssInsanc(procssInsanc);
} ls {
schdulDa = procssInsanc.gSchdulTim();
(schdulDa == null) {
schdulDa = sarDa;
}
}
whil (Soppr.isRunning()) {
loggr.info("procss {} sar o complmn {} daa",
procssInsanc.gId(), DaUils.daToSring(schdulDa));
prparProcss();
(dag == null) {
loggr.rror("procss {} dag is null, plas chck ou paramrs",
procssInsanc.gId()); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | procssInsanc.sSa(ExcuionSaus.SUCCESS);
procssSrvic.updaProcssInsanc(procssInsanc);
rurn;
}
runProcss();
ndProcss();
(!procssInsanc.gSa().ypIsSuccss()) {
loggr.info("procss {} sa {}, complmn no complly!",
procssInsanc.gId(), procssInsanc.gSa());
brak;
}
//
(null == iraor) {
//
schdulDa = DaUils.gSomDay(schdulDa, 1);
(schdulDa.afr(ndDa)) {
//
loggr.info("procss {} complmn complly!", procssInsanc.gId());
brak;
}
} ls {
//
(!iraor.hasNx()) {
//
loggr.info("procss {} complmn complly!", procssInsanc.gId());
brak;
}
schdulDa = iraor.nx(); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | }
// flow nd
//
procssInsanc.sSchdulTim(schdulDa);
(cmdParam.conainsKy(Consans.CMD_PARAM_RECOVERY_START_NODE_STRING)) {
cmdParam.rmov(Consans.CMD_PARAM_RECOVERY_START_NODE_STRING);
procssInsanc.sCommandParam(JSONUils.oJsonSring(cmdParam));
}
procssInsanc.sSa(ExcuionSaus.RUNNING_EXECUTION);
procssInsanc.sGlobalParams(ParamrUils.curingGlobalParams(
procssInsanc.gProcssDfiniion().gGlobalParamMap(),
procssInsanc.gProcssDfiniion().gGlobalParamLis(),
CommandTyp.COMPLEMENT_DATA, procssInsanc.gSchdulTim()));
procssInsanc.sId(0);
procssInsanc.sSarTim(nw Da());
procssInsanc.sEndTim(null);
procssSrvic.savProcssInsanc(procssInsanc);
}
}
/**
* prpar procss paramr
*
* @hrows Excpion xcpion
*/
priva void prparProcss() hrows Excpion {
//
buildFlowDag();
//
iniTaskQuu();
loggr.info("prpar procss :{} nd", procssInsanc.gId()); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | }
/**
* procss nd handl
*/
priva void ndProcss() {
procssInsanc.sEndTim(nw Da());
procssSrvic.updaProcssInsanc(procssInsanc);
(procssInsanc.gSa().ypIsWaiingThrad()) {
procssSrvic.craRcovryWaiingThradCommand(null, procssInsanc);
}
Lis<TaskInsanc> askInsancs = procssSrvic.findValidTaskLisByProcssId(procssInsanc.gId());
ProjcUsr projcUsr = procssSrvic.quryProjcWihUsrByProcssInsancId(procssInsanc.gId());
alrManagr.sndAlrProcssInsanc(procssInsanc, askInsancs, projcUsr);
}
/**
*
*
* @hrows Excpion xcpion
*/
priva void buildFlowDag() hrows Excpion {
rcovrNodIdLis = gSarTaskInsancLis(procssInsanc.gCommandParam());
forbiddnTaskLis = DagHlpr.gForbiddnTaskNodMaps(procssInsanc.gProcssInsancJson());
//
Lis<Sring> rcovryNamLis = gRcovryNodNamLis();
Lis<Sring> sarNodNamLis = parsSarNodNam(procssInsanc.gCommandParam());
ProcssDag procssDag = gnraFlowDag(procssInsanc.gProcssInsancJson(),
sarNodNamLis, rcovryNamLis, procssInsanc.gTaskDpndTyp());
(procssDag == null) {
loggr.rror("procssDag is null");
rurn; |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | }
//
dag = DagHlpr.buildDagGraph(procssDag);
}
/**
*
*/
priva void iniTaskQuu() {
askFaildSubmi = fals;
acivTaskNod.clar();
dpndFaildTask.clar();
complTaskLis.clar();
rrorTaskLis.clar();
Lis<TaskInsanc> askInsancLis = procssSrvic.findValidTaskLisByProcssId(procssInsanc.gId());
for (TaskInsanc ask : askInsancLis) {
(ask.isTaskCompl()) {
complTaskLis.pu(ask.gNam(), ask);
}
(ask.isCondiionsTask() || DagHlpr.havCondiionsAfrNod(ask.gNam(), dag)) {
coninu;
}
(ask.gSa().ypIsFailur() && !ask.askCanRry()) {
rrorTaskLis.pu(ask.gNam(), ask);
}
}
}
/**
* procss pos handl
*/
priva void posHandl() { |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | loggr.info("dvlop mod is: {}", CommonUils.isDvlopMod());
(!CommonUils.isDvlopMod()) {
//
Sring xcLocalPah = org.apach.dolphinschdulr.common.uils.FilUils
.gProcssExcDir(procssInsanc.gProcssDfiniion().gProjcId(),
procssInsanc.gProcssDfiniionId(),
procssInsanc.gId());
ry {
FilUils.dlDircory(nw Fil(xcLocalPah));
} cach (IOExcpion ) {
loggr.rror("dl xc dir faild ", );
}
}
}
/**
* submi ask o xcu
*
* @param askInsanc ask insanc
* @rurn TaskInsanc
*/
priva TaskInsanc submiTaskExc(TaskInsanc askInsanc) {
MasrBasTaskExcThrad absracExcThrad = null;
(askInsanc.isSubProcss()) {
absracExcThrad = nw SubProcssTaskExcThrad(askInsanc);
} ls (askInsanc.isDpndTask()) {
absracExcThrad = nw DpndnTaskExcThrad(askInsanc);
} ls (askInsanc.isCondiionsTask()) {
absracExcThrad = nw CondiionsTaskExcThrad(askInsanc);
} ls {
absracExcThrad = nw MasrTaskExcThrad(askInsanc); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | }
Fuur<Boolan> fuur = askExcSrvic.submi(absracExcThrad);
acivTaskNod.puIfAbsn(absracExcThrad, fuur);
rurn absracExcThrad.gTaskInsanc();
}
/**
* find ask insanc in db.
* in cas submi mor han on sam nam ask in h sam im.
*
* @param askNam ask nam
* @rurn TaskInsanc
*/
priva TaskInsanc findTaskIfExiss(Sring askNam) {
Lis<TaskInsanc> askInsancLis = procssSrvic.findValidTaskLisByProcssId(his.procssInsanc.gId());
for (TaskInsanc askInsanc : askInsancLis) {
(askInsanc.gNam().quals(askNam)) {
rurn askInsanc;
}
}
rurn null;
}
/**
* ncapsulaion ask
*
* @param procssInsanc procss insanc
* @param nodNam nod nam
* @rurn TaskInsanc
*/
priva TaskInsanc craTaskInsanc(ProcssInsanc procssInsanc, Sring nodNam,
TaskNod askNod) { |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | //
his.procssInsanc = his.procssSrvic.findProcssInsancById(his.procssInsanc.gId());
TaskInsanc askInsanc = findTaskIfExiss(nodNam);
(askInsanc == null) {
askInsanc = nw TaskInsanc();
// ask nam
askInsanc.sNam(nodNam);
//
askInsanc.sProcssDfiniionId(procssInsanc.gProcssDfiniionId());
//
askInsanc.sSa(ExcuionSaus.SUBMITTED_SUCCESS);
//
askInsanc.sProcssInsancId(procssInsanc.gId());
//
askInsanc.sTaskJson(JSONUils.oJsonSring(askNod));
//
askInsanc.sTaskTyp(askNod.gTyp());
//
askInsanc.sAlrFlag(Flag.NO);
//
askInsanc.sSarTim(null);
//
askInsanc.sFlag(Flag.YES);
//
askInsanc.sRryTims(0);
//
askInsanc.sMaxRryTims(askNod.gMaxRryTims());
//
askInsanc.sRryInrval(askNod.gRryInrval());
// |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | (askNod.gTaskInsancPrioriy() == null) {
askInsanc.sTaskInsancPrioriy(Prioriy.MEDIUM);
} ls {
askInsanc.sTaskInsancPrioriy(askNod.gTaskInsancPrioriy());
}
Sring procssWorkrGroup = procssInsanc.gWorkrGroup();
procssWorkrGroup = SringUils.isBlank(procssWorkrGroup) ? DEFAULT_WORKER_GROUP : procssWorkrGroup;
Sring askWorkrGroup = SringUils.isBlank(askNod.gWorkrGroup()) ? procssWorkrGroup : askNod.gWorkrGroup();
(!procssWorkrGroup.quals(DEFAULT_WORKER_GROUP) && askWorkrGroup.quals(DEFAULT_WORKER_GROUP)) {
askInsanc.sWorkrGroup(procssWorkrGroup);
} ls {
askInsanc.sWorkrGroup(askWorkrGroup);
}
//
sProcssGlobal(askNod, askInsanc);
//
askInsanc.sDlayTim(askNod.gDlayTim());
}
rurn askInsanc;
}
priva void sProcssGlobal(TaskNod askNod, TaskInsanc askInsanc) {
Sring globalParams = his.procssInsanc.gGlobalParams();
(SringUils.isNoEmpy(globalParams)) {
Map<Sring, Sring> globalMap = procssSrvic.gGlobalParamMap(globalParams);
(globalMap != null && globalMap.siz() != 0) {
sGlobalMapToTask(askNod, askInsanc, globalMap);
}
}
}
priva void sGlobalMapToTask(TaskNod askNod, TaskInsanc askInsanc, Map<Sring, Sring> globalMap) { |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | //
Map<Sring, Objc> rsul = JSONUils.oMap(askNod.gParams(), Sring.class, Objc.class);
Objc localParams = rsul.g(LOCAL_PARAMS);
(localParams != null) {
Lis<Propry> allParam = JSONUils.oLis(JSONUils.oJsonSring(localParams), Propry.class);
for (Propry info : allParam) {
(info.gDirc().quals(Dirc.IN)) {
Sring paramNam = info.gProp();
Sring valu = globalMap.g(paramNam);
(SringUils.isNoEmpy(valu)) {
info.sValu(valu);
}
}
}
rsul.pu(LOCAL_PARAMS, allParam);
askNod.sParams(JSONUils.oJsonSring(rsul));
//
askInsanc.sTaskJson(JSONUils.oJsonSring(askNod));
}
}
priva void submiPosNod(Sring parnNodNam) {
S<Sring> submiTaskNodLis = DagHlpr.parsPosNods(parnNodNam, skipTaskNodLis, dag, complTaskLis);
Lis<TaskInsanc> askInsancs = nw ArrayLis<>();
for (Sring askNod : submiTaskNodLis) {
ry {
VarPoolUils.convrVarPoolToMap(propToValu, procssInsanc.gVarPool());
} cach (ParsExcpion ) {
loggr.rror("pars {} xcpion", procssInsanc.gVarPool(), );
hrow nw RunimExcpion();
} |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | TaskNod askNodObjc = dag.gNod(askNod);
VarPoolUils.sTaskNodLocalParams(askNodObjc, propToValu);
askInsancs.add(craTaskInsanc(procssInsanc, askNod,
askNodObjc));
}
//
for (TaskInsanc ask : askInsancs) {
(radyToSubmiTaskQuu.conains(ask)) {
coninu;
}
(complTaskLis.conainsKy(ask.gNam())) {
loggr.info("ask {} has alrady run succss", ask.gNam());
coninu;
}
(ask.gSa().ypIsPaus() || ask.gSa().ypIsCancl()) {
loggr.info("ask {} soppd, h sa is {}", ask.gNam(), ask.gSa());
} ls {
addTaskToSandByLis(ask);
}
}
}
/**
* drmin whhr h dpndncis of h ask nod ar compl
*
* @rurn DpndRsul
*/
priva DpndRsul isTaskDpsCompl(Sring askNam) {
Collcion<Sring> sarNods = dag.gBginNod();
//
(sarNods.conains(askNam)) { |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | rurn DpndRsul.SUCCESS;
}
TaskNod askNod = dag.gNod(askNam);
Lis<Sring> dpNamLis = askNod.gDpLis();
for (Sring dpsNod : dpNamLis) {
(!dag.conainsNod(dpsNod)
|| forbiddnTaskLis.conainsKy(dpsNod)
|| skipTaskNodLis.conainsKy(dpsNod)) {
coninu;
}
//
(!complTaskLis.conainsKy(dpsNod)) {
rurn DpndRsul.WAITING;
}
ExcuionSaus dpTaskSa = complTaskLis.g(dpsNod).gSa();
(dpTaskSa.ypIsPaus() || dpTaskSa.ypIsCancl()) {
rurn DpndRsul.WAITING;
}
//
(askNod.isCondiionsTask()) {
coninu;
}
(!dpndTaskSuccss(dpsNod, askNam)) {
rurn DpndRsul.FAILED;
}
}
loggr.info("askNam: {} complDpndTaskLis: {}", askNam, Arrays.oSring(complTaskLis.kyS().oArray()));
rurn DpndRsul.SUCCESS;
}
/** |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | * dpnd nod is compld, bu hr nd chck h condiion ask branch is h nx nod
*/
priva boolan dpndTaskSuccss(Sring dpndNodNam, Sring nxNodNam) {
(dag.gNod(dpndNodNam).isCondiionsTask()) {
//
Lis<Sring> nxTaskLis = DagHlpr.parsCondiionTask(dpndNodNam, skipTaskNodLis, dag, complTaskLis);
(!nxTaskLis.conains(nxNodNam)) {
rurn fals;
}
} ls {
ExcuionSaus dpTaskSa = complTaskLis.g(dpndNodNam).gSa();
(dpTaskSa.ypIsFailur()) {
rurn fals;
}
}
rurn ru;
}
/**
* qury ask insanc by compl sa
*
* @param sa sa
* @rurn ask insanc lis
*/
priva Lis<TaskInsanc> gComplTaskBySa(ExcuionSaus sa) {
Lis<TaskInsanc> rsulLis = nw ArrayLis<>();
for (Map.Enry<Sring, TaskInsanc> nry : complTaskLis.nryS()) {
(nry.gValu().gSa() == sa) {
rsulLis.add(nry.gValu());
}
} |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | rurn rsulLis;
}
/**
* whr hr ar ongoing asks
*
* @param sa sa
* @rurn ExcuionSaus
*/
priva ExcuionSaus runningSa(ExcuionSaus sa) {
(sa == ExcuionSaus.READY_STOP
|| sa == ExcuionSaus.READY_PAUSE
|| sa == ExcuionSaus.WAITTING_THREAD
|| sa == ExcuionSaus.DELAY_EXECUTION) {
//
rurn sa;
} ls {
rurn ExcuionSaus.RUNNING_EXECUTION;
}
}
/**
* xiss failur ask,conains submi failur、dpndncy failur,xcu failur(rry afr)
*
* @rurn Boolan whhr has faild ask
*/
priva boolan hasFaildTask() {
(his.askFaildSubmi) {
rurn ru;
}
(his.rrorTaskLis.siz() > 0) {
rurn ru; |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | }
rurn his.dpndFaildTask.siz() > 0;
}
/**
* procss insanc failur
*
* @rurn Boolan whhr procss insanc faild
*/
priva boolan procssFaild() {
(hasFaildTask()) {
(procssInsanc.gFailurSragy() == FailurSragy.END) {
rurn ru;
}
(procssInsanc.gFailurSragy() == FailurSragy.CONTINUE) {
rurn radyToSubmiTaskQuu.siz() == 0 || acivTaskNod.siz() == 0;
}
}
rurn fals;
}
/**
* whhr ask for waiing hrad
*
* @rurn Boolan whhr has waiing hrad ask
*/
priva boolan hasWaiingThradTask() {
Lis<TaskInsanc> waiingLis = gComplTaskBySa(ExcuionSaus.WAITTING_THREAD);
rurn CollcionUils.isNoEmpy(waiingLis);
}
/**
* prpar for paus |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | * 1，faild rry ask in h prparaion quu , rurns o failur dircly
* 2，xiss paus ask，complmn no compld, pnding submission of asks, rurn o suspnsion
* 3，succss
*
* @rurn ExcuionSaus
*/
priva ExcuionSaus procssRadyPaus() {
(hasRryTaskInSandBy()) {
rurn ExcuionSaus.FAILURE;
}
Lis<TaskInsanc> pausLis = gComplTaskBySa(ExcuionSaus.PAUSE);
(CollcionUils.isNoEmpy(pausLis)
|| !isComplmnEnd()
|| radyToSubmiTaskQuu.siz() > 0) {
rurn ExcuionSaus.PAUSE;
} ls {
rurn ExcuionSaus.SUCCESS;
}
}
/**
* gnra h las procss insanc saus by h asks sa
*
* @rurn procss insanc xcuion saus
*/
priva ExcuionSaus gProcssInsancSa() {
ProcssInsanc insanc = procssSrvic.findProcssInsancById(procssInsanc.gId());
ExcuionSaus sa = insanc.gSa();
(acivTaskNod.siz() > 0 || hasRryTaskInSandBy()) {
// aciv a
rurn runningSa(sa); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | }
// procss failur
(procssFaild()) {
rurn ExcuionSaus.FAILURE;
}
// waiing hrad
(hasWaiingThradTask()) {
rurn ExcuionSaus.WAITTING_THREAD;
}
// paus
(sa == ExcuionSaus.READY_PAUSE) {
rurn procssRadyPaus();
}
// sop
(sa == ExcuionSaus.READY_STOP) {
Lis<TaskInsanc> sopLis = gComplTaskBySa(ExcuionSaus.STOP);
Lis<TaskInsanc> killLis = gComplTaskBySa(ExcuionSaus.KILL);
(CollcionUils.isNoEmpy(sopLis)
|| CollcionUils.isNoEmpy(killLis)
|| !isComplmnEnd()) {
rurn ExcuionSaus.STOP;
} ls {
rurn ExcuionSaus.SUCCESS;
}
}
// succss
(sa == ExcuionSaus.RUNNING_EXECUTION) {
Lis<TaskInsanc> killTasks = gComplTaskBySa(ExcuionSaus.KILL);
(radyToSubmiTaskQuu.siz() > 0) {
//asks curr |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | rurn ExcuionSaus.RUNNING_EXECUTION;
} ls (CollcionUils.isNoEmpy(killTasks)) {
// asks may
rurn ExcuionSaus.FAILURE;
} ls {
// h w
rurn ExcuionSaus.SUCCESS;
}
}
rurn sa;
}
/**
* whhr sandby ask lis hav rry asks
*/
priva boolan rryTaskExiss() {
boolan rsul = fals;
for (Iraor<TaskInsanc> ir = radyToSubmiTaskQuu.iraor(); ir.hasNx(); ) {
TaskInsanc ask = ir.nx();
(ask.gSa().ypIsFailur()) {
rsul = ru;
brak;
}
}
rurn rsul;
}
/**
* whhr complmn nd
*
* @rurn Boolan whhr is complmn nd
*/ |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | priva boolan isComplmnEnd() {
(!procssInsanc.isComplmnDaa()) {
rurn ru;
}
ry {
Map<Sring, Sring> cmdParam = JSONUils.oMap(procssInsanc.gCommandParam());
Da ndTim = DaUils.gSchdulDa(cmdParam.g(CMDPARAM_COMPLEMENT_DATA_END_DATE));
rurn procssInsanc.gSchdulTim().quals(ndTim);
} cach (Excpion ) {
loggr.rror("complmn nd faild ", );
rurn fals;
}
}
/**
* updaProcssInsanc procss insanc sa
* afr ach bach of asks is xcud, h saus of h procss insanc is updad
*/
priva void updaProcssInsancSa() {
ExcuionSaus sa = gProcssInsancSa();
(procssInsanc.gSa() != sa) {
loggr.info(
"work flow procss insanc [id: {}, nam:{}], sa chang from {} o {}, cmd yp: {}",
procssInsanc.gId(), procssInsanc.gNam(),
procssInsanc.gSa(), sa,
procssInsanc.gCommandTyp());
ProcssInsanc insanc = procssSrvic.findProcssInsancById(procssInsanc.gId());
insanc.sSa(sa);
insanc.sProcssDfiniion(procssInsanc.gProcssDfiniion());
procssSrvic.updaProcssInsanc(insanc);
procssInsanc = insanc; |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | }
}
/**
* g ask dpndncy rsul
*
* @param askInsanc ask insanc
* @rurn DpndRsul
*/
priva DpndRsul gDpndRsulForTask(TaskInsanc askInsanc) {
rurn isTaskDpsCompl(askInsanc.gNam());
}
/**
* add ask o sandby lis
*
* @param askInsanc ask insanc
*/
priva void addTaskToSandByLis(TaskInsanc askInsanc) {
loggr.info("add ask o sand by lis: {}", askInsanc.gNam());
ry {
radyToSubmiTaskQuu.pu(askInsanc);
} cach (Excpion ) {
loggr.rror("add ask insanc o radyToSubmiTaskQuu rror");
}
}
/**
* rmov ask from sand by lis
*
* @param askInsanc ask insanc
*/
priva void rmovTaskFromSandbyLis(TaskInsanc askInsanc) { |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | loggr.info("rmov ask from sand by lis: {}", askInsanc.gNam());
ry {
radyToSubmiTaskQuu.rmov(askInsanc);
} cach (Excpion ) {
loggr.rror("rmov ask insanc from radyToSubmiTaskQuu rror");
}
}
/**
* has rry ask in sandby
*
* @rurn Boolan whhr has rry ask in sandby
*/
priva boolan hasRryTaskInSandBy() {
for (Iraor<TaskInsanc> ir = radyToSubmiTaskQuu.iraor(); ir.hasNx(); ) {
(ir.nx().gSa().ypIsFailur()) {
rurn ru;
}
}
rurn fals;
}
/**
* submi and wach h asks, unil h work flow sop
*/
priva void runProcss() {
// submi sar nod
submiPosNod(null);
boolan sndTimWarning = fals;
whil (!procssInsanc.isProcssInsancSop() && Soppr.isRunning()) {
// snd warn
(!sndTimWarning && chckProcssTimOu(procssInsanc)) { |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | alrManagr.sndProcssTimouAlr(procssInsanc,
procssSrvic.findProcssDfinById(procssInsanc.gProcssDfiniionId()));
sndTimWarning = ru;
}
for (Map.Enry<MasrBasTaskExcThrad, Fuur<Boolan>> nry : acivTaskNod.nryS()) {
Fuur<Boolan> fuur = nry.gValu();
TaskInsanc ask = nry.gKy().gTaskInsanc();
(!fuur.isDon()) {
coninu;
}
// nod moni
ask = his.procssSrvic.findTaskInsancById(ask.gId());
(ask == null) {
his.askFaildSubmi = ru;
acivTaskNod.rmov(nry.gKy());
coninu;
}
// nod moni
(ask.gSa().ypIsFinishd()) {
acivTaskNod.rmov(nry.gKy());
}
loggr.info("ask :{}, id:{} compl, sa is {} ",
ask.gNam(), ask.gId(), ask.gSa());
// nod succ
(ask.gSa() == ExcuionSaus.SUCCESS) {
procssInsanc = procssSrvic.findProcssInsancById(procssInsanc.gId());
procssInsanc.sVarPool(ask.gVarPool());
procssSrvic.updaProcssInsanc(procssInsanc);
complTaskLis.pu(ask.gNam(), ask);
submiPosNod(ask.gNam()); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | coninu;
}
// nod fail
(ask.gSa().ypIsFailur()) {
(ask.gSa() == ExcuionSaus.NEED_FAULT_TOLERANCE) {
his.rcovrTolrancFaulTaskLis.add(ask);
}
(ask.askCanRry()) {
addTaskToSandByLis(ask);
} ls {
complTaskLis.pu(ask.gNam(), ask);
(ask.isCondiionsTask()
|| DagHlpr.havCondiionsAfrNod(ask.gNam(), dag)) {
submiPosNod(ask.gNam());
} ls {
rrorTaskLis.pu(ask.gNam(), ask);
(procssInsanc.gFailurSragy() == FailurSragy.END) {
killThOhrTasks();
}
}
}
coninu;
}
// ohr sa
complTaskLis.pu(ask.gNam(), ask);
}
// snd alr
(CollcionUils.isNoEmpy(his.rcovrTolrancFaulTaskLis)) {
alrManagr.sndAlrWorkrTolrancFaul(procssInsanc, rcovrTolrancFaulTaskLis);
his.rcovrTolrancFaulTaskLis.clar(); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | }
// updaPro
// failur p
// a ask
// chck
(rrorTaskLis.siz() > 0) {
for (Map.Enry<Sring, TaskInsanc> nry : complTaskLis.nryS()) {
TaskInsanc complTask = nry.gValu();
(complTask.gSa() == ExcuionSaus.PAUSE) {
complTask.sSa(ExcuionSaus.KILL);
complTaskLis.pu(nry.gKy(), complTask);
procssSrvic.updaTaskInsanc(complTask);
}
}
for (Map.Enry<Sring, TaskInsanc> nry : rrorTaskLis.nryS()) {
TaskInsanc rrorTask = nry.gValu();
TaskInsanc currnTask = procssSrvic.findTaskInsancById(rrorTask.gId());
(currnTask == null) {
coninu;
}
// for nods
(rrorTask.gSa().ypIsFailur() && currnTask.gSa().quals(ExcuionSaus.FORCED_SUCCESS)) {
// upda s
rrorTask.sSa(currnTask.gSa());
loggr.info("ask: {} has bn forcd succss, rmov i from rror ask lis", rrorTask.gNam());
rrorTaskLis.rmov(rrorTask.gNam());
// submi po
submiPosNod(rrorTask.gNam());
}
} |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | }
(canSubmiTaskToQuu()) {
submiSandByTask();
}
ry {
Thrad.slp(Consans.SLEEP_TIME_MILLIS);
} cach (InrrupdExcpion ) {
loggr.rror(.gMssag(), );
Thrad.currnThrad().inrrup();
}
updaProcssInsancSa();
}
loggr.info("procss:{} nd, sa :{}", procssInsanc.gId(), procssInsanc.gSa());
}
/**
* whhr chck procss im ou
*
* @param procssInsanc ask insanc
* @rurn ru im ou of procss insanc > running im of procss insanc
*/
priva boolan chckProcssTimOu(ProcssInsanc procssInsanc) {
(procssInsanc.gTimou() == 0) {
rurn fals;
}
Da now = nw Da();
long runningTim = DaUils.dfMin(now, procssInsanc.gSarTim());
rurn runningTim > procssInsanc.gTimou();
}
/**
* whhr can submi ask o quu |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | *
* @rurn boolan
*/
priva boolan canSubmiTaskToQuu() {
rurn OSUils.chckRsourc(masrConfig.gMasrMaxCpuloadAvg(), masrConfig.gMasrRsrvdMmory());
}
/**
* clos h on going asks
*/
priva void killThOhrTasks() {
loggr.info("kill calld on : {}, num: {}", procssInsanc.gId(),
acivTaskNod.siz());
for (Map.Enry<MasrBasTaskExcThrad, Fuur<Boolan>> nry : acivTaskNod.nryS()) {
MasrBasTaskExcThrad askExcThrad = nry.gKy();
Fuur<Boolan> fuur = nry.gValu();
TaskInsanc askInsanc = askExcThrad.gTaskInsanc();
askInsanc = procssSrvic.findTaskInsancById(askInsanc.gId());
(askInsanc != null && askInsanc.gSa().ypIsFinishd()) {
coninu;
}
(!fuur.isDon()) {
// rcord ki
loggr.info("kill procss insanc, id: {}, ask: {}", procssInsanc.gId(), askExcThrad.gTaskInsanc().gId());
// kill nod
askExcThrad.kill();
}
}
}
/**
* whhr h rry inrval is imd ou |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | *
* @param askInsanc ask insanc
* @rurn Boolan
*/
priva boolan rryTaskInrvalOvrTim(TaskInsanc askInsanc) {
(askInsanc.gSa() != ExcuionSaus.FAILURE) {
rurn ru;
}
(askInsanc.gId() == 0
||
askInsanc.gMaxRryTims() == 0
||
askInsanc.gRryInrval() == 0) {
rurn ru;
}
Da now = nw Da();
long faildTimInrval = DaUils.dfrSc(now, askInsanc.gEndTim());
// ask rry dos no ovr im, rurn fals
rurn askInsanc.gRryInrval() * SEC_2_MINUTES_TIME_UNIT < faildTimInrval;
}
/**
* handling h lis of asks o b submid
*/
priva void submiSandByTask() {
ry {
in lngh = radyToSubmiTaskQuu.siz();
for (in i = 0; i < lngh; i++) {
TaskInsanc ask = radyToSubmiTaskQuu.pk();
// sop ask
(ask.askCanRry()) { |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | TaskInsanc rryTask = procssSrvic.findTaskInsancById(ask.gId());
(rryTask != null && rryTask.gSa().quals(ExcuionSaus.FORCED_SUCCESS)) {
ask.sSa(rryTask.gSa());
loggr.info("ask: {} has bn forcd succss, pu i ino compl ask lis and sop rrying", ask.gNam());
rmovTaskFromSandbyLis(ask);
complTaskLis.pu(ask.gNam(), ask);
submiPosNod(ask.gNam());
coninu;
}
}
DpndRsul dpndRsul = gDpndRsulForTask(ask);
(DpndRsul.SUCCESS == dpndRsul) {
(rryTaskInrvalOvrTim(ask)) {
submiTaskExc(ask);
rmovTaskFromSandbyLis(ask);
}
} ls (DpndRsul.FAILED == dpndRsul) {
// h d
dpndFaildTask.pu(ask.gNam(), ask);
rmovTaskFromSandbyLis(ask);
loggr.info("ask {},id:{} dpnd rsul : {}", ask.gNam(), ask.gId(), dpndRsul);
}
}
} cach (Excpion ) {
loggr.rror("submi sandby ask rror", );
}
}
/**
* g rcovry ask insanc
* |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | * @param askId ask id
* @rurn rcovry ask insanc
*/
priva TaskInsanc gRcovryTaskInsanc(Sring askId) {
(!SringUils.isNoEmpy(askId)) {
rurn null;
}
ry {
Ingr inId = Ingr.valuOf(askId);
TaskInsanc ask = procssSrvic.findTaskInsancById(inId);
(ask == null) {
loggr.rror("sar nod id canno b found: {}", askId);
} ls {
rurn ask;
}
} cach (Excpion ) {
loggr.rror("g rcovry ask insanc faild ", );
}
rurn null;
}
/**
* g sar ask insanc lis
*
* @param cmdParam command param
* @rurn ask insanc lis
*/
priva Lis<TaskInsanc> gSarTaskInsancLis(Sring cmdParam) {
Lis<TaskInsanc> insancLis = nw ArrayLis<>();
Map<Sring, Sring> paramMap = JSONUils.oMap(cmdParam);
(paramMap != null && paramMap.conainsKy(CMD_PARAM_RECOVERY_START_NODE_STRING)) { |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | Sring[] idLis = paramMap.g(CMD_PARAM_RECOVERY_START_NODE_STRING).spli(Consans.COMMA);
for (Sring nodId : idLis) {
TaskInsanc ask = gRcovryTaskInsanc(nodId);
(ask != null) {
insancLis.add(ask);
}
}
}
rurn insancLis;
}
/**
* pars "SarNodNamLis" from cmd param
*
* @param cmdParam command param
* @rurn sar nod nam lis
*/
priva Lis<Sring> parsSarNodNam(Sring cmdParam) {
Lis<Sring> sarNodNamLis = nw ArrayLis<>();
Map<Sring, Sring> paramMap = JSONUils.oMap(cmdParam);
(paramMap == null) {
rurn sarNodNamLis;
}
(paramMap.conainsKy(CMD_PARAM_START_NODE_NAMES)) {
sarNodNamLis = Arrays.asLis(paramMap.g(CMD_PARAM_START_NODE_NAMES).spli(Consans.COMMA));
}
rurn sarNodNamLis;
}
/**
* gnra sar nod nam lis from parsing command param;
* "SarNodIdLis" xiss in command param, rurn SarNodIdLis |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterExecThread.java | *
* @rurn rcovry nod nam lis
*/
priva Lis<Sring> gRcovryNodNamLis() {
Lis<Sring> rcovryNodNamLis = nw ArrayLis<>();
(CollcionUils.isNoEmpy(rcovrNodIdLis)) {
for (TaskInsanc ask : rcovrNodIdLis) {
rcovryNodNamLis.add(ask.gNam());
}
}
rurn rcovryNodNamLis;
}
/**
* gnra flow dag
*
* @param procssDfiniionJson procss dfiniion json
* @param sarNodNamLis sar nod nam lis
* @param rcovryNodNamLis rcovry nod nam lis
* @param dpNodTyp dpnd nod yp
* @rurn ProcssDag procss dag
* @hrows Excpion xcpion
*/
public ProcssDag gnraFlowDag(Sring procssDfiniionJson,
Lis<Sring> sarNodNamLis,
Lis<Sring> rcovryNodNamLis,
TaskDpndTyp dpNodTyp) hrows Excpion {
rurn DagHlpr.gnraFlowDag(procssDfiniionJson, sarNodNamLis, rcovryNodNamLis, dpNodTyp);
}
} |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/processor/TaskExecuteProcessor.java | /*
* 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.
*/
package org.apache.dolphinscheduler.server.worker.processor;
import org.apache.dolphinscheduler.common.enums.Event;
import org.apache.dolphinscheduler.common.enums.ExecutionStatus;
import org.apache.dolphinscheduler.common.enums.TaskType;
import org.apache.dolphinscheduler.common.utils.DateUtils; |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/processor/TaskExecuteProcessor.java | import org.apache.dolphinscheduler.common.utils.FileUtils;
import org.apache.dolphinscheduler.common.utils.JSONUtils;
import org.apache.dolphinscheduler.common.utils.LoggerUtils;
import org.apache.dolphinscheduler.common.utils.NetUtils;
import org.apache.dolphinscheduler.common.utils.OSUtils;
import org.apache.dolphinscheduler.common.utils.Preconditions;
import org.apache.dolphinscheduler.remote.command.Command;
import org.apache.dolphinscheduler.remote.command.CommandType;
import org.apache.dolphinscheduler.remote.command.TaskExecuteAckCommand;
import org.apache.dolphinscheduler.remote.command.TaskExecuteRequestCommand;
import org.apache.dolphinscheduler.remote.processor.NettyRequestProcessor;
import org.apache.dolphinscheduler.server.entity.TaskExecutionContext;
import org.apache.dolphinscheduler.server.utils.LogUtils;
import org.apache.dolphinscheduler.server.worker.cache.ResponceCache;
import org.apache.dolphinscheduler.server.worker.cache.TaskExecutionContextCacheManager;
import org.apache.dolphinscheduler.server.worker.cache.impl.TaskExecutionContextCacheManagerImpl;
import org.apache.dolphinscheduler.server.worker.config.WorkerConfig;
import org.apache.dolphinscheduler.server.worker.runner.TaskExecuteThread;
import org.apache.dolphinscheduler.server.worker.runner.WorkerManagerThread;
import org.apache.dolphinscheduler.service.alert.AlertClientService;
import org.apache.dolphinscheduler.service.bean.SpringApplicationContext;
import java.util.Date;
import java.util.Optional;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import io.netty.channel.Channel;
/**
* worker request processor
*/
public class TaskExecuteProcessor implements NettyRequestProcessor { |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/processor/TaskExecuteProcessor.java | private static final Logger logger = LoggerFactory.getLogger(TaskExecuteProcessor.class);
/**
* worker config
*/
private final WorkerConfig workerConfig;
/**
* task callback service
*/
private final TaskCallbackService taskCallbackService;
/**
* alert client service
*/
private AlertClientService alertClientService;
/**
* taskExecutionContextCacheManager
*/
private final TaskExecutionContextCacheManager taskExecutionContextCacheManager;
/*
* task execute manager
*/
private final WorkerManagerThread workerManager;
public TaskExecuteProcessor() { |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/processor/TaskExecuteProcessor.java | this.taskCallbackService = SpringApplicationContext.getBean(TaskCallbackService.class);
this.workerConfig = SpringApplicationContext.getBean(WorkerConfig.class);
this.taskExecutionContextCacheManager = SpringApplicationContext.getBean(TaskExecutionContextCacheManagerImpl.class);
this.workerManager = SpringApplicationContext.getBean(WorkerManagerThread.class);
}
/**
* Pre-cache task to avoid extreme situations when kill task. There is no such task in the cache
*
* @param taskExecutionContext task
*/
private void setTaskCache(TaskExecutionContext taskExecutionContext) {
TaskExecutionContext preTaskCache = new TaskExecutionContext();
preTaskCache.setTaskInstanceId(taskExecutionContext.getTaskInstanceId());
taskExecutionContextCacheManager.cacheTaskExecutionContext(preTaskCache);
}
public TaskExecuteProcessor(AlertClientService alertClientService) {
this();
this.alertClientService = alertClientService;
}
@Override
public void process(Channel channel, Command command) {
Preconditions.checkArgument(CommandType.TASK_EXECUTE_REQUEST == command.getType(),
String.format("invalid command type : %s", command.getType()));
TaskExecuteRequestCommand taskRequestCommand = JSONUtils.parseObject(
command.getBody(), TaskExecuteRequestCommand.class);
logger.info("received command : {}", taskRequestCommand);
if (taskRequestCommand == null) {
logger.error("task execute request command is null");
return;
} |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/processor/TaskExecuteProcessor.java | String contextJson = taskRequestCommand.getTaskExecutionContext();
TaskExecutionContext taskExecutionContext = JSONUtils.parseObject(contextJson, TaskExecutionContext.class);
if (taskExecutionContext == null) {
logger.error("task execution context is null");
return;
}
setTaskCache(taskExecutionContext);
Logger taskLogger = LoggerFactory.getLogger(LoggerUtils.buildTaskId(LoggerUtils.TASK_LOGGER_INFO_PREFIX,
taskExecutionContext.getProcessDefineId(),
taskExecutionContext.getProcessInstanceId(),
taskExecutionContext.getTaskInstanceId()));
taskExecutionContext.setHost(NetUtils.getAddr(workerConfig.getListenPort()));
taskExecutionContext.setLogPath(LogUtils.getTaskLogPath(taskExecutionContext));
String execLocalPath = getExecLocalPath(taskExecutionContext);
logger.info("task instance local execute path : {} ", execLocalPath);
taskExecutionContext.setExecutePath(execLocalPath);
FileUtils.taskLoggerThreadLocal.set(taskLogger);
try {
FileUtils.createWorkDirIfAbsent(execLocalPath);
if (workerConfig.getWorkerTenantAutoCreate()) {
OSUtils.createUserIfAbsent(taskExecutionContext.getTenantCode());
}
} catch (Throwable ex) {
String errorLog = String.format("create execLocalPath : %s", execLocalPath);
LoggerUtils.logError(Optional.of(logger), errorLog, ex);
LoggerUtils.logError(Optional.ofNullable(taskLogger), errorLog, ex);
taskExecutionContextCacheManager.removeByTaskInstanceId(taskExecutionContext.getTaskInstanceId());
} |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/processor/TaskExecuteProcessor.java | FileUtils.taskLoggerThreadLocal.remove();
taskCallbackService.addRemoteChannel(taskExecutionContext.getTaskInstanceId(),
new NettyRemoteChannel(channel, command.getOpaque()));
long remainTime = DateUtils.getRemainTime(taskExecutionContext.getFirstSubmitTime(), taskExecutionContext.getDelayTime() * 60L);
if (remainTime > 0) {
logger.info("delay the execution of task instance {}, delay time: {} s", taskExecutionContext.getTaskInstanceId(), remainTime);
taskExecutionContext.setCurrentExecutionStatus(ExecutionStatus.DELAY_EXECUTION);
taskExecutionContext.setStartTime(null);
} else {
taskExecutionContext.setCurrentExecutionStatus(ExecutionStatus.RUNNING_EXECUTION);
taskExecutionContext.setStartTime(new Date());
}
this.doAck(taskExecutionContext);
if (!workerManager.offer(new TaskExecuteThread(taskExecutionContext, taskCallbackService, taskLogger, alertClientService))) {
logger.info("submit task to manager error, queue is full, queue size is {}", workerManager.getQueueSize());
}
}
private void doAck(TaskExecutionContext taskExecutionContext) {
TaskExecuteAckCommand ackCommand = buildAckCommand(taskExecutionContext);
ResponceCache.get().cache(taskExecutionContext.getTaskInstanceId(), ackCommand.convert2Command(), Event.ACK);
taskCallbackService.sendAck(taskExecutionContext.getTaskInstanceId(), ackCommand.convert2Command());
}
/**
* build ack command
*
* @param taskExecutionContext taskExecutionContext
* @return TaskExecuteAckCommand |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/processor/TaskExecuteProcessor.java | */
private TaskExecuteAckCommand buildAckCommand(TaskExecutionContext taskExecutionContext) {
TaskExecuteAckCommand ackCommand = new TaskExecuteAckCommand();
ackCommand.setTaskInstanceId(taskExecutionContext.getTaskInstanceId());
ackCommand.setStatus(taskExecutionContext.getCurrentExecutionStatus().getCode());
ackCommand.setLogPath(LogUtils.getTaskLogPath(taskExecutionContext));
ackCommand.setHost(taskExecutionContext.getHost());
ackCommand.setStartTime(taskExecutionContext.getStartTime());
if (taskExecutionContext.getTaskType().equals(TaskType.SQL.name()) || taskExecutionContext.getTaskType().equals(TaskType.PROCEDURE.name())) {
ackCommand.setExecutePath(null);
} else {
ackCommand.setExecutePath(taskExecutionContext.getExecutePath());
}
taskExecutionContext.setLogPath(ackCommand.getLogPath());
return ackCommand;
}
/**
* get execute local path
*
* @param taskExecutionContext taskExecutionContext
* @return execute local path
*/
private String getExecLocalPath(TaskExecutionContext taskExecutionContext) {
return FileUtils.getProcessExecDir(taskExecutionContext.getProjectId(),
taskExecutionContext.getProcessDefineId(),
taskExecutionContext.getProcessInstanceId(),
taskExecutionContext.getTaskInstanceId());
}
} |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/runner/TaskExecuteThread.java | /*
* 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.
*/
package org.apache.dolphinscheduler.server.worker.runner;
import org.apache.dolphinscheduler.common.enums.Event;
import org.apache.dolphinscheduler.common.enums.ExecutionStatus;
import org.apache.dolphinscheduler.common.enums.TaskType;
import org.apache.dolphinscheduler.common.model.TaskNode;
import org.apache.dolphinscheduler.common.process.Property;
import org.apache.dolphinscheduler.common.task.TaskTimeoutParameter;
import org.apache.dolphinscheduler.common.utils.CommonUtils;
import org.apache.dolphinscheduler.common.utils.DateUtils;
import org.apache.dolphinscheduler.common.utils.HadoopUtils;
import org.apache.dolphinscheduler.common.utils.JSONUtils;
import org.apache.dolphinscheduler.common.utils.OSUtils;
import org.apache.dolphinscheduler.common.utils.RetryerUtils; |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/runner/TaskExecuteThread.java | import org.apache.dolphinscheduler.remote.command.Command;
import org.apache.dolphinscheduler.remote.command.TaskExecuteAckCommand;
import org.apache.dolphinscheduler.remote.command.TaskExecuteResponseCommand;
import org.apache.dolphinscheduler.server.entity.TaskExecutionContext;
import org.apache.dolphinscheduler.server.worker.cache.ResponceCache;
import org.apache.dolphinscheduler.server.worker.cache.TaskExecutionContextCacheManager;
import org.apache.dolphinscheduler.server.worker.cache.impl.TaskExecutionContextCacheManagerImpl;
import org.apache.dolphinscheduler.server.worker.processor.TaskCallbackService;
import org.apache.dolphinscheduler.server.worker.task.AbstractTask;
import org.apache.dolphinscheduler.server.worker.task.TaskManager;
import org.apache.dolphinscheduler.service.alert.AlertClientService;
import org.apache.dolphinscheduler.service.bean.SpringApplicationContext;
import org.apache.commons.collections.MapUtils;
import java.io.File;
import java.util.Date;
import java.util.HashMap;
import java.util.List;
import java.util.Map;
import java.util.Set;
import java.util.concurrent.Delayed;
import java.util.concurrent.ExecutionException;
import java.util.concurrent.TimeUnit;
import java.util.stream.Collectors;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import com.github.rholder.retry.RetryException;
/**
* task scheduler thread
*/
public class TaskExecuteThread implements Runnable, Delayed { |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/runner/TaskExecuteThread.java | /**
* logger
*/
private final Logger logger = LoggerFactory.getLogger(TaskExecuteThread.class);
/**
* task instance
*/
private TaskExecutionContext taskExecutionContext;
/**
* abstract task |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/runner/TaskExecuteThread.java | */
private AbstractTask task;
/**
* task callback service
*/
private TaskCallbackService taskCallbackService;
/**
* taskExecutionContextCacheManager
*/
private TaskExecutionContextCacheManager taskExecutionContextCacheManager;
/**
* task logger
*/
private Logger taskLogger;
/**
* alert client server
*/
private AlertClientService alertClientService;
/**
* constructor
* @param taskExecutionContext taskExecutionContext
* @param taskCallbackService taskCallbackService
*/
public TaskExecuteThread(TaskExecutionContext taskExecutionContext
, TaskCallbackService taskCallbackService
, Logger taskLogger, AlertClientService alertClientService) {
this.taskExecutionContext = taskExecutionContext;
this.taskCallbackService = taskCallbackService;
this.taskExecutionContextCacheManager = SpringApplicationContext.getBean(TaskExecutionContextCacheManagerImpl.class);
this.taskLogger = taskLogger; |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/runner/TaskExecuteThread.java | this.alertClientService = alertClientService;
}
@Override
public void run() {
TaskExecuteResponseCommand responseCommand = new TaskExecuteResponseCommand(taskExecutionContext.getTaskInstanceId());
try {
logger.info("script path : {}", taskExecutionContext.getExecutePath());
if (!OSUtils.getUserList().contains(taskExecutionContext.getTenantCode())) {
String errorLog = String.format("tenantCode: %s does not exist", taskExecutionContext.getTenantCode());
taskLogger.error(errorLog);
responseCommand.setStatus(ExecutionStatus.FAILURE.getCode());
responseCommand.setEndTime(new Date());
return;
}
TaskNode taskNode = JSONUtils.parseObject(taskExecutionContext.getTaskJson(), TaskNode.class);
if (taskExecutionContext.getStartTime() == null) {
taskExecutionContext.setStartTime(new Date());
}
if (taskExecutionContext.getCurrentExecutionStatus() != ExecutionStatus.RUNNING_EXECUTION) {
changeTaskExecutionStatusToRunning();
}
logger.info("the task begins to execute. task instance id: {}", taskExecutionContext.getTaskInstanceId());
downloadResource(taskExecutionContext.getExecutePath(),
taskExecutionContext.getResources(),
logger);
taskExecutionContext.setTaskParams(taskNode.getParams());
taskExecutionContext.setEnvFile(CommonUtils.getSystemEnvPath()); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/runner/TaskExecuteThread.java | taskExecutionContext.setDefinedParams(getGlobalParamsMap());
setTaskTimeout(taskExecutionContext, taskNode);
taskExecutionContext.setTaskAppId(String.format("%s_%s_%s",
taskExecutionContext.getProcessDefineId(),
taskExecutionContext.getProcessInstanceId(),
taskExecutionContext.getTaskInstanceId()));
task = TaskManager.newTask(taskExecutionContext, taskLogger, alertClientService);
task.init();
task.handle();
task.after();
responseCommand.setStatus(task.getExitStatus().getCode());
responseCommand.setEndTime(new Date());
responseCommand.setProcessId(task.getProcessId());
responseCommand.setAppIds(task.getAppIds());
responseCommand.setVarPool(task.getVarPool());
responseCommand.setResult(task.getResultString());
logger.info("task instance id : {},task final status : {}", taskExecutionContext.getTaskInstanceId(), task.getExitStatus());
} catch (Exception e) {
logger.error("task scheduler failure", e);
kill();
responseCommand.setStatus(ExecutionStatus.FAILURE.getCode());
responseCommand.setEndTime(new Date());
responseCommand.setProcessId(task.getProcessId());
responseCommand.setAppIds(task.getAppIds());
} finally {
taskExecutionContextCacheManager.removeByTaskInstanceId(taskExecutionContext.getTaskInstanceId()); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/runner/TaskExecuteThread.java | ResponceCache.get().cache(taskExecutionContext.getTaskInstanceId(),responseCommand.convert2Command(),Event.RESULT);
taskCallbackService.sendResult(taskExecutionContext.getTaskInstanceId(), responseCommand.convert2Command());
}
}
/**
* get global paras map
* @return
*/
private Map<String, String> getGlobalParamsMap() {
Map<String,String> globalParamsMap = new HashMap<>(16);
String globalParamsStr = taskExecutionContext.getGlobalParams();
if (globalParamsStr != null) {
List<Property> globalParamsList = JSONUtils.toList(globalParamsStr, Property.class);
globalParamsMap.putAll(globalParamsList.stream().collect(Collectors.toMap(Property::getProp, Property::getValue)));
}
return globalParamsMap;
}
/**
* set task timeout
* @param taskExecutionContext TaskExecutionContext
* @param taskNode
*/
private void setTaskTimeout(TaskExecutionContext taskExecutionContext, TaskNode taskNode) {
taskExecutionContext.setTaskTimeout(Integer.MAX_VALUE);
TaskTimeoutParameter taskTimeoutParameter = taskNode.getTaskTimeoutParameter();
if (taskTimeoutParameter.getEnable()) {
taskExecutionContext.setTaskTimeoutStrategy(taskTimeoutParameter.getStrategy().getCode()); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/runner/TaskExecuteThread.java | switch (taskTimeoutParameter.getStrategy()) {
case WARN:
break;
case FAILED:
if (Integer.MAX_VALUE > taskTimeoutParameter.getInterval() * 60) {
taskExecutionContext.setTaskTimeout(taskTimeoutParameter.getInterval() * 60);
}
break;
case WARNFAILED:
if (Integer.MAX_VALUE > taskTimeoutParameter.getInterval() * 60) {
taskExecutionContext.setTaskTimeout(taskTimeoutParameter.getInterval() * 60);
}
break;
default:
logger.error("not support task timeout strategy: {}", taskTimeoutParameter.getStrategy());
throw new IllegalArgumentException("not support task timeout strategy");
}
}
}
/**
* kill task
*/
public void kill() {
if (task != null) {
try {
task.cancelApplication(true);
} catch (Exception e) {
logger.error(e.getMessage(),e);
}
} |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/runner/TaskExecuteThread.java | }
/**
* download resource file
*
* @param execLocalPath
* @param projectRes
* @param logger
*/
private void downloadResource(String execLocalPath,
Map<String,String> projectRes,
Logger logger) throws Exception {
if (MapUtils.isEmpty(projectRes)) {
return;
}
Set<Map.Entry<String, String>> resEntries = projectRes.entrySet();
for (Map.Entry<String,String> resource : resEntries) {
String fullName = resource.getKey();
String tenantCode = resource.getValue();
File resFile = new File(execLocalPath, fullName);
if (!resFile.exists()) {
try {
String resHdfsPath = HadoopUtils.getHdfsResourceFileName(tenantCode, fullName);
logger.info("get resource file from hdfs :{}", resHdfsPath);
HadoopUtils.getInstance().copyHdfsToLocal(resHdfsPath, execLocalPath + File.separator + fullName, false, true);
} catch (Exception e) {
logger.error(e.getMessage(),e);
throw new RuntimeException(e.getMessage());
}
} else { |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/runner/TaskExecuteThread.java | logger.info("file : {} exists ", resFile.getName());
}
}
}
/**
* send an ack to change the status of the task.
*/
private void changeTaskExecutionStatusToRunning() {
taskExecutionContext.setCurrentExecutionStatus(ExecutionStatus.RUNNING_EXECUTION);
Command ackCommand = buildAckCommand().convert2Command();
try {
RetryerUtils.retryCall(() -> {
taskCallbackService.sendAck(taskExecutionContext.getTaskInstanceId(), ackCommand);
return Boolean.TRUE;
});
} catch (ExecutionException | RetryException e) {
logger.error(e.getMessage(), e);
}
}
/**
* build ack command.
*
* @return TaskExecuteAckCommand
*/
private TaskExecuteAckCommand buildAckCommand() {
TaskExecuteAckCommand ackCommand = new TaskExecuteAckCommand();
ackCommand.setTaskInstanceId(taskExecutionContext.getTaskInstanceId());
ackCommand.setStatus(taskExecutionContext.getCurrentExecutionStatus().getCode());
ackCommand.setStartTime(taskExecutionContext.getStartTime());
ackCommand.setLogPath(taskExecutionContext.getLogPath()); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/runner/TaskExecuteThread.java | ackCommand.setHost(taskExecutionContext.getHost());
if (taskExecutionContext.getTaskType().equals(TaskType.SQL.name())
|| taskExecutionContext.getTaskType().equals(TaskType.PROCEDURE.name())) {
ackCommand.setExecutePath(null);
} else {
ackCommand.setExecutePath(taskExecutionContext.getExecutePath());
}
return ackCommand;
}
/**
* get current TaskExecutionContext
* @return TaskExecutionContext
*/
public TaskExecutionContext getTaskExecutionContext() {
return this.taskExecutionContext;
}
@Override
public long getDelay(TimeUnit unit) {
return unit.convert(DateUtils.getRemainTime(taskExecutionContext.getFirstSubmitTime(),
taskExecutionContext.getDelayTime() * 60L), TimeUnit.SECONDS);
}
@Override
public int compareTo(Delayed o) {
if (o == null) {
return 1;
}
return Long.compare(this.getDelay(TimeUnit.MILLISECONDS), o.getDelay(TimeUnit.MILLISECONDS));
}
} |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/test/java/org/apache/dolphinscheduler/server/master/MasterExecThreadTest.java | /*
* 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.
*/
package org.apache.dolphinscheduler.server.master;
import static org.apache.dolphinscheduler.common.Constants.CMDPARAM_COMPLEMENT_DATA_END_DATE;
import static org.apache.dolphinscheduler.common.Constants.CMDPARAM_COMPLEMENT_DATA_START_DATE;
import static org.apache.dolphinscheduler.common.Constants.CMD_PARAM_RECOVERY_START_NODE_STRING;
import static org.apache.dolphinscheduler.common.Constants.CMD_PARAM_START_NODE_NAMES;
import static org.mockito.Mockito.times;
import static org.mockito.Mockito.verify;
import static org.powermock.api.mockito.PowerMockito.mock;
import org.apache.dolphinscheduler.common.enums.CommandType;
import org.apache.dolphinscheduler.common.enums.ExecutionStatus;
import org.apache.dolphinscheduler.common.enums.Flag;
import org.apache.dolphinscheduler.common.graph.DAG; |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/test/java/org/apache/dolphinscheduler/server/master/MasterExecThreadTest.java | import org.apache.dolphinscheduler.common.utils.DateUtils;
import org.apache.dolphinscheduler.common.utils.JSONUtils;
import org.apache.dolphinscheduler.dao.entity.ProcessDefinition;
import org.apache.dolphinscheduler.dao.entity.ProcessInstance;
import org.apache.dolphinscheduler.dao.entity.Schedule;
import org.apache.dolphinscheduler.dao.entity.TaskInstance;
import org.apache.dolphinscheduler.server.master.config.MasterConfig;
import org.apache.dolphinscheduler.server.master.runner.MasterExecThread;
import org.apache.dolphinscheduler.service.process.ProcessService;
import java.lang.reflect.Field;
import java.lang.reflect.Method;
import java.text.ParseException;
import java.util.Collections;
import java.util.HashMap;
import java.util.LinkedList;
import java.util.List;
import java.util.Map;
import org.junit.Assert;
import org.junit.Before;
import org.junit.Test;
import org.junit.runner.RunWith;
import org.mockito.Mockito;
import org.powermock.api.mockito.PowerMockito;
import org.powermock.core.classloader.annotations.PrepareForTest;
import org.powermock.modules.junit4.PowerMockRunner;
import org.springframework.context.ApplicationContext;
/**
* test for MasterExecThread
*/
@RunWith(PowerMockRunner.class) |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/test/java/org/apache/dolphinscheduler/server/master/MasterExecThreadTest.java | @PrepareForTest({MasterExecThread.class})
public class MasterExecThreadTest {
private MasterExecThread masterExecThread;
private ProcessInstance processInstance;
private ProcessService processService;
private int processDefinitionId = 1;
private MasterConfig config;
private ApplicationContext applicationContext;
@Before
public void init() throws Exception {
processService = mock(ProcessService.class);
applicationContext = mock(ApplicationContext.class);
config = new MasterConfig();
config.setMasterExecTaskNum(1);
Mockito.when(applicationContext.getBean(MasterConfig.class)).thenReturn(config);
processInstance = mock(ProcessInstance.class);
Mockito.when(processInstance.getProcessDefinitionId()).thenReturn(processDefinitionId);
Mockito.when(processInstance.getState()).thenReturn(ExecutionStatus.SUCCESS);
Mockito.when(processInstance.getHistoryCmd()).thenReturn(CommandType.COMPLEMENT_DATA.toString());
Mockito.when(processInstance.getIsSubProcess()).thenReturn(Flag.NO);
Mockito.when(processInstance.getScheduleTime()).thenReturn(DateUtils.stringToDate("2020-01-01 00:00:00"));
Map<String, String> cmdParam = new HashMap<>();
cmdParam.put(CMDPARAM_COMPLEMENT_DATA_START_DATE, "2020-01-01 00:00:00");
cmdParam.put(CMDPARAM_COMPLEMENT_DATA_END_DATE, "2020-01-20 23:00:00"); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/test/java/org/apache/dolphinscheduler/server/master/MasterExecThreadTest.java | Mockito.when(processInstance.getCommandParam()).thenReturn(JSONUtils.toJsonString(cmdParam));
ProcessDefinition processDefinition = new ProcessDefinition();
processDefinition.setGlobalParamMap(Collections.EMPTY_MAP);
processDefinition.setGlobalParamList(Collections.EMPTY_LIST);
Mockito.when(processInstance.getProcessDefinition()).thenReturn(processDefinition);
masterExecThread = PowerMockito.spy(new MasterExecThread(
processInstance
, processService
, null, null, config));
Field dag = MasterExecThread.class.getDeclaredField("dag");
dag.setAccessible(true);
dag.set(masterExecThread, new DAG());
PowerMockito.doNothing().when(masterExecThread, "executeProcess");
PowerMockito.doNothing().when(masterExecThread, "postHandle");
PowerMockito.doNothing().when(masterExecThread, "prepareProcess");
PowerMockito.doNothing().when(masterExecThread, "runProcess");
PowerMockito.doNothing().when(masterExecThread, "endProcess");
}
/**
* without schedule
*/
@Test
public void testParallelWithOutSchedule() throws ParseException {
try {
Mockito.when(processService.queryReleaseSchedulerListByProcessDefinitionId(processDefinitionId)).thenReturn(zeroSchedulerList());
Method method = MasterExecThread.class.getDeclaredMethod("executeComplementProcess");
method.setAccessible(true);
method.invoke(masterExecThread); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/test/java/org/apache/dolphinscheduler/server/master/MasterExecThreadTest.java | verify(processService, times(20)).saveProcessInstance(processInstance);
} catch (Exception e) {
e.printStackTrace();
Assert.fail();
}
}
/**
* with schedule
*/
@Test
public void testParallelWithSchedule() {
try {
Mockito.when(processService.queryReleaseSchedulerListByProcessDefinitionId(processDefinitionId)).thenReturn(oneSchedulerList());
Method method = MasterExecThread.class.getDeclaredMethod("executeComplementProcess");
method.setAccessible(true);
method.invoke(masterExecThread);
verify(processService, times(9)).saveProcessInstance(processInstance);
} catch (Exception e) {
Assert.fail();
}
}
@Test
public void testParseStartNodeName() throws ParseException {
try {
Map<String, String> cmdParam = new HashMap<>();
cmdParam.put(CMD_PARAM_START_NODE_NAMES, "t1,t2,t3");
Mockito.when(processInstance.getCommandParam()).thenReturn(JSONUtils.toJsonString(cmdParam));
Class<MasterExecThread> masterExecThreadClass = MasterExecThread.class;
Method method = masterExecThreadClass.getDeclaredMethod("parseStartNodeName", String.class); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/test/java/org/apache/dolphinscheduler/server/master/MasterExecThreadTest.java | method.setAccessible(true);
List<String> nodeNames = (List<String>) method.invoke(masterExecThread, JSONUtils.toJsonString(cmdParam));
Assert.assertEquals(3, nodeNames.size());
} catch (Exception e) {
Assert.fail();
}
}
@Test
public void testRetryTaskIntervalOverTime() {
try {
TaskInstance taskInstance = new TaskInstance();
taskInstance.setId(0);
taskInstance.setMaxRetryTimes(0);
taskInstance.setRetryInterval(0);
taskInstance.setState(ExecutionStatus.FAILURE);
Class<MasterExecThread> masterExecThreadClass = MasterExecThread.class;
Method method = masterExecThreadClass.getDeclaredMethod("retryTaskIntervalOverTime", TaskInstance.class);
method.setAccessible(true);
Assert.assertTrue((Boolean) method.invoke(masterExecThread, taskInstance));
} catch (Exception e) {
Assert.fail();
}
}
@Test
public void testGetStartTaskInstanceList() {
try {
TaskInstance taskInstance1 = new TaskInstance();
taskInstance1.setId(1);
TaskInstance taskInstance2 = new TaskInstance();
taskInstance2.setId(2); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 4,114 | [Question] data.basedir.path cleanup problem. | 1, I have modified the data. The basedir. Path from/tmp/dolphinscheduler to /mydata/dolphinscheduler/tmp/.
2. Developer mode is false.
3, /mydata/dolphinscheduler/tmp folder read and write access to normal, ds is perfectly normal.
4, after running for a period of time only, find/data/dolphinscheduler files in the/tmp directory cannot be automatically deleted, lead to disk pile up.
Q: Can temporary files in this directory only be removed manually?Cannot automatically delete??
1、我修改了data.basedir.path从/tmp/dolphinscheduler/ 到数据盘/data/dolphinscheduler/tmp.
2、开发者模式为false.
3、/data/dolphinscheduler/tmp文件夹读写权限正常，ds工作完全正常.
4、在运行了一段时间只有，发现/data/dolphinscheduler/tmp目录中的文件不能自动删除，导致磁盘被占满.
问题：这个目录中的临时文件只能手动删除么？不能自动删除？？？ | https://github.com/apache/dolphinscheduler/issues/4114 | https://github.com/apache/dolphinscheduler/pull/5123 | a8b47e1d4f4ebb9795239ef69b57f2928a81f44c | 492b318bd321d35247488e1f181e3ea9d1259963 | "2020-11-27T02:11:34Z" | java | "2021-03-26T02:11:56Z" | dolphinscheduler-server/src/test/java/org/apache/dolphinscheduler/server/master/MasterExecThreadTest.java | TaskInstance taskInstance3 = new TaskInstance();
taskInstance3.setId(3);
TaskInstance taskInstance4 = new TaskInstance();
taskInstance4.setId(4);
Map<String, String> cmdParam = new HashMap<>();
cmdParam.put(CMD_PARAM_RECOVERY_START_NODE_STRING, "1,2,3,4");
Mockito.when(processService.findTaskInstanceById(1)).thenReturn(taskInstance1);
Mockito.when(processService.findTaskInstanceById(2)).thenReturn(taskInstance2);
Mockito.when(processService.findTaskInstanceById(3)).thenReturn(taskInstance3);
Mockito.when(processService.findTaskInstanceById(4)).thenReturn(taskInstance4);
Class<MasterExecThread> masterExecThreadClass = MasterExecThread.class;
Method method = masterExecThreadClass.getDeclaredMethod("getStartTaskInstanceList", String.class);
method.setAccessible(true);
List<TaskInstance> taskInstances = (List<TaskInstance>) method.invoke(masterExecThread, JSONUtils.toJsonString(cmdParam));
Assert.assertEquals(4, taskInstances.size());
} catch (Exception e) {
Assert.fail();
}
}
private List<Schedule> zeroSchedulerList() {
return Collections.EMPTY_LIST;
}
private List<Schedule> oneSchedulerList() {
List<Schedule> schedulerList = new LinkedList<>();
Schedule schedule = new Schedule();
schedule.setCrontab("0 0 0 1/2 * ?");
schedulerList.add(schedule);
return schedulerList;
}
} |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 5,132 | [Bug][server] when an exception occurs in the taskExecuteThread, task cannot stop immediately |
**Describe the bug**
When an exception occurs in the taskExecuteThread, task will be called the `cancelApplication()` method to stop the task immediately。Howerver，the task whose` cancelApplication()` method base on the `AbstractCommandExecutor.cancelApplication()` cannot be killed immediately,because `AbstractCommandExecutor.cancelApplication()` would not call `hardKill()` method when soft kill process fail;
**To Reproduce**
**Expected behavior**
In order to make the error task stop immediately ，It should call the `hardKill()` method when soft kill process fails；
**Screenshots**
**Which version of Dolphin Scheduler:**
-[dev]
**Additional context**
It is a very simple Bug, the `softKill()` method returns the opposite state, so just modify the return value can fix this bug. I will fix this Bug.
**Requirement or improvement**
| https://github.com/apache/dolphinscheduler/issues/5132 | https://github.com/apache/dolphinscheduler/pull/5133 | 573252f3e1baba5e133b6c8f608c22e3c2267a03 | 9c0439621836b5134b8a7da4e671cb74edc7c31b | "2021-03-23T10:23:38Z" | java | "2021-03-29T02:41:51Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/task/AbstractCommandExecutor.java | /*
* 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.
*/
package org.apache.dolphinscheduler.server.worker.task;
import static org.apache.dolphinscheduler.common.Constants.EXIT_CODE_FAILURE;
import static org.apache.dolphinscheduler.common.Constants.EXIT_CODE_KILL;
import static org.apache.dolphinscheduler.common.Constants.EXIT_CODE_SUCCESS;
import org.apache.dolphinscheduler.common.Constants;
import org.apache.dolphinscheduler.common.enums.ExecutionStatus;
import org.apache.dolphinscheduler.common.thread.Stopper;
import org.apache.dolphinscheduler.common.thread.ThreadUtils;
import org.apache.dolphinscheduler.common.utils.HadoopUtils;
import org.apache.dolphinscheduler.common.utils.LoggerUtils;
import org.apache.dolphinscheduler.common.utils.OSUtils;
import org.apache.dolphinscheduler.common.utils.StringUtils; |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 5,132 | [Bug][server] when an exception occurs in the taskExecuteThread, task cannot stop immediately |
**Describe the bug**
When an exception occurs in the taskExecuteThread, task will be called the `cancelApplication()` method to stop the task immediately。Howerver，the task whose` cancelApplication()` method base on the `AbstractCommandExecutor.cancelApplication()` cannot be killed immediately,because `AbstractCommandExecutor.cancelApplication()` would not call `hardKill()` method when soft kill process fail;
**To Reproduce**
**Expected behavior**
In order to make the error task stop immediately ，It should call the `hardKill()` method when soft kill process fails；
**Screenshots**
**Which version of Dolphin Scheduler:**
-[dev]
**Additional context**
It is a very simple Bug, the `softKill()` method returns the opposite state, so just modify the return value can fix this bug. I will fix this Bug.
**Requirement or improvement**
| https://github.com/apache/dolphinscheduler/issues/5132 | https://github.com/apache/dolphinscheduler/pull/5133 | 573252f3e1baba5e133b6c8f608c22e3c2267a03 | 9c0439621836b5134b8a7da4e671cb74edc7c31b | "2021-03-23T10:23:38Z" | java | "2021-03-29T02:41:51Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/task/AbstractCommandExecutor.java | import org.apache.dolphinscheduler.server.entity.TaskExecutionContext;
import org.apache.dolphinscheduler.server.utils.ProcessUtils;
import org.apache.dolphinscheduler.server.worker.cache.TaskExecutionContextCacheManager;
import org.apache.dolphinscheduler.server.worker.cache.impl.TaskExecutionContextCacheManagerImpl;
import org.apache.dolphinscheduler.service.bean.SpringApplicationContext;
import java.io.BufferedReader;
import java.io.File;
import java.io.FileInputStream;
import java.io.IOException;
import java.io.InputStreamReader;
import java.lang.reflect.Field;
import java.nio.charset.StandardCharsets;
import java.util.ArrayList;
import java.util.Collections;
import java.util.LinkedList;
import java.util.List;
import java.util.concurrent.ExecutorService;
import java.util.concurrent.TimeUnit;
import java.util.function.Consumer;
import java.util.regex.Matcher;
import java.util.regex.Pattern;
import org.slf4j.Logger;
/**
* abstract command executor
*/
public abstract class AbstractCommandExecutor {
/**
* rules for extracting application ID
*/
protected static final Pattern APPLICATION_REGEX = Pattern.compile(Constants.APPLICATION_REGEX); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 5,132 | [Bug][server] when an exception occurs in the taskExecuteThread, task cannot stop immediately |
**Describe the bug**
When an exception occurs in the taskExecuteThread, task will be called the `cancelApplication()` method to stop the task immediately。Howerver，the task whose` cancelApplication()` method base on the `AbstractCommandExecutor.cancelApplication()` cannot be killed immediately,because `AbstractCommandExecutor.cancelApplication()` would not call `hardKill()` method when soft kill process fail;
**To Reproduce**
**Expected behavior**
In order to make the error task stop immediately ，It should call the `hardKill()` method when soft kill process fails；
**Screenshots**
**Which version of Dolphin Scheduler:**
-[dev]
**Additional context**
It is a very simple Bug, the `softKill()` method returns the opposite state, so just modify the return value can fix this bug. I will fix this Bug.
**Requirement or improvement**
| https://github.com/apache/dolphinscheduler/issues/5132 | https://github.com/apache/dolphinscheduler/pull/5133 | 573252f3e1baba5e133b6c8f608c22e3c2267a03 | 9c0439621836b5134b8a7da4e671cb74edc7c31b | "2021-03-23T10:23:38Z" | java | "2021-03-29T02:41:51Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/task/AbstractCommandExecutor.java | protected StringBuilder varPool = new StringBuilder();
/**
* process
*/
private Process process;
/**
* log handler
*/
protected Consumer<List<String>> logHandler;
/**
* logger
*/
protected Logger logger;
/**
* log list
*/
protected final List<String> logBuffer;
protected boolean logOutputIsScuccess = false;
/**
* SHELL result string
*/
protected String taskResultString;
/**
* taskExecutionContext
*/
protected TaskExecutionContext taskExecutionContext;
/**
* taskExecutionContextCacheManager
*/ |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 5,132 | [Bug][server] when an exception occurs in the taskExecuteThread, task cannot stop immediately |
**Describe the bug**
When an exception occurs in the taskExecuteThread, task will be called the `cancelApplication()` method to stop the task immediately。Howerver，the task whose` cancelApplication()` method base on the `AbstractCommandExecutor.cancelApplication()` cannot be killed immediately,because `AbstractCommandExecutor.cancelApplication()` would not call `hardKill()` method when soft kill process fail;
**To Reproduce**
**Expected behavior**
In order to make the error task stop immediately ，It should call the `hardKill()` method when soft kill process fails；
**Screenshots**
**Which version of Dolphin Scheduler:**
-[dev]
**Additional context**
It is a very simple Bug, the `softKill()` method returns the opposite state, so just modify the return value can fix this bug. I will fix this Bug.
**Requirement or improvement**
| https://github.com/apache/dolphinscheduler/issues/5132 | https://github.com/apache/dolphinscheduler/pull/5133 | 573252f3e1baba5e133b6c8f608c22e3c2267a03 | 9c0439621836b5134b8a7da4e671cb74edc7c31b | "2021-03-23T10:23:38Z" | java | "2021-03-29T02:41:51Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/task/AbstractCommandExecutor.java | private TaskExecutionContextCacheManager taskExecutionContextCacheManager;
public AbstractCommandExecutor(Consumer<List<String>> logHandler,
TaskExecutionContext taskExecutionContext,
Logger logger) {
this.logHandler = logHandler;
this.taskExecutionContext = taskExecutionContext;
this.logger = logger;
this.logBuffer = Collections.synchronizedList(new ArrayList<>());
this.taskExecutionContextCacheManager = SpringApplicationContext.getBean(TaskExecutionContextCacheManagerImpl.class);
}
protected AbstractCommandExecutor(List<String> logBuffer) {
this.logBuffer = logBuffer;
}
/**
* build process
*
* @param commandFile command file
* @throws IOException IO Exception
*/
private void buildProcess(String commandFile) throws IOException {
List<String> command = new LinkedList<>();
ProcessBuilder processBuilder = new ProcessBuilder();
processBuilder.directory(new File(taskExecutionContext.getExecutePath()));
processBuilder.redirectErrorStream(true);
command.add("sudo"); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 5,132 | [Bug][server] when an exception occurs in the taskExecuteThread, task cannot stop immediately |
**Describe the bug**
When an exception occurs in the taskExecuteThread, task will be called the `cancelApplication()` method to stop the task immediately。Howerver，the task whose` cancelApplication()` method base on the `AbstractCommandExecutor.cancelApplication()` cannot be killed immediately,because `AbstractCommandExecutor.cancelApplication()` would not call `hardKill()` method when soft kill process fail;
**To Reproduce**
**Expected behavior**
In order to make the error task stop immediately ，It should call the `hardKill()` method when soft kill process fails；
**Screenshots**
**Which version of Dolphin Scheduler:**
-[dev]
**Additional context**
It is a very simple Bug, the `softKill()` method returns the opposite state, so just modify the return value can fix this bug. I will fix this Bug.
**Requirement or improvement**
| https://github.com/apache/dolphinscheduler/issues/5132 | https://github.com/apache/dolphinscheduler/pull/5133 | 573252f3e1baba5e133b6c8f608c22e3c2267a03 | 9c0439621836b5134b8a7da4e671cb74edc7c31b | "2021-03-23T10:23:38Z" | java | "2021-03-29T02:41:51Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/task/AbstractCommandExecutor.java | command.add("-u");
command.add(taskExecutionContext.getTenantCode());
command.add(commandInterpreter());
command.addAll(commandOptions());
command.add(commandFile);
processBuilder.command(command);
process = processBuilder.start();
printCommand(command);
}
/**
* task specific execution logic
*
* @param execCommand execCommand
* @return CommandExecuteResult
* @throws Exception if error throws Exception
*/
public CommandExecuteResult run(String execCommand) throws Exception {
CommandExecuteResult result = new CommandExecuteResult();
int taskInstanceId = taskExecutionContext.getTaskInstanceId();
if (null == taskExecutionContextCacheManager.getByTaskInstanceId(taskInstanceId)) {
result.setExitStatusCode(EXIT_CODE_KILL);
return result;
}
if (StringUtils.isEmpty(execCommand)) {
taskExecutionContextCacheManager.removeByTaskInstanceId(taskInstanceId);
return result;
} |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 5,132 | [Bug][server] when an exception occurs in the taskExecuteThread, task cannot stop immediately |
**Describe the bug**
When an exception occurs in the taskExecuteThread, task will be called the `cancelApplication()` method to stop the task immediately。Howerver，the task whose` cancelApplication()` method base on the `AbstractCommandExecutor.cancelApplication()` cannot be killed immediately,because `AbstractCommandExecutor.cancelApplication()` would not call `hardKill()` method when soft kill process fail;
**To Reproduce**
**Expected behavior**
In order to make the error task stop immediately ，It should call the `hardKill()` method when soft kill process fails；
**Screenshots**
**Which version of Dolphin Scheduler:**
-[dev]
**Additional context**
It is a very simple Bug, the `softKill()` method returns the opposite state, so just modify the return value can fix this bug. I will fix this Bug.
**Requirement or improvement**
| https://github.com/apache/dolphinscheduler/issues/5132 | https://github.com/apache/dolphinscheduler/pull/5133 | 573252f3e1baba5e133b6c8f608c22e3c2267a03 | 9c0439621836b5134b8a7da4e671cb74edc7c31b | "2021-03-23T10:23:38Z" | java | "2021-03-29T02:41:51Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/task/AbstractCommandExecutor.java | String commandFilePath = buildCommandFilePath();
createCommandFileIfNotExists(execCommand, commandFilePath);
buildProcess(commandFilePath);
parseProcessOutput(process);
Integer processId = getProcessId(process);
result.setProcessId(processId);
taskExecutionContext.setProcessId(processId);
boolean updateTaskExecutionContextStatus = taskExecutionContextCacheManager.updateTaskExecutionContext(taskExecutionContext);
if (Boolean.FALSE.equals(updateTaskExecutionContextStatus)) {
ProcessUtils.kill(taskExecutionContext);
result.setExitStatusCode(EXIT_CODE_KILL);
return result;
}
logger.info("process start, process id is: {}", processId);
long remainTime = getRemaintime();
boolean status = process.waitFor(remainTime, TimeUnit.SECONDS);
logger.info("process has exited, execute path:{}, processId:{} ,exitStatusCode:{}",
taskExecutionContext.getExecutePath(),
processId
, result.getExitStatusCode());
if (status) { |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 5,132 | [Bug][server] when an exception occurs in the taskExecuteThread, task cannot stop immediately |
**Describe the bug**
When an exception occurs in the taskExecuteThread, task will be called the `cancelApplication()` method to stop the task immediately。Howerver，the task whose` cancelApplication()` method base on the `AbstractCommandExecutor.cancelApplication()` cannot be killed immediately,because `AbstractCommandExecutor.cancelApplication()` would not call `hardKill()` method when soft kill process fail;
**To Reproduce**
**Expected behavior**
In order to make the error task stop immediately ，It should call the `hardKill()` method when soft kill process fails；
**Screenshots**
**Which version of Dolphin Scheduler:**
-[dev]
**Additional context**
It is a very simple Bug, the `softKill()` method returns the opposite state, so just modify the return value can fix this bug. I will fix this Bug.
**Requirement or improvement**
| https://github.com/apache/dolphinscheduler/issues/5132 | https://github.com/apache/dolphinscheduler/pull/5133 | 573252f3e1baba5e133b6c8f608c22e3c2267a03 | 9c0439621836b5134b8a7da4e671cb74edc7c31b | "2021-03-23T10:23:38Z" | java | "2021-03-29T02:41:51Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/task/AbstractCommandExecutor.java | List<String> appIds = getAppIds(taskExecutionContext.getLogPath());
result.setAppIds(String.join(Constants.COMMA, appIds));
result.setExitStatusCode(process.exitValue());
if (process.exitValue() == 0) {
result.setExitStatusCode(isSuccessOfYarnState(appIds) ? EXIT_CODE_SUCCESS : EXIT_CODE_FAILURE);
}
} else {
logger.error("process has failure , exitStatusCode : {} , ready to kill ...", result.getExitStatusCode());
ProcessUtils.kill(taskExecutionContext);
result.setExitStatusCode(EXIT_CODE_FAILURE);
}
return result;
}
public String getVarPool() {
return varPool.toString();
}
/**
* cancel application
*
* @throws Exception exception
*/
public void cancelApplication() throws Exception {
if (process == null) {
return;
}
clear();
int processId = getProcessId(process); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 5,132 | [Bug][server] when an exception occurs in the taskExecuteThread, task cannot stop immediately |
**Describe the bug**
When an exception occurs in the taskExecuteThread, task will be called the `cancelApplication()` method to stop the task immediately。Howerver，the task whose` cancelApplication()` method base on the `AbstractCommandExecutor.cancelApplication()` cannot be killed immediately,because `AbstractCommandExecutor.cancelApplication()` would not call `hardKill()` method when soft kill process fail;
**To Reproduce**
**Expected behavior**
In order to make the error task stop immediately ，It should call the `hardKill()` method when soft kill process fails；
**Screenshots**
**Which version of Dolphin Scheduler:**
-[dev]
**Additional context**
It is a very simple Bug, the `softKill()` method returns the opposite state, so just modify the return value can fix this bug. I will fix this Bug.
**Requirement or improvement**
| https://github.com/apache/dolphinscheduler/issues/5132 | https://github.com/apache/dolphinscheduler/pull/5133 | 573252f3e1baba5e133b6c8f608c22e3c2267a03 | 9c0439621836b5134b8a7da4e671cb74edc7c31b | "2021-03-23T10:23:38Z" | java | "2021-03-29T02:41:51Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/task/AbstractCommandExecutor.java | logger.info("cancel process: {}", processId);
boolean killed = softKill(processId);
if (!killed) {
hardKill(processId);
process.destroy();
process = null;
}
}
/**
* soft kill
*
* @param processId process id
* @return process is alive
* @throws InterruptedException interrupted exception
*/
private boolean softKill(int processId) {
if (processId != 0 && process.isAlive()) {
try {
String cmd = String.format("kill %d", processId);
cmd = OSUtils.getSudoCmd(taskExecutionContext.getTenantCode(), cmd);
logger.info("soft kill task:{}, process id:{}, cmd:{}", taskExecutionContext.getTaskAppId(), processId, cmd);
Runtime.getRuntime().exec(cmd);
} catch (IOException e) {
logger.info("kill attempt failed", e);
}
} |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 5,132 | [Bug][server] when an exception occurs in the taskExecuteThread, task cannot stop immediately |
**Describe the bug**
When an exception occurs in the taskExecuteThread, task will be called the `cancelApplication()` method to stop the task immediately。Howerver，the task whose` cancelApplication()` method base on the `AbstractCommandExecutor.cancelApplication()` cannot be killed immediately,because `AbstractCommandExecutor.cancelApplication()` would not call `hardKill()` method when soft kill process fail;
**To Reproduce**
**Expected behavior**
In order to make the error task stop immediately ，It should call the `hardKill()` method when soft kill process fails；
**Screenshots**
**Which version of Dolphin Scheduler:**
-[dev]
**Additional context**
It is a very simple Bug, the `softKill()` method returns the opposite state, so just modify the return value can fix this bug. I will fix this Bug.
**Requirement or improvement**
| https://github.com/apache/dolphinscheduler/issues/5132 | https://github.com/apache/dolphinscheduler/pull/5133 | 573252f3e1baba5e133b6c8f608c22e3c2267a03 | 9c0439621836b5134b8a7da4e671cb74edc7c31b | "2021-03-23T10:23:38Z" | java | "2021-03-29T02:41:51Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/task/AbstractCommandExecutor.java | return process.isAlive();
}
/**
* hard kill
*
* @param processId process id
*/
private void hardKill(int processId) {
if (processId != 0 && process.isAlive()) {
try {
String cmd = String.format("kill -9 %d", processId);
cmd = OSUtils.getSudoCmd(taskExecutionContext.getTenantCode(), cmd);
logger.info("hard kill task:{}, process id:{}, cmd:{}", taskExecutionContext.getTaskAppId(), processId, cmd);
Runtime.getRuntime().exec(cmd);
} catch (IOException e) {
logger.error("kill attempt failed ", e);
}
}
}
/**
* print command
*
* @param commands process builder
*/
private void printCommand(List<String> commands) {
String cmdStr;
try {
cmdStr = ProcessUtils.buildCommandStr(commands);
logger.info("task run command:\n{}", cmdStr);
} catch (Exception e) { |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 5,132 | [Bug][server] when an exception occurs in the taskExecuteThread, task cannot stop immediately |
**Describe the bug**
When an exception occurs in the taskExecuteThread, task will be called the `cancelApplication()` method to stop the task immediately。Howerver，the task whose` cancelApplication()` method base on the `AbstractCommandExecutor.cancelApplication()` cannot be killed immediately,because `AbstractCommandExecutor.cancelApplication()` would not call `hardKill()` method when soft kill process fail;
**To Reproduce**
**Expected behavior**
In order to make the error task stop immediately ，It should call the `hardKill()` method when soft kill process fails；
**Screenshots**
**Which version of Dolphin Scheduler:**
-[dev]
**Additional context**
It is a very simple Bug, the `softKill()` method returns the opposite state, so just modify the return value can fix this bug. I will fix this Bug.
**Requirement or improvement**
| https://github.com/apache/dolphinscheduler/issues/5132 | https://github.com/apache/dolphinscheduler/pull/5133 | 573252f3e1baba5e133b6c8f608c22e3c2267a03 | 9c0439621836b5134b8a7da4e671cb74edc7c31b | "2021-03-23T10:23:38Z" | java | "2021-03-29T02:41:51Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/task/AbstractCommandExecutor.java | logger.error(e.getMessage(), e);
}
}
/**
* clear
*/
private void clear() {
List<String> markerList = new ArrayList<>();
markerList.add(ch.qos.logback.classic.ClassicConstants.FINALIZE_SESSION_MARKER.toString());
if (!logBuffer.isEmpty()) {
logHandler.accept(logBuffer);
logBuffer.clear();
}
logHandler.accept(markerList);
}
/**
* get the standard output of the process
*
* @param process process
*/
private void parseProcessOutput(Process process) {
String threadLoggerInfoName = String.format(LoggerUtils.TASK_LOGGER_THREAD_NAME + "-%s", taskExecutionContext.getTaskAppId());
ExecutorService getOutputLogService = ThreadUtils.newDaemonSingleThreadExecutor(threadLoggerInfoName + "-" + "getOutputLogService");
getOutputLogService.submit(() -> {
BufferedReader inReader = null;
try {
inReader = new BufferedReader(new InputStreamReader(process.getInputStream()));
String line;
logBuffer.add("welcome to use bigdata scheduling system..."); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 5,132 | [Bug][server] when an exception occurs in the taskExecuteThread, task cannot stop immediately |
**Describe the bug**
When an exception occurs in the taskExecuteThread, task will be called the `cancelApplication()` method to stop the task immediately。Howerver，the task whose` cancelApplication()` method base on the `AbstractCommandExecutor.cancelApplication()` cannot be killed immediately,because `AbstractCommandExecutor.cancelApplication()` would not call `hardKill()` method when soft kill process fail;
**To Reproduce**
**Expected behavior**
In order to make the error task stop immediately ，It should call the `hardKill()` method when soft kill process fails；
**Screenshots**
**Which version of Dolphin Scheduler:**
-[dev]
**Additional context**
It is a very simple Bug, the `softKill()` method returns the opposite state, so just modify the return value can fix this bug. I will fix this Bug.
**Requirement or improvement**
| https://github.com/apache/dolphinscheduler/issues/5132 | https://github.com/apache/dolphinscheduler/pull/5133 | 573252f3e1baba5e133b6c8f608c22e3c2267a03 | 9c0439621836b5134b8a7da4e671cb74edc7c31b | "2021-03-23T10:23:38Z" | java | "2021-03-29T02:41:51Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/task/AbstractCommandExecutor.java | while ((line = inReader.readLine()) != null) {
if (line.startsWith("${setValue(")) {
varPool.append(line.substring("${setValue(".length(), line.length() - 2));
varPool.append("$VarPool$");
} else {
logBuffer.add(line);
taskResultString = line;
}
}
} catch (Exception e) {
logger.error(e.getMessage(), e);
} finally {
logOutputIsScuccess = true;
close(inReader);
}
});
getOutputLogService.shutdown();
ExecutorService parseProcessOutputExecutorService = ThreadUtils.newDaemonSingleThreadExecutor(threadLoggerInfoName);
parseProcessOutputExecutorService.submit(() -> {
try {
long lastFlushTime = System.currentTimeMillis();
while (logBuffer.size() > 0 || !logOutputIsScuccess) {
if (logBuffer.size() > 0) {
lastFlushTime = flush(lastFlushTime);
} else {
Thread.sleep(Constants.DEFAULT_LOG_FLUSH_INTERVAL);
}
}
} catch (Exception e) {
logger.error(e.getMessage(), e); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 5,132 | [Bug][server] when an exception occurs in the taskExecuteThread, task cannot stop immediately |
**Describe the bug**
When an exception occurs in the taskExecuteThread, task will be called the `cancelApplication()` method to stop the task immediately。Howerver，the task whose` cancelApplication()` method base on the `AbstractCommandExecutor.cancelApplication()` cannot be killed immediately,because `AbstractCommandExecutor.cancelApplication()` would not call `hardKill()` method when soft kill process fail;
**To Reproduce**
**Expected behavior**
In order to make the error task stop immediately ，It should call the `hardKill()` method when soft kill process fails；
**Screenshots**
**Which version of Dolphin Scheduler:**
-[dev]
**Additional context**
It is a very simple Bug, the `softKill()` method returns the opposite state, so just modify the return value can fix this bug. I will fix this Bug.
**Requirement or improvement**
| https://github.com/apache/dolphinscheduler/issues/5132 | https://github.com/apache/dolphinscheduler/pull/5133 | 573252f3e1baba5e133b6c8f608c22e3c2267a03 | 9c0439621836b5134b8a7da4e671cb74edc7c31b | "2021-03-23T10:23:38Z" | java | "2021-03-29T02:41:51Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/task/AbstractCommandExecutor.java | } finally {
clear();
}
});
parseProcessOutputExecutorService.shutdown();
}
/**
* check yarn state
*
* @param appIds application id list
* @return is success of yarn task state
*/
public boolean isSuccessOfYarnState(List<String> appIds) {
boolean result = true;
try {
for (String appId : appIds) {
while (Stopper.isRunning()) {
ExecutionStatus applicationStatus = HadoopUtils.getInstance().getApplicationStatus(appId);
logger.info("appId:{}, final state:{}", appId, applicationStatus.name());
if (applicationStatus.equals(ExecutionStatus.FAILURE)
|| applicationStatus.equals(ExecutionStatus.KILL)) {
return false;
}
if (applicationStatus.equals(ExecutionStatus.SUCCESS)) {
break;
}
Thread.sleep(Constants.SLEEP_TIME_MILLIS);
}
}
} catch (Exception e) { |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 5,132 | [Bug][server] when an exception occurs in the taskExecuteThread, task cannot stop immediately |
**Describe the bug**
When an exception occurs in the taskExecuteThread, task will be called the `cancelApplication()` method to stop the task immediately。Howerver，the task whose` cancelApplication()` method base on the `AbstractCommandExecutor.cancelApplication()` cannot be killed immediately,because `AbstractCommandExecutor.cancelApplication()` would not call `hardKill()` method when soft kill process fail;
**To Reproduce**
**Expected behavior**
In order to make the error task stop immediately ，It should call the `hardKill()` method when soft kill process fails；
**Screenshots**
**Which version of Dolphin Scheduler:**
-[dev]
**Additional context**
It is a very simple Bug, the `softKill()` method returns the opposite state, so just modify the return value can fix this bug. I will fix this Bug.
**Requirement or improvement**
| https://github.com/apache/dolphinscheduler/issues/5132 | https://github.com/apache/dolphinscheduler/pull/5133 | 573252f3e1baba5e133b6c8f608c22e3c2267a03 | 9c0439621836b5134b8a7da4e671cb74edc7c31b | "2021-03-23T10:23:38Z" | java | "2021-03-29T02:41:51Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/task/AbstractCommandExecutor.java | logger.error(String.format("yarn applications: %s status failed ", appIds.toString()), e);
result = false;
}
return result;
}
public int getProcessId() {
return getProcessId(process);
}
/**
* get app links
*
* @param logPath log path
* @return app id list
*/
private List<String> getAppIds(String logPath) {
List<String> logs = convertFile2List(logPath);
List<String> appIds = new ArrayList<>();
/**
* analysis log?get submited yarn application id
*/
for (String log : logs) {
String appId = findAppId(log);
if (StringUtils.isNotEmpty(appId) && !appIds.contains(appId)) {
logger.info("find app id: {}", appId);
appIds.add(appId);
}
}
return appIds;
}
/** |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 5,132 | [Bug][server] when an exception occurs in the taskExecuteThread, task cannot stop immediately |
**Describe the bug**
When an exception occurs in the taskExecuteThread, task will be called the `cancelApplication()` method to stop the task immediately。Howerver，the task whose` cancelApplication()` method base on the `AbstractCommandExecutor.cancelApplication()` cannot be killed immediately,because `AbstractCommandExecutor.cancelApplication()` would not call `hardKill()` method when soft kill process fail;
**To Reproduce**
**Expected behavior**
In order to make the error task stop immediately ，It should call the `hardKill()` method when soft kill process fails；
**Screenshots**
**Which version of Dolphin Scheduler:**
-[dev]
**Additional context**
It is a very simple Bug, the `softKill()` method returns the opposite state, so just modify the return value can fix this bug. I will fix this Bug.
**Requirement or improvement**
| https://github.com/apache/dolphinscheduler/issues/5132 | https://github.com/apache/dolphinscheduler/pull/5133 | 573252f3e1baba5e133b6c8f608c22e3c2267a03 | 9c0439621836b5134b8a7da4e671cb74edc7c31b | "2021-03-23T10:23:38Z" | java | "2021-03-29T02:41:51Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/task/AbstractCommandExecutor.java | * convert file to list
*
* @param filename file name
* @return line list
*/
private List<String> convertFile2List(String filename) {
List lineList = new ArrayList<String>(100);
File file = new File(filename);
if (!file.exists()) {
return lineList;
}
BufferedReader br = null;
try {
br = new BufferedReader(new InputStreamReader(new FileInputStream(filename), StandardCharsets.UTF_8));
String line = null;
while ((line = br.readLine()) != null) {
lineList.add(line);
}
} catch (Exception e) {
logger.error(String.format("read file: %s failed : ", filename), e);
} finally {
if (br != null) {
try {
br.close();
} catch (IOException e) {
logger.error(e.getMessage(), e);
}
}
}
return lineList; |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 5,132 | [Bug][server] when an exception occurs in the taskExecuteThread, task cannot stop immediately |
**Describe the bug**
When an exception occurs in the taskExecuteThread, task will be called the `cancelApplication()` method to stop the task immediately。Howerver，the task whose` cancelApplication()` method base on the `AbstractCommandExecutor.cancelApplication()` cannot be killed immediately,because `AbstractCommandExecutor.cancelApplication()` would not call `hardKill()` method when soft kill process fail;
**To Reproduce**
**Expected behavior**
In order to make the error task stop immediately ，It should call the `hardKill()` method when soft kill process fails；
**Screenshots**
**Which version of Dolphin Scheduler:**
-[dev]
**Additional context**
It is a very simple Bug, the `softKill()` method returns the opposite state, so just modify the return value can fix this bug. I will fix this Bug.
**Requirement or improvement**
| https://github.com/apache/dolphinscheduler/issues/5132 | https://github.com/apache/dolphinscheduler/pull/5133 | 573252f3e1baba5e133b6c8f608c22e3c2267a03 | 9c0439621836b5134b8a7da4e671cb74edc7c31b | "2021-03-23T10:23:38Z" | java | "2021-03-29T02:41:51Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/task/AbstractCommandExecutor.java | }
/**
* find app id
*
* @param line line
* @return appid
*/
private String findAppId(String line) {
Matcher matcher = APPLICATION_REGEX.matcher(line);
if (matcher.find()) {
return matcher.group();
}
return null;
}
/**
* get remain time（s）
*
* @return remain time
*/
private long getRemaintime() {
long usedTime = (System.currentTimeMillis() - taskExecutionContext.getStartTime().getTime()) / 1000;
long remainTime = taskExecutionContext.getTaskTimeout() - usedTime;
if (remainTime < 0) {
throw new RuntimeException("task execution time out");
}
return remainTime;
}
/**
* get process id
* |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 5,132 | [Bug][server] when an exception occurs in the taskExecuteThread, task cannot stop immediately |
**Describe the bug**
When an exception occurs in the taskExecuteThread, task will be called the `cancelApplication()` method to stop the task immediately。Howerver，the task whose` cancelApplication()` method base on the `AbstractCommandExecutor.cancelApplication()` cannot be killed immediately,because `AbstractCommandExecutor.cancelApplication()` would not call `hardKill()` method when soft kill process fail;
**To Reproduce**
**Expected behavior**
In order to make the error task stop immediately ，It should call the `hardKill()` method when soft kill process fails；
**Screenshots**
**Which version of Dolphin Scheduler:**
-[dev]
**Additional context**
It is a very simple Bug, the `softKill()` method returns the opposite state, so just modify the return value can fix this bug. I will fix this Bug.
**Requirement or improvement**
| https://github.com/apache/dolphinscheduler/issues/5132 | https://github.com/apache/dolphinscheduler/pull/5133 | 573252f3e1baba5e133b6c8f608c22e3c2267a03 | 9c0439621836b5134b8a7da4e671cb74edc7c31b | "2021-03-23T10:23:38Z" | java | "2021-03-29T02:41:51Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/task/AbstractCommandExecutor.java | * @param process process
* @return process id
*/
private int getProcessId(Process process) {
int processId = 0;
try {
Field f = process.getClass().getDeclaredField(Constants.PID);
f.setAccessible(true);
processId = f.getInt(process);
} catch (Throwable e) {
logger.error(e.getMessage(), e);
}
return processId;
}
/**
* when log buffer siz or flush time reach condition , then flush
*
* @param lastFlushTime last flush time
* @return last flush time
*/
private long flush(long lastFlushTime) {
long now = System.currentTimeMillis();
/**
* when log buffer siz or flush time reach condition , then flush
*/
if (logBuffer.size() >= Constants.DEFAULT_LOG_ROWS_NUM || now - lastFlushTime > Constants.DEFAULT_LOG_FLUSH_INTERVAL) {
lastFlushTime = now;
/**
logHandler.accept(logBuffer);
logBuffer.clear(); |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 5,132 | [Bug][server] when an exception occurs in the taskExecuteThread, task cannot stop immediately |
**Describe the bug**
When an exception occurs in the taskExecuteThread, task will be called the `cancelApplication()` method to stop the task immediately。Howerver，the task whose` cancelApplication()` method base on the `AbstractCommandExecutor.cancelApplication()` cannot be killed immediately,because `AbstractCommandExecutor.cancelApplication()` would not call `hardKill()` method when soft kill process fail;
**To Reproduce**
**Expected behavior**
In order to make the error task stop immediately ，It should call the `hardKill()` method when soft kill process fails；
**Screenshots**
**Which version of Dolphin Scheduler:**
-[dev]
**Additional context**
It is a very simple Bug, the `softKill()` method returns the opposite state, so just modify the return value can fix this bug. I will fix this Bug.
**Requirement or improvement**
| https://github.com/apache/dolphinscheduler/issues/5132 | https://github.com/apache/dolphinscheduler/pull/5133 | 573252f3e1baba5e133b6c8f608c22e3c2267a03 | 9c0439621836b5134b8a7da4e671cb74edc7c31b | "2021-03-23T10:23:38Z" | java | "2021-03-29T02:41:51Z" | dolphinscheduler-server/src/main/java/org/apache/dolphinscheduler/server/worker/task/AbstractCommandExecutor.java | }
return lastFlushTime;
}
/**
* close buffer reader
*
* @param inReader in reader
*/
private void close(BufferedReader inReader) {
if (inReader != null) {
try {
inReader.close();
} catch (IOException e) {
logger.error(e.getMessage(), e);
}
}
}
protected List<String> commandOptions() {
return Collections.emptyList();
}
protected abstract String buildCommandFilePath();
protected abstract String commandInterpreter();
protected abstract void createCommandFileIfNotExists(String execCommand, String commandFile) throws IOException;
public String getTaskResultString() {
return taskResultString;
}
public void setTaskResultString(String taskResultString) {
this.taskResultString = taskResultString;
}
} |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 5,128 | [Feature][Worker] Support turning off sudo permissions | *For better global communication, please give priority to using English description, thx! *
*Please review https://dolphinscheduler.apache.org/en-us/community/development/issue.html when describe an issue.*
**Describe the feature**
The current version of multi-tenant implementation requires sudo permission. Most of the time the deployment execution user does not have sudo permission and does not need to be executed by the tenant account. At this time, the sudo permission dependency can be turned off, and the task execution is executed by the deployment user.
当前版本多租户的实现，需要sudo权限，大多数时候部署执行用户没有sudo权限，并且不需要利用租户账户执行，这时候可以关掉sudo权限依赖，任务执行采用部署用户执行
sudo stands for privilege escalation. If privilege escalation is not configured, multi-tenant is only used to isolate resources and users. After privilege escalation is configured, task execution will be performed by tenants, and deployment users will not be configured; and if privilege escalation is not configured, tenants cannot be automatically created.
sudo 代表提权，如果不配置提权，多租户仅用来隔离资源与用户，配置提权以后，任务执行使用租户执行，不配置使用部署用户执行；并且不配置提权不允许自动创建租户 | https://github.com/apache/dolphinscheduler/issues/5128 | https://github.com/apache/dolphinscheduler/pull/5129 | 9c0439621836b5134b8a7da4e671cb74edc7c31b | a6a1b94df4f5c4d22845fe99f2f778ba53d60e5c | "2021-03-23T04:00:15Z" | java | "2021-03-29T03:07:39Z" | dolphinscheduler-common/src/main/java/org/apache/dolphinscheduler/common/Constants.java | /*
* 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.
*/
package org.apache.dolphinscheduler.common;
import org.apache.dolphinscheduler.common.enums.ExecutionStatus;
import org.apache.dolphinscheduler.common.utils.OSUtils;
import org.apache.dolphinscheduler.common.utils.StringUtils;
import java.util.regex.Pattern;
/**
* Constants
*/
public final class Constants { |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 5,128 | [Feature][Worker] Support turning off sudo permissions | *For better global communication, please give priority to using English description, thx! *
*Please review https://dolphinscheduler.apache.org/en-us/community/development/issue.html when describe an issue.*
**Describe the feature**
The current version of multi-tenant implementation requires sudo permission. Most of the time the deployment execution user does not have sudo permission and does not need to be executed by the tenant account. At this time, the sudo permission dependency can be turned off, and the task execution is executed by the deployment user.
当前版本多租户的实现，需要sudo权限，大多数时候部署执行用户没有sudo权限，并且不需要利用租户账户执行，这时候可以关掉sudo权限依赖，任务执行采用部署用户执行
sudo stands for privilege escalation. If privilege escalation is not configured, multi-tenant is only used to isolate resources and users. After privilege escalation is configured, task execution will be performed by tenants, and deployment users will not be configured; and if privilege escalation is not configured, tenants cannot be automatically created.
sudo 代表提权，如果不配置提权，多租户仅用来隔离资源与用户，配置提权以后，任务执行使用租户执行，不配置使用部署用户执行；并且不配置提权不允许自动创建租户 | https://github.com/apache/dolphinscheduler/issues/5128 | https://github.com/apache/dolphinscheduler/pull/5129 | 9c0439621836b5134b8a7da4e671cb74edc7c31b | a6a1b94df4f5c4d22845fe99f2f778ba53d60e5c | "2021-03-23T04:00:15Z" | java | "2021-03-29T03:07:39Z" | dolphinscheduler-common/src/main/java/org/apache/dolphinscheduler/common/Constants.java | private Constants() {
throw new UnsupportedOperationException("Construct Constants");
}
/**
* quartz config
*/
public static final String ORG_QUARTZ_JOBSTORE_DRIVERDELEGATECLASS = "org.quartz.jobStore.driverDelegateClass";
public static final String ORG_QUARTZ_SCHEDULER_INSTANCENAME = "org.quartz.scheduler.instanceName";
public static final String ORG_QUARTZ_SCHEDULER_INSTANCEID = "org.quartz.scheduler.instanceId";
public static final String ORG_QUARTZ_SCHEDULER_MAKESCHEDULERTHREADDAEMON = "org.quartz.scheduler.makeSchedulerThreadDaemon";
public static final String ORG_QUARTZ_JOBSTORE_USEPROPERTIES = "org.quartz.jobStore.useProperties";
public static final String ORG_QUARTZ_THREADPOOL_CLASS = "org.quartz.threadPool.class";
public static final String ORG_QUARTZ_THREADPOOL_THREADCOUNT = "org.quartz.threadPool.threadCount";
public static final String ORG_QUARTZ_THREADPOOL_MAKETHREADSDAEMONS = "org.quartz.threadPool.makeThreadsDaemons";
public static final String ORG_QUARTZ_THREADPOOL_THREADPRIORITY = "org.quartz.threadPool.threadPriority";
public static final String ORG_QUARTZ_JOBSTORE_CLASS = "org.quartz.jobStore.class";
public static final String ORG_QUARTZ_JOBSTORE_TABLEPREFIX = "org.quartz.jobStore.tablePrefix";
public static final String ORG_QUARTZ_JOBSTORE_ISCLUSTERED = "org.quartz.jobStore.isClustered";
public static final String ORG_QUARTZ_JOBSTORE_MISFIRETHRESHOLD = "org.quartz.jobStore.misfireThreshold";
public static final String ORG_QUARTZ_JOBSTORE_CLUSTERCHECKININTERVAL = "org.quartz.jobStore.clusterCheckinInterval";
public static final String ORG_QUARTZ_JOBSTORE_ACQUIRETRIGGERSWITHINLOCK = "org.quartz.jobStore.acquireTriggersWithinLock";
public static final String ORG_QUARTZ_JOBSTORE_DATASOURCE = "org.quartz.jobStore.dataSource";
public static final String ORG_QUARTZ_DATASOURCE_MYDS_CONNECTIONPROVIDER_CLASS = "org.quartz.dataSource.myDs.connectionProvider.class";
/**
* quartz config default value
*/
public static final String QUARTZ_TABLE_PREFIX = "QRTZ_";
public static final String QUARTZ_MISFIRETHRESHOLD = "60000";
public static final String QUARTZ_CLUSTERCHECKININTERVAL = "5000"; |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 5,128 | [Feature][Worker] Support turning off sudo permissions | *For better global communication, please give priority to using English description, thx! *
*Please review https://dolphinscheduler.apache.org/en-us/community/development/issue.html when describe an issue.*
**Describe the feature**
The current version of multi-tenant implementation requires sudo permission. Most of the time the deployment execution user does not have sudo permission and does not need to be executed by the tenant account. At this time, the sudo permission dependency can be turned off, and the task execution is executed by the deployment user.
当前版本多租户的实现，需要sudo权限，大多数时候部署执行用户没有sudo权限，并且不需要利用租户账户执行，这时候可以关掉sudo权限依赖，任务执行采用部署用户执行
sudo stands for privilege escalation. If privilege escalation is not configured, multi-tenant is only used to isolate resources and users. After privilege escalation is configured, task execution will be performed by tenants, and deployment users will not be configured; and if privilege escalation is not configured, tenants cannot be automatically created.
sudo 代表提权，如果不配置提权，多租户仅用来隔离资源与用户，配置提权以后，任务执行使用租户执行，不配置使用部署用户执行；并且不配置提权不允许自动创建租户 | https://github.com/apache/dolphinscheduler/issues/5128 | https://github.com/apache/dolphinscheduler/pull/5129 | 9c0439621836b5134b8a7da4e671cb74edc7c31b | a6a1b94df4f5c4d22845fe99f2f778ba53d60e5c | "2021-03-23T04:00:15Z" | java | "2021-03-29T03:07:39Z" | dolphinscheduler-common/src/main/java/org/apache/dolphinscheduler/common/Constants.java | public static final String QUARTZ_DATASOURCE = "myDs";
public static final String QUARTZ_THREADCOUNT = "25";
public static final String QUARTZ_THREADPRIORITY = "5";
public static final String QUARTZ_INSTANCENAME = "DolphinScheduler";
public static final String QUARTZ_INSTANCEID = "AUTO";
public static final String QUARTZ_ACQUIRETRIGGERSWITHINLOCK = "true";
/**
* common properties path
*/
public static final String COMMON_PROPERTIES_PATH = "/common.properties";
/**
* fs.defaultFS
*/
public static final String FS_DEFAULTFS = "fs.defaultFS";
/**
* fs s3a endpoint
*/
public static final String FS_S3A_ENDPOINT = "fs.s3a.endpoint";
/**
* fs s3a access key
*/
public static final String FS_S3A_ACCESS_KEY = "fs.s3a.access.key";
/**
* fs s3a secret key
*/
public static final String FS_S3A_SECRET_KEY = "fs.s3a.secret.key";
/**
* yarn.resourcemanager.ha.rm.ids
*/
public static final String YARN_RESOURCEMANAGER_HA_RM_IDS = "yarn.resourcemanager.ha.rm.ids"; |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 5,128 | [Feature][Worker] Support turning off sudo permissions | *For better global communication, please give priority to using English description, thx! *
*Please review https://dolphinscheduler.apache.org/en-us/community/development/issue.html when describe an issue.*
**Describe the feature**
The current version of multi-tenant implementation requires sudo permission. Most of the time the deployment execution user does not have sudo permission and does not need to be executed by the tenant account. At this time, the sudo permission dependency can be turned off, and the task execution is executed by the deployment user.
当前版本多租户的实现，需要sudo权限，大多数时候部署执行用户没有sudo权限，并且不需要利用租户账户执行，这时候可以关掉sudo权限依赖，任务执行采用部署用户执行
sudo stands for privilege escalation. If privilege escalation is not configured, multi-tenant is only used to isolate resources and users. After privilege escalation is configured, task execution will be performed by tenants, and deployment users will not be configured; and if privilege escalation is not configured, tenants cannot be automatically created.
sudo 代表提权，如果不配置提权，多租户仅用来隔离资源与用户，配置提权以后，任务执行使用租户执行，不配置使用部署用户执行；并且不配置提权不允许自动创建租户 | https://github.com/apache/dolphinscheduler/issues/5128 | https://github.com/apache/dolphinscheduler/pull/5129 | 9c0439621836b5134b8a7da4e671cb74edc7c31b | a6a1b94df4f5c4d22845fe99f2f778ba53d60e5c | "2021-03-23T04:00:15Z" | java | "2021-03-29T03:07:39Z" | dolphinscheduler-common/src/main/java/org/apache/dolphinscheduler/common/Constants.java | public static final String YARN_RESOURCEMANAGER_HA_XX = "xx";
/**
* yarn.application.status.address
*/
public static final String YARN_APPLICATION_STATUS_ADDRESS = "yarn.application.status.address";
/**
* yarn.job.history.status.address
*/
public static final String YARN_JOB_HISTORY_STATUS_ADDRESS = "yarn.job.history.status.address";
/**
* hdfs configuration
* hdfs.root.user
*/
public static final String HDFS_ROOT_USER = "hdfs.root.user";
/**
* hdfs/s3 configuration
* resource.upload.path
*/
public static final String RESOURCE_UPLOAD_PATH = "resource.upload.path";
/**
* data basedir path
*/
public static final String DATA_BASEDIR_PATH = "data.basedir.path";
/**
* dolphinscheduler.env.path
*/
public static final String DOLPHINSCHEDULER_ENV_PATH = "dolphinscheduler.env.path";
/**
* environment properties default path
*/ |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.