E.2.6. Terminology: Fields appliedLastEventId

Continuent Documentation

Manual Home

Tungsten Replicator 7.0 Manual

Page in Other Manuals

Tungsten Clustering (for MySQL) 6.1 Manual

Tungsten Clustering (for MySQL) 8.0 Manual

Tungsten Clustering (for MySQL) 7.0 Manual

Tungsten Replicator 8.0 Manual

Tungsten Clustering (for MySQL) 7.1 Manual

Tungsten MI (TMI)

Tungsten Replicator 7.1 Manual

Tungsten Replicator 6.1 Manual

Breadcrumbs

> Tungsten Replicator 7.0 Manual

> E. Terminology Reference

> E.2. Generated Field Reference

Navigate Up

E.2. Generated Field Reference

Parent Sections

E.2.1. Terminology: Fields masterConnectUri

E.2.2. Terminology: Fields masterListenUri

E.2.3. Terminology: Fields accessFailures

E.2.4. Terminology: Fields active

E.2.5. Terminology: Fields activeSeqno

E.2.6. Terminology: Fields appliedLastEventId

E.2.7. Terminology: Fields appliedLastGoodLatency

E.2.8. Terminology: Fields appliedLastGoodSeqno

E.2.9. Terminology: Fields appliedLastSeqno

E.2.10. Terminology: Fields appliedLatency

E.2.11. Terminology: Fields applier.class

E.2.12. Terminology: Fields applier.name

E.2.13. Terminology: Fields applyTime

E.2.14. Terminology: Fields autoRecoveryEnabled

E.2.15. Terminology: Fields autoRecoveryTotal

E.2.16. Terminology: Fields averageBlockSize

E.2.17. Terminology: Fields blockCommitRowCount

E.2.18. Terminology: Fields cancelled

E.2.19. Terminology: Fields channel

E.2.20. Terminology: Fields channels

E.2.21. Terminology: Fields clusterName

E.2.22. Terminology: Fields commits

E.2.23. Terminology: Fields committedMinSeqno

E.2.24. Terminology: Fields criticalPartition

E.2.25. Terminology: Fields currentBlockSize

E.2.26. Terminology: Fields currentEventId

E.2.27. Terminology: Fields currentLastEventId

E.2.28. Terminology: Fields currentLastFragno

E.2.29. Terminology: Fields currentLastSeqno

E.2.30. Terminology: Fields currentTimeMillis

E.2.31. Terminology: Fields dataServerHost

E.2.32. Terminology: Fields discardCount

E.2.33. Terminology: Fields doChecksum

E.2.34. Terminology: Fields estimatedOfflineInterval

E.2.35. Terminology: Fields eventCount

E.2.36. Terminology: Fields extensions

E.2.37. Terminology: Fields extractTime

E.2.38. Terminology: Fields extractor.class

E.2.39. Terminology: Fields extractor.name

E.2.40. Terminology: Fields filter.#.class

E.2.41. Terminology: Fields filter.#.name

E.2.42. Terminology: Fields filterTime

E.2.43. Terminology: Fields flushIntervalMillis

E.2.44. Terminology: Fields fsyncOnFlush

E.2.45. Terminology: Fields headSeqno

E.2.46. Terminology: Fields intervalGuard

E.2.47. Terminology: Fields lastCommittedBlockSize

E.2.48. Terminology: Fields lastCommittedBlockTime

E.2.49. Terminology: Fields latestEpochNumber

E.2.50. Terminology: Fields logConnectionTimeout

E.2.51. Terminology: Fields logDir

E.2.52. Terminology: Fields logFileRetainMillis

E.2.53. Terminology: Fields logFileSize

E.2.54. Terminology: Fields maxChannel

E.2.55. Terminology: Fields maxDelayInterval

E.2.56. Terminology: Fields maxOfflineInterval

E.2.57. Terminology: Fields maxSize

E.2.58. Terminology: Fields maximumStoredSeqNo

E.2.59. Terminology: Fields minimumStoredSeqNo

E.2.60. Terminology: Fields name

E.2.61. Terminology: Fields offlineRequests

E.2.62. Terminology: Fields otherTime

E.2.63. Terminology: Fields pendingError

E.2.64. Terminology: Fields pendingErrorCode

E.2.65. Terminology: Fields pendingErrorEventId

E.2.66. Terminology: Fields pendingErrorSeqno

E.2.67. Terminology: Fields pendingExceptionMessage

E.2.68. Terminology: Fields pipelineSource

E.2.69. Terminology: Fields processedMinSeqno

E.2.70. Terminology: Fields queues

E.2.71. Terminology: Fields readOnly

E.2.72. Terminology: Fields relativeLatency

E.2.73. Terminology: Fields resourcePrecedence

E.2.74. Terminology: Fields rmiPort

E.2.75. Terminology: Fields role

E.2.76. Terminology: Fields seqnoType

E.2.77. Terminology: Fields serializationCount

E.2.78. Terminology: Fields serialized

E.2.79. Terminology: Fields serviceName

E.2.80. Terminology: Fields serviceType

E.2.81. Terminology: Fields shard_id

E.2.82. Terminology: Fields simpleServiceName

E.2.83. Terminology: Fields siteName

E.2.84. Terminology: Fields sourceId

E.2.85. Terminology: Fields stage

E.2.86. Terminology: Fields started

E.2.87. Terminology: Fields state

E.2.88. Terminology: Fields stopRequested

E.2.89. Terminology: Fields store.#

E.2.90. Terminology: Fields storeClass

E.2.91. Terminology: Fields syncInterval

E.2.92. Terminology: Fields taskCount

E.2.93. Terminology: Fields taskId

E.2.94. Terminology: Fields timeInCurrentEvent

E.2.95. Terminology: Fields timeInStateSeconds

E.2.96. Terminology: Fields timeoutMillis

E.2.97. Terminology: Fields totalAssignments

E.2.98. Terminology: Fields transitioningTo

E.2.99. Terminology: Fields uptimeSeconds

E.2.100. Terminology: Fields version

E.2.6. Terminology: Fields `appliedLastEventId`
Prev	^Up	E.2. Generated Field Reference	Next

E.2.6. Terminology: Fields `appliedLastEventId`

The event ID from the source database of the last corresponding event from the stage that has been applied to the database.

MySQL

When extracting from MySQL, the output from trepctl shows the MySQL binary log file and the byte position within the log where the transaction was extracted:

shell> trepctl status
Processing status command...
NAME VALUE
---- -----
appliedLastEventId : mysql-bin.000064:0000000002757461;0
...

Prev	Up	Next
E.2.5. Terminology: Fields `activeSeqno`	^Level	E.2.7. Terminology: Fields `appliedLastGoodLatency`

Copyright © 2025 Continuent, Ltd.1 (415) 529-4901Terms of UsePrivacy & CookiesLegal NoticeExhibits