You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2019/10/10 09:52:42 UTC

[GitHub] [incubator-shardingsphere] liusf1993 opened a new issue #3211: Statement "SELECT GET_LOCK('lock10086')" doesn't work as expected

liusf1993 opened a new issue #3211: Statement "SELECT GET_LOCK('lock10086')" doesn't work as  expected
URL: https://github.com/apache/incubator-shardingsphere/issues/3211
 
 
   ```
   SELECT GET_LOCK('lock10086',1000);
   SELECT RELEASE_LOCK('lock10086');
   ```
   while executing two statements above, UnicastRoutingEngine was chosen because not logic tables is empty.
   And the first statement may be executed on database db1, second on database db2, resulting that the lock is not freed.
   Can you support an option for using DefaultDatabaseRoutingEngine while no logic table exists.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services