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/05/16 11:23:21 UTC
[GitHub] [shardingsphere] TeslaCN opened a new issue, #17708: `completionDetector not configured` appeared in logs while detector was configured
TeslaCN opened a new issue, #17708:
URL: https://github.com/apache/shardingsphere/issues/17708
## Bug Report
### Which version of ShardingSphere did you use?
master - 12e8d1383a76595ef229be5ede0662e472c14846
### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
Scaling
### Expected behavior
Auto switch data sources after scaling finished.
### Actual behavior
Keep logging:
```
[INFO ] 2022-05-16 19:05:30.047 [_finished_check_Worker-1] o.a.s.d.p.core.job.FinishedCheckJob - completionDetector not configured, auto switch will not be enabled. You could query job progress and switch config manually with DistSQL.
[INFO ] 2022-05-16 19:05:40.049 [_finished_check_Worker-1] o.a.s.d.p.core.job.FinishedCheckJob - completionDetector not configured, auto switch will not be enabled. You could query job progress and switch config manually with DistSQL.
[INFO ] 2022-05-16 19:05:50.046 [_finished_check_Worker-1] o.a.s.d.p.core.job.FinishedCheckJob - completionDetector not configured, auto switch will not be enabled. You could query job progress and switch config manually with DistSQL.
[INFO ] 2022-05-16 19:06:00.046 [_finished_check_Worker-1] o.a.s.d.p.core.job.FinishedCheckJob - completionDetector not configured, auto switch will not be enabled. You could query job progress and switch config manually with DistSQL.
[INFO ] 2022-05-16 19:06:10.042 [_finished_check_Worker-1] o.a.s.d.p.core.job.FinishedCheckJob - completionDetector not configured, auto switch will not be enabled. You could query job progress and switch config manually with DistSQL.
```
```
mysql> show scaling list;
+----------------------------------------------------+------------+----------------------+--------+---------------------+-----------+
| id | tables | sharding_total_count | active | create_time | stop_time |
+----------------------------------------------------+------------+----------------------+--------+---------------------+-----------+
| 0130317c30317c3054317c626d73716c5f7368617264696e67 | bmsql_item | 2 | true | 2022-05-16 19:05:16 | NULL |
+----------------------------------------------------+------------+----------------------+--------+---------------------+-----------+
1 row in set (0.05 sec)
mysql> show scaling status 0130317c30317c3054317c626d73716c5f7368617264696e67;
+------+-------------+--------------------------+--------+-------------------------------+--------------------------+
| item | data_source | status | active | inventory_finished_percentage | incremental_idle_seconds |
+------+-------------+--------------------------+--------+-------------------------------+--------------------------+
| 0 | ds_0 | EXECUTE_INCREMENTAL_TASK | true | 100 | 463 |
| 1 | ds_1 | EXECUTE_INCREMENTAL_TASK | true | 100 | 460 |
+------+-------------+--------------------------+--------+-------------------------------+--------------------------+
2 rows in set (0.02 sec)
mysql> show sharding scaling rules;
+--------------------+-------+--------+----------------+--------------------------------------------------------------------------+-----------------------------------------------------+
| name | input | output | stream_channel | completion_detector | data_consistency_checker |
+--------------------+-------+--------+----------------+--------------------------------------------------------------------------+-----------------------------------------------------+
| bmsql_scaling_conf | | | | {"type":"IDLE","props":{"incremental-task-idle-seconds-threshold":"60"}} | {"type":"DATA_MATCH","props":{"chunk-size":"1000"}} |
+--------------------+-------+--------+----------------+--------------------------------------------------------------------------+-----------------------------------------------------+
1 row in set (0.01 sec)
```
--
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] TeslaCN closed issue #17708: `completionDetector not configured` appeared in logs while detector was configured
Posted by GitBox <gi...@apache.org>.
TeslaCN closed issue #17708: `completionDetector not configured` appeared in logs while detector was configured
URL: https://github.com/apache/shardingsphere/issues/17708
--
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] TeslaCN commented on issue #17708: `completionDetector not configured` appeared in logs while detector was configured
Posted by GitBox <gi...@apache.org>.
TeslaCN commented on issue #17708:
URL: https://github.com/apache/shardingsphere/issues/17708#issuecomment-1128348609
This issue is caused by `scalingName` didn't matched the config name under `scaling`. The `scalingName` in configuration is regarded as something like `activeConfiguration`.
--
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