You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2022/04/19 02:58:34 UTC
[GitHub] [shardingsphere-elasticjob] ycy1991 opened a new issue, #2067: Multi slice useless scheduling
ycy1991 opened a new issue, #2067:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/2067
When I use Lite core to develop a 3-slice task, the same actuator will be called three times. Is this a little redundant? And the more slices, the more frequent this useless call. Personally, I think this is mainly useful when centralization is used. Decentralized scheduling is actually useless. Can it be improved
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere-elasticjob] TeslaCN closed issue #2067: Multi slice useless scheduling
Posted by GitBox <gi...@apache.org>.
TeslaCN closed issue #2067: Multi slice useless scheduling
URL: https://github.com/apache/shardingsphere-elasticjob/issues/2067
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere-elasticjob] ycy1991 commented on issue #2067: Multi slice useless scheduling
Posted by GitBox <gi...@apache.org>.
ycy1991 commented on issue #2067:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/2067#issuecomment-1101943640
config
cron: 0/5 * * * * ?
description: ''
disabled: false
failover: false
jobExtraConfigurations:
- !!org.apache.shardingsphere.elasticjob.tracing.yaml.YamlTracingConfiguration
tracingStorageConfiguration: !!org.apache.shardingsphere.elasticjob.tracing.rdb.yaml.YamlDataSourceConfiguration
dataSourceClassName: org.apache.commons.dbcp2.BasicDataSource
props:
logAbandoned: false
numTestsPerEvictionRun: 3
url: jdbc:h2:mem:job_event_storage
timeBetweenEvictionRunsMillis: -1
enableAutoCommitOnReturn: true
removeAbandonedTimeout: 300
lifo: true
driverClassName: org.h2.Driver
softMinEvictableIdleTimeMillis: -1
rollbackOnReturn: true
abandonedUsageTracking: false
testOnBorrow: true
testOnReturn: false
numIdle: 1
maxIdle: 8
minIdle: 0
logExpiredConnections: true
maxTotal: 8
numActive: 0
defaultTransactionIsolation: -1
testOnCreate: false
removeAbandonedOnMaintenance: false
fastFailValidation: false
password: ''
cacheState: true
initialSize: 0
maxWaitMillis: -1
validationQueryTimeout: -1
evictionPolicyClassName: org.apache.commons.pool2.impl.DefaultEvictionPolicy
maxOpenPreparedStatements: -1
removeAbandonedOnBorrow: false
connectionInitSqls: []
testWhileIdle: false
autoCommitOnReturn: true
minEvictableIdleTimeMillis: 1800000
maxConnLifetimeMillis: -1
username: sa
type: RDB
jobName: scriptElasticJob
jobParameter: ''
maxTimeDiffSeconds: -1
misfire: true
monitorExecution: true
overwrite: false
props:
script.command.line: D:\workspace\shardingsphere-elasticjob\examples\elasticjob-example-lite-java\target\classes\script\demo.bat
reconcileIntervalMinutes: 10
shardingItemParameters: ''
shardingTotalCount: 3
staticSharding: false
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere-elasticjob] TeslaCN commented on issue #2067: Multi slice useless scheduling
Posted by GitBox <gi...@apache.org>.
TeslaCN commented on issue #2067:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/2067#issuecomment-1102586271
The logic is same, but the elements in `items` are different between instances.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere-elasticjob] TeslaCN commented on issue #2067: Multi slice useless scheduling
Posted by GitBox <gi...@apache.org>.
TeslaCN commented on issue #2067:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/2067#issuecomment-1118560321
Close due to no response.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere-elasticjob] TeslaCN commented on issue #2067: Multi slice useless scheduling
Posted by GitBox <gi...@apache.org>.
TeslaCN commented on issue #2067:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/2067#issuecomment-1104881734
> Yes, the processing elements are different. It's just that any instance is executing this useless for loop. I think it's just unnecessary
Sorry, I can't get your point. Why the loop is useless and what is unnecessary?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere-elasticjob] ycy1991 commented on issue #2067: Multi slice useless scheduling
Posted by GitBox <gi...@apache.org>.
ycy1991 commented on issue #2067:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/2067#issuecomment-1104878153
Yes, the processing elements are different. It's just that any instance is executing this useless for loop. I think it's just unnecessary
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org