Correct Mysql README + potential fix for UseBiasedLocking (#42)

* Fixed typos README.md Fixed exec command in README * Fixed jvm.config Removed UseBiasedLocking, as it resulted with invalid parameter which caused the trino-coordinator to crash. Also relates to issue: #41
bitsondatadev · Mar 28, 2024 · ce3b5dc · ce3b5dc
1 parent 07051c1
commit ce3b5dc
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 3 deletions.
diff --git a/mysql/trino-mysql/README.md b/mysql/trino-mysql/README.md
@@ -40,7 +40,7 @@ container. Notice the container id is `trino-mysql_trino-coordinator_1` so the
 command you will run is:
 
 ```
-docker container exec -it trino-mysql_trino-coordinator_1 trino
+docker container exec -it trino-mysql-trino-coordinator-1 trino
 ```
 
 When you start this step, you should see the `trino` cursor once the startup

diff --git a/mysql/trino-mysql/etc/jvm.config b/mysql/trino-mysql/etc/jvm.config
@@ -1,6 +1,5 @@
 -server
 -Xmx1G
--XX:-UseBiasedLocking
 -XX:+UseG1GC
 -XX:G1HeapRegionSize=32M
 -XX:+ExplicitGCInvokesConcurrent
@@ -9,4 +8,4 @@
 -XX:+ExitOnOutOfMemoryError
 -XX:ReservedCodeCacheSize=256M
 -Djdk.attach.allowAttachSelf=true
--Djdk.nio.maxCachedBufferSize=2000000
+-Djdk.nio.maxCachedBufferSize=2000000