• 

      <ul id="0c1fb"></ul>
      

      <noscript id="0c1fb"><video id="0c1fb"></video></noscript>
      <noscript id="0c1fb"><listing id="0c1fb"><thead id="0c1fb"></thead></listing></noscript>
      

      99热在线精品一区二区三区_国产伦精品一区二区三区女破破_亚洲一区二区三区无码_精品国产欧美日韩另类一区
      


      
    
      
        
      
            
        
      
        
        
       
      
    
      

      


      
    

      

      
    
      
        
      RELATEED CONSULTING
      
        
      相關咨詢
      
    
      
    
      
        
      選擇下列產(chǎn)品馬上在線溝通
      
        
        
      服務時間：8:30-17:00
      
    
      
    
      
        
      你可能遇到了下面的問題
      
        
    
      
    
       關閉右側工具欄 
      

      



      
    
      
        
      
            
      
                
                
      
                    
      
                        
      
                            
      
                                
      新聞中心
      
                                
       這里有您想知道的互聯(lián)網(wǎng)營銷解決方案 
      
                            
      
                            
        
                                
      • 
                                
      • 
                                
      • 
                                
      • 
                                
      • 
                                
      • 
                                
      • 
                                
      • 
                                
      • 
                                
      • 
                            
      
                        
      
                    
      
                
      
                
                
      
                    
      
                        
      
                            
      
                                
      
                                    
      
                                        
      
                                            
      
                                                
      mysqlPXC集群腦裂及grastate.dat修改實驗
      
                                            
      
                                            
      
                                                
            
      三臺服務器做了

MySQL PXC

集群
      創(chuàng)新互聯(lián)公司是一家專注網(wǎng)站建設、網(wǎng)絡營銷策劃、微信小程序開發(fā)、電子商務建設、網(wǎng)絡推廣、移動互聯(lián)開發(fā)、研究、服務為一體的技術型公司。公司成立十年以來，已經(jīng)為近1000家成都酒樓設計各業(yè)的企業(yè)公司提供互聯(lián)網(wǎng)服務。現(xiàn)在，服務的近1000家客戶與我們一路同行，見證我們的成長；未來，我們一起分享成功的喜悅。
      172.31.217.182  bd-dev-mingshuo-182
      172.31.217.183  bd-dev-mingshuo-183
      172.31.217.89   bd-dev-vertica-89
       
      正常關閉

183

一個節(jié)點
      mysqladmin -uroot -poracle -S /u01/mysql/3307/data/mysql.sock -P3307 shutdown
       
      關閉節(jié)點

log

