<h2 dir="auto">Bug Report</h2>
<p dir="auto"><strong>For English only</strong>, other languages will not accept.</p>
<p dir="auto">Before report a bug, make sure you have:</p>
<ul dir="auto">
<li>Searched open and closed <a href="https://github.com/apache/incubator-shardingsphere/issues">GitHub issues</a>.</li>
<li>Read documentation: <a href="https://shardingsphere.apache.org/document/current/en/overview" rel="nofollow">ShardingSphere Doc</a>.</li>
</ul>
<p dir="auto">Please pay attention on issues you submitted, because we maybe need more details.<br>
If no response <strong>more than 7 days</strong> and we cannot reproduce it on current information, we will <strong>close it</strong>.</p>
<p dir="auto">Please answer these questions before submitting your issue. Thanks!</p>
<h3 dir="auto">Which version of ShardingSphere did you use?</h3>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="	&lt;dependency&gt;
		&lt;groupId&gt;org.apache.shardingsphere&lt;/groupId&gt;
		&lt;artifactId&gt;sharding-jdbc-core&lt;/artifactId&gt;
		&lt;version&gt;4.0.0-RC1&lt;/version&gt;
	&lt;/dependency&gt;
	&lt;dependency&gt;
		&lt;groupId&gt;org.apache.shardingsphere&lt;/groupId&gt;
		&lt;artifactId&gt;sharding-jdbc-spring-namespace&lt;/artifactId&gt;
		&lt;version&gt;4.0.0-RC1&lt;/version&gt;
	&lt;/dependency&gt;"><pre class="notranslate"><code class="notranslate">	&lt;dependency&gt;
		&lt;groupId&gt;org.apache.shardingsphere&lt;/groupId&gt;
		&lt;artifactId&gt;sharding-jdbc-core&lt;/artifactId&gt;
		&lt;version&gt;4.0.0-RC1&lt;/version&gt;
	&lt;/dependency&gt;
	&lt;dependency&gt;
		&lt;groupId&gt;org.apache.shardingsphere&lt;/groupId&gt;
		&lt;artifactId&gt;sharding-jdbc-spring-namespace&lt;/artifactId&gt;
		&lt;version&gt;4.0.0-RC1&lt;/version&gt;
	&lt;/dependency&gt;
