dmbj edited a comment on issue #7223:
URL: https://github.com/apache/shardingsphere/issues/7223#issuecomment-691757293
> @dmbj , Scaling support resume from break-point, which depends on
zookeeper service. You should setup an zookeeper service and add config.
>
> ${scaling_home}/conf/server.yaml
>
> ```yaml
> name: scalingjob
> registryCenter:
> type: zookeeper
> serverLists: localhost:2181 # your zk host
> props:
> ```
>
> restart scaling service.
>
> Focus on your exceptions: `Could not find first log file name in binary
log index file`, which means binlog has been removed before execute increase
job.
>
> So you should turn up binlog expire days.
appreciate to answer the question! In my case,as you said binlog has been
removed is the exact reason cause the exception,I contact ops found their has a
strategy to ensure disk space,But their will not intent to change that.So i
need to think another solution to solve my problem:
can scaling surpport file document read to solve increase data sync?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