：
      

      2018-09-27T07:33:13.222079Z   0 [Note] WSREP: Received shutdown signal. Will sleep for 10 secs before   initiating shutdown. pxc_maint_mode switched to SHUTDOWN
      2018-09-27T07:33:23.230509Z   0 [Note] WSREP: Stop replication
      2018-09-27T07:33:23.230619Z   0 [Note] WSREP: Closing send monitor...
      2018-09-27T07:33:23.230640Z   0 [Note] WSREP: Closed send monitor.
      2018-09-27T07:33:23.230660Z   0 [Note] WSREP: gcomm: terminating thread
      2018-09-27T07:33:23.230680Z   0 [Note] WSREP: gcomm: joining thread
      2018-09-27T07:33:23.230827Z   0 [Note] WSREP: gcomm: closing backend
      2018-09-27T07:33:23.231780Z   0 [Note] WSREP: Current view of cluster as seen by this node
      view   (view_id(NON_PRIM,12f1e199,11)
      memb {
              12f1e199,0
              }
      joined {
              }
      left {
              }
      partitioned {
              2331d3d7,0
              c05737fd,0
              }
      )
      2018-09-27T07:33:23.231867Z   0 [Note] WSREP: Current view of cluster as seen by this node
      view ((empty))
      2018-09-27T07:33:23.232111Z   0 [Note] WSREP: gcomm: closed
      2018-09-27T07:33:23.232165Z   0 [Note] WSREP: New COMPONENT: primary = no, bootstrap = no, my_idx = 0,   memb_num = 1
      2018-09-27T07:33:23.232253Z   0 [Note] WSREP: Flow-control interval: [100, 100]
      2018-09-27T07:33:23.232260Z   0 [Note] WSREP: Trying to continue unpaused monitor
      2018-09-27T07:33:23.232264Z   0 [Note] WSREP: Received NON-PRIMARY.
      2018-09-27T07:33:23.232268Z   0 [Note] WSREP: Shifting SYNCED -> OPEN (TO: 27)
      2018-09-27T07:33:23.232279Z   0 [Note] WSREP: Received self-leave message.
      2018-09-27T07:33:23.232285Z   0 [Note] WSREP: Flow-control interval: [0, 0]
      2018-09-27T07:33:23.232288Z   0 [Note] WSREP: Trying to continue unpaused monitor
      2018-09-27T07:33:23.232291Z   0 [Note] WSREP: Received SELF-LEAVE. Closing connection.
      2018-09-27T07:33:23.232295Z   0 [Note] WSREP: Shifting OPEN -> CLOSED (TO: 27)
      2018-09-27T07:33:23.232302Z   0 [Note] WSREP: RECV thread exiting 0: Success
      2018-09-27T07:33:23.232383Z   2 [Note] WSREP: New cluster view: global state:   c057dbc5-c16e-11e8-a1a6-825ed9079934:27, view# -1: non-Primary, number of   nodes: 1, my index: 0, protocol version 3
      2018-09-27T07:33:23.232394Z   2 [Note] WSREP: Setting wsrep_ready to false
      2018-09-27T07:33:23.232400Z   2 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
      2018-09-27T07:33:23.232439Z   2 [Note] WSREP: New cluster view: global state:   c057dbc5-c16e-11e8-a1a6-825ed9079934:27, view# -1: non-Primary, number of   nodes: 0, my index: -1, protocol version 3
      2018-09-27T07:33:23.232443Z   2 [Note] WSREP: Setting wsrep_ready to false
      2018-09-27T07:33:23.232446Z   2 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
      2018-09-27T07:33:23.232472Z   2 [Note] WSREP: applier thread exiting (code:0)
      2018-09-27T07:33:23.232479Z   0 [Note] WSREP: recv_thread() joined.
      2018-09-27T07:33:23.232502Z   0 [Note] WSREP: Closing replication queue.
      2018-09-27T07:33:23.232509Z   0 [Note] WSREP: Closing slave action queue.
      2018-09-27T07:33:23.232517Z   0 [Note] Giving 2 client threads a chance to die gracefully
      2018-09-27T07:33:25.232639Z   0 [Note] WSREP: Waiting for active wsrep applier to exit
      2018-09-27T07:33:25.232758Z   1 [Note] WSREP: rollbacker thread exiting
      2018-09-27T07:33:25.232994Z   0 [Note] Giving 0 client threads a chance to die gracefully
      2018-09-27T07:33:25.233010Z   0 [Note] Shutting down slave threads
      2018-09-27T07:33:25.233025Z   0 [Note] Forcefully disconnecting 0 remaining clients
      2018-09-27T07:33:25.233044Z   0 [Note] Event Scheduler: Purging the queue. 0 events
      2018-09-27T07:33:25.242788Z   0 [Note] WSREP: Service thread queue flushed.
      2018-09-27T07:33:25.250399Z   0 [Note] WSREP: MemPool(SlaveTrxHandle): hit ratio: 0, misses: 0, in use: 0,   in pool: 0
      2018-09-27T07:33:25.250479Z   0 [Note] WSREP: Shifting CLOSED -> DESTROYED (TO: 27)
      2018-09-27T07:33:25.259428Z   0 [Note] Binlog end
      2018-09-27T07:33:25.261702Z   0 [Note] Shutting down plugin 'ngram'
      2018-09-27T07:33:25.261721Z   0 [Note] Shutting down plugin 'partition'
      2018-09-27T07:33:25.261726Z   0 [Note] Shutting down plugin 'ARCHIVE'
      2018-09-27T07:33:25.261729Z   0 [Note] Shutting down plugin 'BLACKHOLE'
      2018-09-27T07:33:25.261733Z   0 [Note] Shutting down plugin 'INNODB_SYS_VIRTUAL'
      2018-09-27T07:33:25.261736Z   0 [Note] Shutting down plugin 'INNODB_CHANGED_PAGES'
      2018-09-27T07:33:25.261739Z   0 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
      2018-09-27T07:33:25.261741Z   0 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
      2018-09-27T07:33:25.261744Z   0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
      2018-09-27T07:33:25.261746Z   0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
      2018-09-27T07:33:25.261749Z   0 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
      2018-09-27T07:33:25.261751Z   0 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
      2018-09-27T07:33:25.261754Z   0 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
      2018-09-27T07:33:25.261756Z   0 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
      2018-09-27T07:33:25.261759Z   0 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
      2018-09-27T07:33:25.261761Z   0 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
      2018-09-27T07:33:25.261764Z   0 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
      2018-09-27T07:33:25.261766Z   0 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
      2018-09-27T07:33:25.261769Z   0 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
      2018-09-27T07:33:25.261771Z   0 [Note] Shutting down plugin 'INNODB_FT_DELETED'
      2018-09-27T07:33:25.261774Z   0 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
      2018-09-27T07:33:25.261776Z   0 [Note] Shutting down plugin 'INNODB_METRICS'
      2018-09-27T07:33:25.261778Z   0 [Note] Shutting down plugin 'INNODB_TEMP_TABLE_INFO'
      2018-09-27T07:33:25.261781Z   0 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
      2018-09-27T07:33:25.261783Z   0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
      2018-09-27T07:33:25.261785Z   0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
      2018-09-27T07:33:25.261788Z   0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
      2018-09-27T07:33:25.261790Z   0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
      2018-09-27T07:33:25.261793Z   0 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
      2018-09-27T07:33:25.261795Z   0 [Note] Shutting down plugin 'INNODB_CMPMEM'
      2018-09-27T07:33:25.261797Z   0 [Note] Shutting down plugin 'INNODB_CMP_RESET'
      2018-09-27T07:33:25.261800Z   0 [Note] Shutting down plugin 'INNODB_CMP'
      2018-09-27T07:33:25.261802Z   0 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
      2018-09-27T07:33:25.261805Z   0 [Note] Shutting down plugin 'INNODB_LOCKS'
      2018-09-27T07:33:25.261807Z   0 [Note] Shutting down plugin 'INNODB_TRX'
      2018-09-27T07:33:25.261809Z   0 [Note] Shutting down plugin 'XTRADB_ZIP_DICT_COLS'
      2018-09-27T07:33:25.261812Z   0 [Note] Shutting down plugin 'XTRADB_ZIP_DICT'
      2018-09-27T07:33:25.261814Z   0 [Note] Shutting down plugin 'XTRADB_RSEG'
      2018-09-27T07:33:25.261817Z   0 [Note] Shutting down plugin 'XTRADB_INTERNAL_HASH_TABLES'
      2018-09-27T07:33:25.261819Z   0 [Note] Shutting down plugin 'XTRADB_READ_VIEW'
      2018-09-27T07:33:25.261822Z   0 [Note] Shutting down plugin 'InnoDB'
      2018-09-27T07:33:25.261857Z   0 [Note] InnoDB: FTS optimize thread exiting.
      2018-09-27T07:33:25.262097Z   0 [Note] InnoDB: Starting shutdown...
      2018-09-27T07:33:25.362428Z   0 [Note] InnoDB: Dumping buffer pool(s) to   /u01/mysql/3307/data/ib_buffer_pool
      2018-09-27T07:33:25.363022Z   0 [Note] InnoDB: Buffer pool(s) dump completed at 180927 15:33:25
      2018-09-27T07:33:25.562786Z   0 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
      2018-09-27T07:33:26.571050Z   0 [Note] InnoDB: Shutdown completed; log sequence number 2569669
      2018-09-27T07:33:26.574169Z   0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2018-09-27T07:33:26.574193Z   0 [Note] Shutting down plugin 'MyISAM'
      2018-09-27T07:33:26.574210Z   0 [Note] Shutting down plugin 'MRG_MYISAM'
      2018-09-27T07:33:26.574222Z   0 [Note] Shutting down plugin 'CSV'
      2018-09-27T07:33:26.574233Z   0 [Note] Shutting down plugin 'MEMORY'
      2018-09-27T07:33:26.574254Z   0 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
      2018-09-27T07:33:26.574287Z   0 [Note] Shutting down plugin 'sha256_password'
      2018-09-27T07:33:26.574296Z   0 [Note] Shutting down plugin 'mysql_native_password'
      2018-09-27T07:33:26.574304Z   0 [Note] Shutting down plugin 'wsrep'
      2018-09-27T07:33:26.574480Z   0 [Note] Shutting down plugin 'binlog'
      		

      
      

       
      正常節(jié)點

