Skip to content

Commit

Permalink
build docs
Browse files Browse the repository at this point in the history
  • Loading branch information
Ben Osheroff committed Nov 26, 2015
1 parent c6d057a commit 235e2b6
Show file tree
Hide file tree
Showing 3 changed files with 10 additions and 8 deletions.
4 changes: 3 additions & 1 deletion compat/index.html
Expand Up @@ -108,7 +108,9 @@ <h3 id="unsupported">Unsupported</h3>
<h3 id="master-recovery">Master recovery</h3>
<p>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.</p></div>
and start again. We plan on improving master recovery in future releases.</p>
<p>If you know the starting position of your new master, you can start the new Maxwell process with the
<code>--init_position</code> flag, which will ensure that no gap appears in a master failover.</p></div>
</div>


Expand Down
2 changes: 1 addition & 1 deletion mkdocs/search_index.json
Expand Up @@ -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"
}
]
Expand Down
12 changes: 6 additions & 6 deletions sitemap.xml
Expand Up @@ -4,47 +4,47 @@

<url>
<loc>None/</loc>
<lastmod>2015-11-25</lastmod>
<lastmod>2015-11-26</lastmod>
<changefreq>daily</changefreq>
</url>



<url>
<loc>None/quickstart/</loc>
<lastmod>2015-11-25</lastmod>
<lastmod>2015-11-26</lastmod>
<changefreq>daily</changefreq>
</url>



<url>
<loc>None/config/</loc>
<lastmod>2015-11-25</lastmod>
<lastmod>2015-11-26</lastmod>
<changefreq>daily</changefreq>
</url>



<url>
<loc>None/kafka/</loc>
<lastmod>2015-11-25</lastmod>
<lastmod>2015-11-26</lastmod>
<changefreq>daily</changefreq>
</url>



<url>
<loc>None/dataformat/</loc>
<lastmod>2015-11-25</lastmod>
<lastmod>2015-11-26</lastmod>
<changefreq>daily</changefreq>
</url>



<url>
<loc>None/compat/</loc>
<lastmod>2015-11-25</lastmod>
<lastmod>2015-11-26</lastmod>
<changefreq>daily</changefreq>
</url>

Expand Down

0 comments on commit 235e2b6

Please sign in to comment.