</code></pre></div>
<h3 dir="auto">Which project did you use? Sharding-JDBC or Sharding-Proxy?</h3>
<p dir="auto">Sharding-JDBC</p>
<h3 dir="auto">Expected behavior</h3>
<p dir="auto">want to complete in 3s</p>
<h3 dir="auto">Actual behavior</h3>
<p dir="auto">14s</p>
<h3 dir="auto">Reason analyze (If you can)</h3>
<p dir="auto">When i debug into code:<br>
class=SQLExecuteCallback<br>
method:execute0<br>
line:T result = this.executeSQL(routeUnit.getSqlUnit().getSql(), statementExecuteUnit.getStatement(), statementExecuteUnit.getConnectionMode());<br>
I found spent long</p>
<h3 dir="auto">Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.</h3>
<p dir="auto">init data-&gt;total size:1,0000,000<br>
1.execute sql script:sql:SELECT SUM(size) as size_sum FROM table_test<br>
spent: 26s<br>
2.add properties:max.tolerate.time.difference.milliseconds:8 -&gt;restart application<br>
3.execute sql script:sql:SELECT SUM(size) as size_sum FROM table_test<br>
spent:14s</p>
<h3 dir="auto">Example codes for reproduce this issue (such as a github link).</h3>
<p dir="auto">Bug Report<br>
For English only, other languages will not accept.</p>
<p dir="auto">Before report a bug, make sure you have:</p>
<p dir="auto">Searched open and closed GitHub issues.<br>
Read documentation: ShardingSphere Doc.<br>
Please pay attention on issues you submitted, because we maybe need more details.<br>
If no response anymore and we cannot reproduce it on current information, we will close it.</p>
<p dir="auto">Please answer these questions before submitting your issue. Thanks!</p>
<p dir="auto">Which version of ShardingSphere did you use?<br>
shardingsphere version: 5.0.0-RC1-SNAPSHOT<br>
shardingsphere-example version: 5.0.0-alpha</p>
<p dir="auto">Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?<br>
ShardingSphere-JDBC</p>
<p dir="auto">Expected behavior<br>
The order_id and order_item_id should include odd and even numbers respectively. But all order_id is even number and all order_item_id is odd number.</p>
<p dir="auto">Actual behavior<br>
---------------------------- Print Order Data -----------------------<br>
order_id: 609400984137347072, user_id: 1, address_id: 1, status: INSERT_TEST_JPA<br>
order_id: 609400984552583168, user_id: 2, address_id: 2, status: INSERT_TEST_JPA<br>
order_id: 609400984581943296, user_id: 3, address_id: 3, status: INSERT_TEST_JPA<br>
order_id: 609400984607109120, user_id: 4, address_id: 4, status: INSERT_TEST_JPA<br>
order_id: 609400984628080640, user_id: 5, address_id: 5, status: INSERT_TEST_JPA<br>
order_id: 609400984644857856, user_id: 6, address_id: 6, status: INSERT_TEST_JPA<br>
order_id: 609400984661635072, user_id: 7, address_id: 7, status: INSERT_TEST_JPA<br>
order_id: 609400984682606592, user_id: 8, address_id: 8, status: INSERT_TEST_JPA<br>
order_id: 609400984703578112, user_id: 9, address_id: 9, status: INSERT_TEST_JPA<br>
order_id: 609400984724549632, user_id: 10, address_id: 10, status: INSERT_TEST_JPA<br>
---------------------------- Print OrderItem Data -------------------<br>
order_item_id:609400984498057217, order_id: 609400984137347072, user_id: 1, status: INSERT_TEST_JPA<br>
order_item_id:609400984569360385, order_id: 609400984552583168, user_id: 2, status: INSERT_TEST_JPA<br>
order_item_id:609400984594526209, order_id: 609400984581943296, user_id: 3, status: INSERT_TEST_JPA<br>
order_item_id:609400984615497729, order_id: 609400984607109120, user_id: 4, status: INSERT_TEST_JPA<br>
order_item_id:609400984636469249, order_id: 609400984628080640, user_id: 5, status: INSERT_TEST_JPA<br>
order_item_id:609400984653246465, order_id: 609400984644857856, user_id: 6, status: INSERT_TEST_JPA<br>
order_item_id:609400984674217985, order_id: 609400984661635072, user_id: 7, status: INSERT_TEST_JPA<br>
order_item_id:609400984690995201, order_id: 609400984682606592, user_id: 8, status: INSERT_TEST_JPA<br>
order_item_id:609400984711966721, order_id: 609400984703578112, user_id: 9, status: INSERT_TEST_JPA<br>
order_item_id:609400984732938241, order_id: 609400984724549632, user_id: 10, status: INSERT_TEST_JPA</p>
<p dir="auto">Reason analyze (If you can)<br>
SNOWFLAKE algorithm causes data skew.<br>
I had check FAQ, <a href="https://shardingsphere.apache.org/document/current/en/faq/#12-why-are-the-default-distributed-auto-augment-key-strategy-provided-by-shardingsphere-not-continuous-and-most-of-them-end-with-even-numbers" rel="nofollow">https://shardingsphere.apache.org/document/current/en/faq/#12-why-are-the-default-distributed-auto-augment-key-strategy-provided-by-shardingsphere-not-continuous-and-most-of-them-end-with-even-numbers</a>, but it isn't the same issue.</p>
<p dir="auto">Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.<br>
run org.apache.shardingsphere.example.sharding.spring.boot.jpa.ExampleMain#main</p>
<p dir="auto">Example codes for reproduce this issue (such as a github link).<br>
application.properties:<br>
spring.profiles.active=sharding-tables</p>