log
      

      2018-09-27T07:33:22.505216Z   0 [Note] WSREP: declaring c05737fd at tcp://172.31.217.89:4567 stable
      2018-09-27T07:33:22.505345Z   0 [Note] WSREP: forgetting 12f1e199 (tcp://172.31.217.183:4567)
      2018-09-27T07:33:22.511586Z   0 [Note] WSREP: Node 2331d3d7 state primary
      2018-09-27T07:33:22.512245Z   0 [Note] WSREP: Current view of cluster as seen by this node
      view   (view_id(PRIM,2331d3d7,12)
      memb {
              2331d3d7,0
              c05737fd,0
              }
      joined {
              }
      left {
              }
      partitioned {
              12f1e199,0
              }
      )
      2018-09-27T07:33:22.512303Z   0 [Note] WSREP: Save the discovered primary-component to disk
      2018-09-27T07:33:22.512547Z   0 [Note] WSREP: New COMPONENT: primary = yes, bootstrap = no, my_idx = 0,   memb_num = 2
      2018-09-27T07:33:22.513157Z   0 [Note] WSREP: forgetting 12f1e199 (tcp://172.31.217.183:4567)
      2018-09-27T07:33:22.513241Z   0 [Note] WSREP: STATE_EXCHANGE: sent state UUID:   9ccf0351-c227-11e8-ae6a-d3cac5b411a7
      2018-09-27T07:33:22.514096Z   0 [Note] WSREP: STATE EXCHANGE: sent state msg:   9ccf0351-c227-11e8-ae6a-d3cac5b411a7
      2018-09-27T07:33:22.514647Z   0 [Note] WSREP: STATE EXCHANGE: got state msg: 9ccf0351-c227-11e8-ae6a-d3cac5b411a7   from 0 (bd-dev-mingshuo-182)
      2018-09-27T07:33:22.514661Z   0 [Note] WSREP: STATE EXCHANGE: got state msg:   9ccf0351-c227-11e8-ae6a-d3cac5b411a7 from 1 (bd-dev-vertica-89)
      2018-09-27T07:33:22.514669Z   0 [Note] WSREP: Quorum results:
              version    = 4,
              component  = PRIMARY,
              conf_id    = 11,
              members    = 2/2 (primary/total),
              act_id     = 27,
              last_appl. = 0,
              protocols  = 0/8/3 (gcs/repl/appl),
              group UUID =   c057dbc5-c16e-11e8-a1a6-825ed9079934
      2018-09-27T07:33:22.514675Z   0 [Note] WSREP: Flow-control interval: [141, 141]
      2018-09-27T07:33:22.514679Z   0 [Note] WSREP: Trying to continue unpaused monitor
      2018-09-27T07:33:22.514707Z   2 [Note] WSREP: New cluster view: global state:   c057dbc5-c16e-11e8-a1a6-825ed9079934:27, view# 12: Primary, number of nodes:   2, my index: 0, protocol version 3
      2018-09-27T07:33:22.514713Z   2 [Note] WSREP: Setting wsrep_ready to true
      2018-09-27T07:33:22.514719Z   2 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
      2018-09-27T07:33:22.514727Z   2 [Note] WSREP: REPL Protocols: 8 (3, 2)
      2018-09-27T07:33:22.514747Z   2 [Note] WSREP: Assign initial position for certification: 27, protocol   version: 3
      2018-09-27T07:33:22.514830Z   0 [Note] WSREP: Service thread queue flushed.
      2018-09-27T07:33:27.691129Z   0 [Note] WSREP:  cleaning up 12f1e199   (tcp://172.31.217.183:4567)
      		

      
      

       
      182

節(jié)點插入數(shù)據(jù)
      

      mysql> insert   into t1 values (4,4);
      Query OK, 1 row   affected (0.01 sec)
       
      mysql> select   * from t1;
      +---+------+
      | a | b    |
      +---+------+
      | 1 |    1 |
      | 2 |    2 |
      | 3 |    3 |
      | 4 |    4 |
      +---+------+
      4 rows in set   (0.00 sec)
      		

      
      

       
       
      啟動

183

節(jié)點
      

      mysql -S   /u01/mysql/3307/data/mysql.sock -uroot -poracle -P3307
      mysql> select   * from t1;
      +---+------+
      | a | b    |
      +---+------+
      | 1 |    1 |
      | 2 |    2 |
      | 3 |    3 |
      | 4 |    4 |
      +---+------+
      4 rows in set   (0.00 sec)
      		

      
      

      增量數(shù)據(jù)已經(jīng)同步過來了。
       
      下面是日志增量應用部分，可以看到收到了一個事務。
      

      2018-09-27T08:05:50.785769Z   0 [Note] WSREP: Signalling provider to continue on SST completion.
      2018-09-27T08:05:50.785808Z   0 [Note] WSREP: Initialized wsrep sidno 2
      2018-09-27T08:05:50.785833Z   0 [Note] WSREP: SST received: c057dbc5-c16e-11e8-a1a6-825ed9079934:27
      2018-09-27T08:05:50.785872Z   2 [Note] WSREP: Receiving IST: 1 writesets, seqnos 27-28
      2018-09-27T08:05:50.785985Z   0 [Note]
      2018-09-27T08:05:50.785985Z   0 [Note] WSREP: Receiving IST...  0.0%   (0/1 events) complete.
      2018-09-27T08:05:50.877679Z   0 [Note] WSREP: Receiving IST...100.0% (1/1 events) complete.
      2018-09-27T08:05:50.877904Z   2 [Note] WSREP: IST received: c057dbc5-c16e-11e8-a1a6-825ed9079934:28
      2018-09-27T08:05:50.878589Z   0 [Note] WSREP: 1.0 (bd-dev-mingshuo-183): State transfer from 0.0   (bd-dev-mingshuo-182) complete.
      2018-09-27T08:05:50.878603Z   0 [Note] WSREP: SST leaving flow control
      2018-09-27T08:05:50.878608Z   0 [Note] WSREP: Shifting JOINER -> JOINED (TO: 28)
      2018-09-27T08:05:50.879059Z   0 [Note] WSREP: Member 1.0 (bd-dev-mingshuo-183) synced with group.
      2018-09-27T08:05:50.879072Z   0 [Note] WSREP: Shifting JOINED -> SYNCED (TO: 28)
      2018-09-27T08:05:50.879101Z   2 [Note] WSREP: Synchronized with group, ready for connections
      2018-09-27T08:05:50.879115Z   2 [Note] WSREP: Setting wsrep_ready to true
      		

      
      

       
      現(xiàn)在測試直接非正常關閉兩個節(jié)點
      將

182

和

183

兩個節(jié)點進程直接

kill -9

殺掉
      89

存活節(jié)點：
      

      mysql> select   * from ming.t1;
      ERROR   1047 (08S01): WSREP has not yet prepared node for application use
      mysql> insert   into ming.t1 values(10,10);
      ERROR   1047 (08S01): WSREP has not yet prepared node for application use
      		

      
      

      存活節(jié)點已經(jīng)無法正常提供讀寫服務。
       
      

      mysql> show   status where Variable_name IN   ('wsrep_local_state_uuid','wsrep_cluster_conf_id','wsrep_cluster_size',   'wsrep_cluster_status','wsrep_ready','wsrep_connected');
      +------------------------+--------------------------------------+
      |   Variable_name          | Value                                |
      +------------------------+--------------------------------------+
      |   wsrep_local_state_uuid | c057dbc5-c16e-11e8-a1a6-825ed9079934 |
      |   wsrep_cluster_conf_id  |   18446744073709551615                 |
      |   wsrep_cluster_size     | 1                                    |
      |   wsrep_cluster_status   |   non-Primary                          |
      |   wsrep_connected        | ON                                   |
      |   wsrep_ready            | OFF                                  |
      +------------------------+--------------------------------------+
      6 rows in set   (0.00 sec)
      		

      
      

       
      可以看到

wsrep_cluster_size=1

代表集群節(jié)點個數(shù)只剩自己了。
      wsrep_cluster_status=non-Primary

代表集群狀態(tài)不一致
      wsrep_connected=ON

代表數(shù)據(jù)庫還接受連接
      wsrep_read=OFF

代表數(shù)據(jù)庫已經(jīng)不能正常接受查詢服務了。上面的

select

語句也佐證了這一點。
       
      存活節(jié)點能否提供讀服務，取決于

wsrep_dirty_reads

參數(shù)
      

      mysql> show   variables like 'wsrep_dirty_reads';
      +-------------------+-------+
      |   Variable_name     | Value |
      +-------------------+-------+
      |   wsrep_dirty_reads | OFF   |
      +-------------------+-------+
      1 row in set   (0.00 sec)
      		

      
      

       
      wsrep_dirty_reads

是可以動態(tài)調(diào)整的。如果設置為

ON

，那么在節(jié)點狀態(tài)是

non-Primary

時，
      是可以提供讀的服務的。寫的服務還需要提升該節(jié)點為

primary

，這個是要通過其他參數(shù)設定的，
      后面會說的。
       
       
      存活節(jié)點一直在嘗試連接另外兩個節(jié)點
      

      2018-09-28T02:57:37.209095Z   0 [Note] WSREP: (725136c0, 'tcp://0.0.0.0:4567') reconnecting to 2331d3d7   (tcp://172.31.217.182:4567), attempt 960
      2018-09-28T02:58:12.714612Z   0 [Note] WSREP: (725136c0, 'tcp://0.0.0.0:4567') reconnecting to 252da778   (tcp://172.31.217.183:4567), attempt 900
      2018-09-28T02:58:22.216078Z   0 [Note] WSREP: (725136c0, 'tcp://0.0.0.0:4567') reconnecting to 2331d3d7   (tcp://172.31.217.182:4567), attempt 990
      2018-09-28T02:58:57.721850Z   0 [Note] WSREP: (725136c0, 'tcp://0.0.0.0:4567') reconnecting to 252da778   (tcp://172.31.217.183:4567), attempt 930
      2018-09-28T02:59:07.223430Z   0 [Note] WSREP: (725136c0, 'tcp://0.0.0.0:4567') reconnecting to 2331d3d7   (tcp://172.31.217.182:4567), attempt 1020
      		

      
      

       
      不能提供讀寫的原因其實就是

PXC

對集群腦裂的判斷機制還不完善，對我自己來說我是

kill

掉了兩個節(jié)點的進程。
      但是對

PXC

來說，存活節(jié)點不知道另外兩個節(jié)點的狀態(tài)，有可能另外兩個節(jié)點已經(jīng)死掉了，有可能另外兩個節(jié)點相互之間還能繼續(xù)通信對外提供服務，
      這樣一來就形成了兩個信息孤島，彼此之間不能聯(lián)系對方，所以存活節(jié)點就變成了這樣不能讀寫的狀態(tài)。
       
      拉起兩個節(jié)點后存活節(jié)點日志
      

      2018-09-28T03:04:57.003914Z   0 [Note] WSREP: (725136c0, 'tcp://0.0.0.0:4567') connection established to   252da778 tcp://172.31.217.183:4567
      2018-09-28T03:05:03.215507Z   0 [Note] WSREP: declaring 252da778 at tcp://172.31.217.183:4567 stable
      2018-09-28T03:05:03.216346Z   0 [Note] WSREP: Current view of cluster as seen by this node
      view   (view_id(NON_PRIM,252da778,30)
      memb {
              252da778,0
              725136c0,0
              }
      joined {
              }
      left {
              }
      partitioned {
              2331d3d7,0
              }
      )
      2018-09-28T03:05:03.216630Z   0 [Note] WSREP: New COMPONENT: primary = no, bootstrap = no, my_idx = 1,   memb_num = 2
      2018-09-28T03:05:03.216710Z   0 [Note] WSREP: Flow-control interval: [141, 141]
      2018-09-28T03:05:03.216718Z   0 [Note] WSREP: Trying to continue unpaused monitor
      2018-09-28T03:05:03.216723Z   0 [Note] WSREP: Received NON-PRIMARY.
      2018-09-28T03:05:03.216794Z   1 [Note] WSREP: New cluster view: global state:   c057dbc5-c16e-11e8-a1a6-825ed9079934:33, view# -1: non-Primary, number of   nodes: 2, my index: 1, protocol version 3
      2018-09-28T03:05:03.216822Z   1 [Note] WSREP: Setting wsrep_ready to false
      2018-09-28T03:05:03.216833Z   1 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
      2018-09-28T03:05:04.277523Z   0 [Note] WSREP: (725136c0, 'tcp://0.0.0.0:4567') connection established to   2331d3d7 tcp://172.31.217.182:4567
      2018-09-28T03:05:04.279018Z   0 [Note] WSREP: (725136c0, 'tcp://0.0.0.0:4567') connection established to   2331d3d7 tcp://172.31.217.182:4567
      2018-09-28T03:05:04.776965Z   0 [Note] WSREP: declaring 2331d3d7 at tcp://172.31.217.182:4567 stable
      2018-09-28T03:05:04.777019Z   0 [Note] WSREP: declaring 252da778 at tcp://172.31.217.183:4567 stable
      2018-09-28T03:05:04.777487Z   0 [Note] WSREP: re-bootstrapping prim from partitioned components
      2018-09-28T03:05:04.778262Z   0 [Note] WSREP: Current view of cluster as seen by this node
      view   (view_id(PRIM,2331d3d7,31)
      memb {
              2331d3d7,0
              252da778,0
              725136c0,0
              }
      joined {
              }
      left {
              }
      partitioned {
              }
      )
      2018-09-28T03:05:04.778307Z   0 [Note] WSREP: Save the discovered primary-component to disk
      2018-09-28T03:05:04.778588Z   0 [Note] WSREP: New COMPONENT: primary = yes, bootstrap = no, my_idx = 2,   memb_num = 3
      2018-09-28T03:05:04.778629Z   0 [Note] WSREP: STATE EXCHANGE: Waiting for state UUID.
      2018-09-28T03:05:05.277931Z   0 [Note] WSREP: STATE EXCHANGE: sent state msg:   838d4806-c2cb-11e8-8bb1-eeeae1741165
      2018-09-28T03:05:05.278435Z   0 [Note] WSREP: STATE EXCHANGE: got state msg:   838d4806-c2cb-11e8-8bb1-eeeae1741165 from 0 (bd-dev-mingshuo-182)
      2018-09-28T03:05:05.278463Z   0 [Note] WSREP: STATE EXCHANGE: got state msg:   838d4806-c2cb-11e8-8bb1-eeeae1741165 from 1 (bd-dev-mingshuo-183)
      2018-09-28T03:05:05.278470Z   0 [Note] WSREP: STATE EXCHANGE: got state msg:   838d4806-c2cb-11e8-8bb1-eeeae1741165 from 2 (bd-dev-vertica-89)
      2018-09-28T03:05:05.278490Z   0 [Warning] WSREP: Quorum: No node with complete state:
       
              Version      : 4
              Flags        : 0x1
              Protocols    : 0 / 8 / 3
              State        : NON-PRIMARY
              Desync count : 0
              Prim state   : NON-PRIMARY
              Prim UUID    : 00000000-0000-0000-0000-000000000000
              Prim    seqno  : -1
              First seqno  : -1
              Last    seqno  : 33
              Prim JOINED  : 0
              State UUID   : 838d4806-c2cb-11e8-8bb1-eeeae1741165
              Group UUID   : c057dbc5-c16e-11e8-a1a6-825ed9079934
              Name         : 'bd-dev-mingshuo-182'
              Incoming addr: '172.31.217.182:3307'
       
              Version      : 4
              Flags        : 00
              Protocols    : 0 / 8 / 3
              State        : NON-PRIMARY
              Desync count : 0
              Prim state   : NON-PRIMARY
              Prim UUID    : 00000000-0000-0000-0000-000000000000
              Prim    seqno  : -1
              First seqno  : -1
              Last    seqno  : 33
              Prim JOINED  : 0
              State UUID   : 838d4806-c2cb-11e8-8bb1-eeeae1741165
              Group UUID   : c057dbc5-c16e-11e8-a1a6-825ed9079934
              Name         : 'bd-dev-mingshuo-183'
              Incoming addr: '172.31.217.183:3307'
       
              Version      : 4
              Flags        : 0x2
              Protocols    : 0 / 8 / 3
              State        : NON-PRIMARY
              Desync count : 0
              Prim state   : SYNCED
              Prim UUID    : 19faf204-c2c7-11e8-b642-52dd65ccae43
              Prim    seqno  : 26
              First seqno  : 33
              Last    seqno  : 33
              Prim JOINED  : 2
              State UUID   : 838d4806-c2cb-11e8-8bb1-eeeae1741165
              Group UUID   : c057dbc5-c16e-11e8-a1a6-825ed9079934
              Name         : 'bd-dev-vertica-89'
              Incoming addr: '172.31.217.89:3307'
       
      2018-09-28T03:05:05.278511Z   0 [Note] WSREP: Partial re-merge of primary   19faf204-c2c7-11e8-b642-52dd65ccae43 found: 1 of 2.
      2018-09-28T03:05:05.278520Z   0 [Note] WSREP: Quorum results:
              version    = 4,
              component  = PRIMARY,
              conf_id    = 26,
              members    = 3/3 (primary/total),
              act_id     = 33,
              last_appl. = 0,
              protocols  = 0/8/3 (gcs/repl/appl),
              group UUID =   c057dbc5-c16e-11e8-a1a6-825ed9079934
      2018-09-28T03:05:05.278540Z   0 [Note] WSREP: Flow-control interval: [173, 173]
      2018-09-28T03:05:05.278544Z   0 [Note] WSREP: Trying to continue unpaused monitor
      2018-09-28T03:05:05.278548Z   0 [Note] WSREP: Restored state OPEN -> SYNCED (33)
      2018-09-28T03:05:05.278593Z   1 [Note] WSREP: New cluster view: global state:   c057dbc5-c16e-11e8-a1a6-825ed9079934:33, view# 27: Primary, number of nodes:   3, my index: 2, protocol version 3
      2018-09-28T03:05:05.278612Z   1 [Note] WSREP: Setting wsrep_ready to true
      2018-09-28T03:05:05.278621Z   1 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
      2018-09-28T03:05:05.278661Z   1 [Note] WSREP: REPL Protocols: 8 (3, 2)
      2018-09-28T03:05:05.278679Z   1 [Note] WSREP: Assign initial position for certification: 33, protocol   version: 3
      2018-09-28T03:05:05.278752Z   0 [Note] WSREP: Service thread queue flushed.
      2018-09-28T03:05:05.278828Z   1 [Note] WSREP: Synchronized with group, ready for connections
      2018-09-28T03:05:05.278849Z   1 [Note] WSREP: Setting wsrep_ready to true
      2018-09-28T03:05:05.278863Z   1 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
      2018-09-28T03:05:05.279134Z   0 [Note] WSREP: Member 0.0 (bd-dev-mingshuo-182) synced with group.
      2018-09-28T03:05:05.279179Z   0 [Note] WSREP: Member 1.0 (bd-dev-mingshuo-183) synced with group.
      2018-09-28T03:05:07.290328Z   0 [Note] WSREP: (725136c0, 'tcp://0.0.0.0:4567') turning message relay   requesting off
      		

      
      

       
       
       
      出現(xiàn)腦裂后解決方法：
      

      SET GLOBAL   wsrep_provider_options='pc.bootstrap=YES';
      		

      
      

       
       
      三個節(jié)點正常關閉
      依次關閉

183,182,89

三個節(jié)點
      啟動的之前，一定要看一下

grastate.dat

文件內(nèi)容
      183

節(jié)點
      

      root@bd-dev-mingshuo-183:/u01/mysql/3307/data#more   grastate.dat
      # GALERA saved   state
      version: 2.1
      uuid:    c057dbc5-c16e-11e8-a1a6-825ed9079934
      seqno:   51
      safe_to_bootstrap:   0
       
      		

      
      

       
      182

節(jié)點
      

      root@bd-dev-mingshuo-182:/opt/mysql/3307/data#more   grastate.dat
      # GALERA saved state
      version: 2.1
      uuid:    c057dbc5-c16e-11e8-a1a6-825ed9079934
      seqno:   51
      safe_to_bootstrap:   0
      		

      
      

       
      89

節(jié)點
      

      root@bd-dev-vertica-89:/opt/mysql/3307/data#more   grastate.dat
      # GALERA saved   state
      version: 2.1
      uuid:    c057dbc5-c16e-11e8-a1a6-825ed9079934
      seqno:   51
      safe_to_bootstrap:   1
      		

      
      

       
      注意：
      safe_to_bootstrap=1

的節(jié)點，說明這個節(jié)點是可以安全的作為主節(jié)點啟動的。所以啟動的時候必須先啟動

89

節(jié)點。
       
       
      mysqld_safe --defaults-file=/etc/my.cnf --wsrep-new-cluster &
      mysqld_safe --defaults-file=/etc/my3307.cnf &
      mysqld_safe --defaults-file=/etc/my3307.cnf &
       
       
      疑問：

mysql PXC

在啟動時是不是只是按照

grastate.dat

的

safe_to_bootstrap

來驗證集群呢？
      這個很好證明，還是按照上面的做法關閉集群，然后修改

183

的

grastate.dat

的

safe_to_bootstrap

值為

1.
      實驗過程省略，但是這樣做確實是可以啟動集群的。
       
       
      如果在關閉部分節(jié)點后有數(shù)據(jù)變化呢？
      關閉

183,182

節(jié)點后，在

89

節(jié)點插入數(shù)據(jù)
      

      mysql> insert   into ming.t1 values (16,16);
      Query OK, 1 row   affected (0.01 sec)
       
      		

      
      

      然后關閉

89

節(jié)點。至此集群全部關閉。
       
      修改

183

的節(jié)點的

grastate.dat
      

      root@bd-dev-mingshuo-183:/u01/mysql/3307/data#more   grastate.dat
      # GALERA saved   state
      version: 2.1
      uuid:    c057dbc5-c16e-11e8-a1a6-825ed9079934
      seqno:   51
      safe_to_bootstrap:   1
      		

      
      

       
       
      啟動集群，先啟動

183

節(jié)點：
      

      mysqld_safe   --defaults-file=/etc/my3307.cnf --wsrep-new-cluster &
      mysql> select   * from ming.t1;
      +----+------+
      | a  | b      |
      +----+------+
      |  1 |      1 |
      |  2 |      2 |
      |  3 |      3 |
      |  4 |      4 |
      |  5 |      5 |
      |  6 |      6 |
      |  7 |      7 |
      |  8 |      8 |
      |  9 |      9 |
      | 10 |   10 |
      | 11 |   11 |
      | 12 |   12 |
      | 13 |   13 |
      | 14 |   14 |
      | 15 |   15 |
      +----+------+
      15 rows in set   (0.00 sec)
      		

      
      

      16

那行數(shù)據(jù)丟失了。
       
      再去啟動

89

節(jié)點，看看丟失的數(shù)據(jù)能否找回來
      

      2018-09-28T08:13:33.156722Z   0 [ERROR] WSREP: gcs/src/gcs_group.cpp:group_post_state_exchange():322:   Reversing history: 52 -> 51, this member has applied 1 more events than   the primary component.Data loss is possible. Aborting.
      		

      
      

       
      89

節(jié)點的日志序列已經(jīng)到了

52

，超過了其他節(jié)點的

51.

修改

89

節(jié)點日志序列為

51

，然后再嘗試啟動

89

節(jié)點
      

      mysqld_safe   --defaults-file=/etc/my.cnf &
       
      mysql> select   * from ming.t1;
      +----+------+
      | a  | b      |
      +----+------+
      |  1 |      1 |
      |  2 |      2 |
      |  3 |      3 |
      |  4 |      4 |
      |  5 |      5 |
      |  6 |      6 |
      |  7 |      7 |
      |  8 |      8 |
      |  9 |      9 |
      | 10 |   10 |
      | 11 |   11 |
      | 12 |   12 |
      | 13 |   13 |
      | 14 |   14 |
      | 15 |   15 |
      | 16 |   16 |
      +----+------+
      16 rows in set   (0.01 sec)
      		

      
      

      但是

183

節(jié)點的數(shù)據(jù)還是

15

條。
       
      183

節(jié)點刪除一條數(shù)據(jù)
      

      mysql> delete   from ming.t1 where a=11;
      Query OK, 1 row   affected (0.00 sec)
      		

      
      

       
      兩個存活節(jié)點都刪除了

11

這條數(shù)據(jù)。
       
      啟動

182

節(jié)點，可以正常啟動，啟動后檢查數(shù)據(jù)，數(shù)據(jù)與

183

一致，推測數(shù)據(jù)的

donor

節(jié)點被選擇成了

183
      

      2018-09-28T08:21:19.486736Z   2 [Note] WSREP: Check if state gap can be serviced using IST
      2018-09-28T08:21:19.486832Z   2 [Note] WSREP: IST receiver addr using tcp://172.31.217.182:4568
      2018-09-28T08:21:19.487026Z   2 [Note] WSREP: 

Prepared IST receiver, listening at:   tcp://172.31.217.182:4568
      2018-09-28T08:21:19.487050Z   2 [Note] WSREP: State gap can be likely serviced using IST. SST request   though present would be void.
      2018-09-28T08:21:19.487984Z   0 [Note] WSREP: may fallback to sst. ist_seqno [51] < safe_ist_seqno [52]
      2018-09-28T08:21:19.488006Z   0 [Note] WSREP: Member 2.0 (bd-dev-mingshuo-182) requested state transfer   from '*any*'. 

Selected 0.0   (bd-dev-mingshuo-183)(SYNCED) as donor.
      		

      
      

      日志中可以看到，

182

節(jié)點被選擇成為

IST receiver

，監(jiān)聽端口

4568

端口。選擇

183

節(jié)點作為
      數(shù)據(jù)的

donor

。那么數(shù)據(jù)與

183

一致也就不足為奇了。
       
      此時數(shù)據(jù)出現(xiàn)了不一致，如何解決呢？
      可以刪除節(jié)點數(shù)據(jù)目錄下文件，然后按照啟動，通過

SST

全量恢復數(shù)據(jù)。
       
      Pxc

啟動時可以人為選擇數(shù)據(jù)的

doner

節(jié)點。
      wsrep_sst_donor

參數(shù)
      關閉兩個節(jié)點，加

wsrep_sst_donor

參數(shù)重新啟動
      

      mysqld_safe   --defaults-file=/etc/my3307.cnf --

wsrep_sst_donor=172.31.217.89
   &
      mysqld_safe   --defaults-file=/etc/my3307.cnf --

wsrep_sst_donor=172.31.217.89
   &
      		

      
      

       

                  
            
                                                            
      
                                                網(wǎng)頁題目：mysqlPXC集群腦裂及grastate.dat修改實驗                                                
      
                                                標題網(wǎng)址：http://www.ef60e0e.cn/article/iecpie.html
                                            
      
                                            
                                        
      
                                    
      
                                
      
                            
      
                        
      
                    
      
                
      
            
      
        
      
    
      

      




99热在线精品一区二区三区_国产伦精品一区二区三区女破破_亚洲一区二区三区无码_精品国产欧美日韩另类一区 

    3. 

        <ul id="0c1fb"></ul>
        

        <noscript id="0c1fb"><video id="0c1fb"></video></noscript>
        <noscript id="0c1fb"><listing id="0c1fb"><thead id="0c1fb"></thead></listing></noscript>
        
贵定县|
肃南|
白玉县|
碌曲县|
保亭|
西乡县|
新巴尔虎左旗|
石屏县|
葫芦岛市|
临清市|
新余市|
衡阳县|
双流县|
那曲县|
曲靖市|
鄂州市|
堆龙德庆县|
如皋市|
丹江口市|
中卫市|
怀远县|
新兴县|
神农架林区|
剑川县|
屯昌县|
海城市|
永登县|
万全县|
沧源|
开阳县|
青川县|
焉耆|
隆林|
漠河县|
平定县|
寿宁县|
高阳县|
桐梓县|
北海市|
涡阳县|
武汉市|