C.2.27. Services requires a reset

Continuent Documentation

Search:

Manual Home

Tungsten Clustering for MySQL 5.3 Manual

Page in Other Manuals

Tungsten Replicator 5.2 Manual

Breadcrumbs

» Tungsten Clustering for MySQL 5.3 Manual

» C. Troubleshooting

» C.2. Error/Cause/Solution

Navigate Up

C.2. Error/Cause/Solution

Parent Sections

C.2.1. Lots of entries added to replicator log

C.2.2. element 'mysql_readonly' not found in path

C.2.3. Error: could not settle on encryption_client algorithm

C.2.4. The master replicator stopped with a JDBC error.

C.2.5. Event application failed: seqno=20725782 fragno=0 message=java.sql.SQLDataException: Data too long for column 'eventid' at row 1

C.2.6. Unable to update the configuration of an installed directory

C.2.7. [S1000][unixODBC][MySQL][ODBC 5.3(w) Driver]SSL connection error: unknown error number [ISQL]ERROR: Could not SQLConnect

C.2.8. Connector shows errors with "java.net.SocketException: Broken pipe"

C.2.9. cctrl reports MANAGER(state=STOPPED)

C.2.10. Backup agent name not found: xtrabackup-full

C.2.11. Replicator runs out of memory

C.2.12. Replicator fails to connect after updating password

C.2.13. Attempt to write new log record with equal or lower fragno: seqno=3 previous stored fragno=32767 attempted new fragno=-32768

C.2.14. ORA-00257: ARCHIVER ERROR. CONNECT INTERNAL ONLY, UNTIL FREED

C.2.15. ERROR 1010 (HY000) at line 5094506: Error dropping database (can't rmdir './mysql-bin/', errno: 17)

C.2.16. ERROR 1580 (HY000) at line 5093787: You cannot 'DROP' a log table if logging is enabled

C.2.17. ERROR 2013 (HY000) at line 583: Lost connection to MySQL server during query

C.2.18. pendingExceptionMessage": "Unable to update last commit seqno: Incorrect datetime value: '2016-03-13 02:02:26' for column 'update_timestamp' at row 1

C.2.19. Too many open processes or files

C.2.20. WARN [KeepAliveTimerTask] - Error while sending a KEEP_ALIVE query to connection.

C.2.21. Latency is high: master:ONLINE, progress=41331580333, THL latency=78849.733

C.2.22. Triggers not firing correctly on slave

C.2.23. cctrl hangs

C.2.24. Missing events, or events not extracted correctly

C.2.25. Replication latency very high

C.2.26. There were issues configuring the sandbox MySQL server

C.2.27. Services requires a reset

C.2.28. trepctl status hangs

C.2.29. Starting replication after performing a restore because of an invalid restart sequence number

C.2.30. MySQL is incorrectly configured

C.2.31. Replicator reports an Out of Memory error

C.2.32. Backup/Restore is not being my host back to normal

C.2.27. Services requires a reset
Prev	C.2. Error/Cause/Solution	Next

C.2.27. Services requires a reset

Last Updated: 2016-05-18

Condition or Error

The replicator service needs to be reset, for example if your MySQL service has been reconfigured, or when resetting a data warehouse or batch loading service after a significant change to the configuration.

Causes

If the replicator stops replicating effectively, or the configuration and/or schema of a source or target in a datawarehouse loading solution has changed significantly. This will reset the service, starting extraction from the current point, and the target/slave from the new master position. It will also reset all the positions for reading and writing.

Rectifications

To reset a service entirely, without having to perform a re-installation, you should follow these steps. This will reset both the THL, source database binary log reading position and the target THL and starting point.
1. Take the slave offline:
```
slave-shell> trepctl offline
```
2. Take the master offline:
```
slave-shell> trepctl offline
```
3. Use trepctl to reset the service on the master and slave. You must use the service name explicitly on the command-line:
```
master-shell> trepctl -service alpha reset -y
slave-shell> trepctl -service alpha reset -y
```
4. Put the slave online:
```
slave-shell> trepctl offline
```
5. Put the master online:
```
slave-shell> trepctl offline
```

Prev	Up	Next
C.2.26. There were issues configuring the sandbox MySQL server	Home	C.2.28. trepctl status hangs