diff --git a/compat/index.html b/compat/index.html index 61ff6ac3e..e712afb97 100644 --- a/compat/index.html +++ b/compat/index.html @@ -108,7 +108,9 @@

Unsupported

Master recovery

Currently Maxwell is not very smart about master recovery or detecting a promoted slave; if it determines that the server_id has changed between runs, Maxwell will simply delete its old schema cache and binlog position -and start again. We plan on improving this situation in 0.12.

+and start again. We plan on improving master recovery in future releases.

+

If you know the starting position of your new master, you can start the new Maxwell process with the +--init_position flag, which will ensure that no gap appears in a master failover.

diff --git a/mkdocs/search_index.json b/mkdocs/search_index.json index 0046cbe59..16c1c0f09 100644 --- a/mkdocs/search_index.json +++ b/mkdocs/search_index.json @@ -27,7 +27,7 @@ }, { "location": "/compat/", - "text": "Maxwell Compatibility\n\n\n\nRequirements:\n\n\n\n\nJRE 7 or above\n\n\nmysql 5.1, 5.5, 5.6\n\n\nkafka 0.8.2 or greater\n\n\n\n\nUnsupported\n\n\n\n\nMysql 5.7 is untested with Maxwell, and in particular GTID replication is unsupported as of yet.\n\n\nbinlog_row_image=MINIMAL\n is not supported and will break Maxwell in a variety of amusing ways.\n\n\n\n\nMaster recovery\n\n\nCurrently Maxwell is not very smart about master recovery or detecting a promoted slave; if it determines\nthat the server_id has changed between runs, Maxwell will simply delete its old schema cache and binlog position\nand start again. We plan on improving this situation in 0.12.", + "text": "Maxwell Compatibility\n\n\n\nRequirements:\n\n\n\n\nJRE 7 or above\n\n\nmysql 5.1, 5.5, 5.6\n\n\nkafka 0.8.2 or greater\n\n\n\n\nUnsupported\n\n\n\n\nMysql 5.7 is untested with Maxwell, and in particular GTID replication is unsupported as of yet.\n\n\nbinlog_row_image=MINIMAL\n is not supported and will break Maxwell in a variety of amusing ways.\n\n\n\n\nMaster recovery\n\n\nCurrently Maxwell is not very smart about master recovery or detecting a promoted slave; if it determines\nthat the server_id has changed between runs, Maxwell will simply delete its old schema cache and binlog position\nand start again. We plan on improving master recovery in future releases.\n\n\nIf you know the starting position of your new master, you can start the new Maxwell process with the\n\n--init_position\n flag, which will ensure that no gap appears in a master failover.", "title": "Compat / Caveats" } ] diff --git a/sitemap.xml b/sitemap.xml index c65217453..7a27786bf 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -4,7 +4,7 @@ None/ - 2015-11-25 + 2015-11-26 daily @@ -12,7 +12,7 @@ None/quickstart/ - 2015-11-25 + 2015-11-26 daily @@ -20,7 +20,7 @@ None/config/ - 2015-11-25 + 2015-11-26 daily @@ -28,7 +28,7 @@ None/kafka/ - 2015-11-25 + 2015-11-26 daily @@ -36,7 +36,7 @@ None/dataformat/ - 2015-11-25 + 2015-11-26 daily @@ -44,7 +44,7 @@ None/compat/ - 2015-11-25 + 2015-11-26 daily