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 2020/05/15 06:22:34 UTC

[GitHub] [shardingsphere] henrypoter edited a comment on issue #5598: sharding-proxy process disappear without any error log

henrypoter edited a comment on issue #5598:
URL: https://github.com/apache/shardingsphere/issues/5598#issuecomment-629051357


   > > sharding-proxy process disappear without any error log
   > 
   > @henrypoter
   > It's probably caused by an OutOfMemoryError.
   > I want to exclude the environment factor at first. Please provide the information below:
   > 
   > 1. The topology of your deploy. How many machines? And where are the sharding-proxy/sharding-scaling/MySQL deployed?
   > 2. The hardware and software description in detail. Include at least CPU, memory, any software(including operating system) versions.
   > 3. The JVM options of the instance of sharding-proxy and sharding-scaling. At least include memory options.
   > 4. Other instances in every machine. At least include instance which require large memory.
   > 5. Configurations of sharding-proxy and sharding-scaling. (You can mask ip address and password if necessary.)
   > 6. How much data you want to sync in total? And how much completed before the proxy crashed?
   > 
   > Please answer these questions straightforwardly and rawly without any analysis or process. Thanks.
   
   ## 1
    I deploy proxy and scaling on a single centos server. And start with the default start.sh script.
   On the centos,  I deployed a rocketmq, but only few message sent to it.
   
   MySQL server is deployed seperatly.  
   
   ## 2
   system info :
   [rocketmq@rocketmq182 ~]$ free -hm
                total       used       free     shared    buffers     cached
   Mem:          3.7G       3.6G       117M       156K        50M        61M
   -/+ buffers/cache:       3.5G       229M
   Swap:         2.0G       846M       1.1G`
   
   [rocketmq@rocketmq182` ~]$ lscpu
   Architecture:          x86_64
   CPU op-mode(s):        32-bit, 64-bit
   Byte Order:            Little Endian
   CPU(s):                4
   On-line CPU(s) list:   0-3
   Thread(s) per core:    1
   Core(s) per socket:    1
   Socket(s):             4
   NUMA node(s):          1
   Vendor ID:             GenuineIntel
   CPU family:            6
   Model:                 62
   Model name:            Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz
   Stepping:              4
   CPU MHz:               2100.000
   BogoMIPS:              4200.00
   Hypervisor vendor:     VMware
   Virtualization type:   full
   L1d cache:             32K
   L1i cache:             32K
   L2 cache:              256K
   L3 cache:              15360K
   NUMA node0 CPU(s):     0-3
   [rocketmq@rocketmq182 ~]$ df -h
   Filesystem            Size  Used Avail Use% Mounted on
   /dev/mapper/vg_rocketmq179-LogVol01
                          28G  5.6G   21G  22% /
   tmpfs                 1.9G  344K  1.9G   1% /dev/shm
   /dev/sda1             190M   75M  105M  42% /boot
   
   ##  3
   
   `rocketmq  2110     1  4 May14 ?        00:59:29 java -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -server -Xmx2g -Xms2g -Xmn1g -Xss256k -XX:+DisableExplicitGC -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:LargePageSizeInBytes=128m -XX:+UseFastAccessorMethods -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=70 -classpath .:/home/rocketmq/sharding/apache-shardingsphere-4.1.0-sharding-scaling-bin/conf:/home/rocketmq/sharding/apache-shardingsphere-4.1.0-sharding-scaling-bin/lib/* org.apache.shardingsphere.shardingscaling.Bootstrap
   rocketmq  2144     1 14 May14 ?        02:57:14 java -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -server -Xmx2g -Xms2g -Xmn1g -Xss256k -XX:+DisableExplicitGC -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:LargePageSizeInBytes=128m -XX:+UseFastAccessorMethods -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=70 -classpath .:..:/home/rocketmq/sharding/apache-shardingsphere-4.1.0-sharding-proxy-bin/lib/*:/home/rocketmq/sharding/apache-shardingsphere-4.1.0-sharding-proxy-bin/lib/*:/home/rocketmq/sharding/apache-shardingsphere-4.1.0-sharding-proxy-bin/ext-lib/* org.apache.shardingsphere.shardingproxy.Bootstrap
   rocketmq  3438  3413  0 14:00 pts/1    00:00:00 grep sharding`
   
   
   ## 4
   None
   
   ## 5
   ### proxy
   [rocketmq@rocketmq182 conf]$ cat server.yaml
   authentication:
     users:
       root:
         password: root
       sharding:
         password: sharding 
         authorizedSchemas: biz_suite_hzm
     
   props:
     max.connections.size.per.query: 16
     acceptor.size: 16  # The default value is available processors count * 2.
     executor.size: 16  # Infinite by default.
     sql.show: false
   
   ### proxy sharding rule
   [rocketmq@rocketmq182 conf]$ cat config-sharding.yaml 
   
   schemaName: biz_suite_hzm
   
   dataSources:
     ds_0:
       url: jdbc:mysql://192.168.1.2:3306/biz_suite_hzm?serverTimezone=UTC&useSSL=false
       username: ***
       password: ****
       connectionTimeoutMilliseconds: 30000
       idleTimeoutMilliseconds: 60000
       maxLifetimeMilliseconds: 1800000
       maxPoolSize: 100
   
   shardingRule:
     tables:
       t_scheduling_time:
         actualDataNodes: ds_0.t_scheduling_time_${0..15}
         tableStrategy:
           inline:
             shardingColumn: department_id
             algorithmExpression: t_scheduling_time_${department_id % 16}
     defaultDatabaseStrategy:
       none:
     defaultTableStrategy:
       none:
   
   ### scaling
   [rocketmq@rocketmq182 conf]$ cat server.yaml 
   
   port: 8888
   blockQueueSize: 10000
   pushTimeout: 1000
   workerThread: 30
   
   ## 6
    About  5000w rows for sync.
   1000w+ synced before proxy shutdown. It all depends. 
   
   
   Thanks for you help.


----------------------------------------------------------------
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