Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-28868

wsrep_incoming_address status variable prints 0 as port number if the port is not mentioned in wsrep_node_incoming_address system variable

Details

    Description

      wsrep_incoming_address status variable prints 0 as port number if the port is not mentioned in wsrep_node_incoming_address system variable.

      MariaDB [(none)]> show status like '%wsrep%add%';
      +--------------------------+------------------+
      | Variable_name            | Value            |
      +--------------------------+------------------+
      | wsrep_incoming_addresses | 192.168.100.10:0 |
      +--------------------------+------------------+
      1 row in set (0.002 sec)
       
      MariaDB [(none)]>
      vagrant@node1:~$ grep address my.cnf 
      bind-address                   = 0.0.0.0
      wsrep_cluster_address=gcomm://192.168.100.10,192.168.100.20,192.168.100.30
      wsrep_sst_receive_address=192.168.100.10
      wsrep_node_address=192.168.100.10
      wsrep_node_incoming_address=192.168.100.10
      vagrant@node1:~$
       
      MariaDB [(none)]> select @@version;
      +--------------------------+
      | @@version                |
      +--------------------------+
      | 10.9.2-MariaDB-debug-log |
      +--------------------------+
      1 row in set (0.000 sec)
       
      MariaDB [(none)]> 
      
      

      Attachments

        Activity

          ramesh Ramesh Sivaraman created issue -
          ramesh Ramesh Sivaraman made changes -
          Field Original Value New Value
          Affects Version/s 10.4 [ 22408 ]
          Affects Version/s 10.5 [ 23123 ]
          Affects Version/s 10.6 [ 24028 ]
          Affects Version/s 10.7 [ 24805 ]
          Affects Version/s 10.8 [ 26121 ]
          ramesh Ramesh Sivaraman made changes -
          Fix Version/s 10.4 [ 22408 ]
          Fix Version/s 10.5 [ 23123 ]
          Fix Version/s 10.6 [ 24028 ]
          Fix Version/s 10.7 [ 24805 ]
          Fix Version/s 10.8 [ 26121 ]
          jplindst Jan Lindström (Inactive) made changes -
          Priority Major [ 3 ] Critical [ 2 ]
          pramod.mahto@mariadb.com Pramod Mahto added a comment - - edited

          wsrep_on=1
          wsrep_node_name=gcn_01
          wsrep_cluster_name=Galera_Cluster
          wsrep_node_address=192.168.47.29
          wsrep_sst_receive_address=192.168.47.29:7777
          wsrep_cluster_address=gcomm://192.168.47.29,192.168.47.30,192.168.47.31

          MariaDB [(none)]> select version();
          +---------------------+
          | version()           |
          +---------------------+
          | 10.3.36-MariaDB-log |
          +---------------------+
          1 row in set (0.000 sec)
           
          MariaDB [(none)]> show status like '%wsrep_incoming%';
          +--------------------------+--------------------+
          | Variable_name            | Value              |
          +--------------------------+--------------------+
          | wsrep_incoming_addresses | 192.168.47.29:3306 |
          +--------------------------+--------------------+
           
           
           
           
          MariaDB [(none)]> select version();
          +---------------------+
          | version()           |
          +---------------------+
          | 10.4.26-MariaDB-log |
          +---------------------+
          1 row in set (0.000 sec)
           
          MariaDB [(none)]> show status like '%wsrep_incoming%';
          +--------------------------+--------------------+
          | Variable_name            | Value              |
          +--------------------------+--------------------+
          | wsrep_incoming_addresses | 192.168.47.29:0    |
          +--------------------------+--------------------+
          

          pramod.mahto@mariadb.com Pramod Mahto added a comment - - edited wsrep_on=1 wsrep_node_name=gcn_01 wsrep_cluster_name=Galera_Cluster wsrep_node_address=192.168.47.29 wsrep_sst_receive_address=192.168.47.29:7777 wsrep_cluster_address=gcomm://192.168.47.29,192.168.47.30,192.168.47.31 MariaDB [(none)]> select version(); +---------------------+ | version() | +---------------------+ | 10.3.36-MariaDB-log | +---------------------+ 1 row in set (0.000 sec)   MariaDB [(none)]> show status like '%wsrep_incoming%'; +--------------------------+--------------------+ | Variable_name | Value | +--------------------------+--------------------+ | wsrep_incoming_addresses | 192.168.47.29:3306 | +--------------------------+--------------------+         MariaDB [(none)]> select version(); +---------------------+ | version() | +---------------------+ | 10.4.26-MariaDB-log | +---------------------+ 1 row in set (0.000 sec)   MariaDB [(none)]> show status like '%wsrep_incoming%'; +--------------------------+--------------------+ | Variable_name | Value | +--------------------------+--------------------+ | wsrep_incoming_addresses | 192.168.47.29:0 | +--------------------------+--------------------+
          jplindst Jan Lindström (Inactive) made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          jplindst Jan Lindström (Inactive) made changes -
          issue.field.resolutiondate 2022-09-22 11:31:16.0 2022-09-22 11:31:16.784
          jplindst Jan Lindström (Inactive) made changes -
          Fix Version/s 10.4.27 [ 28405 ]
          Fix Version/s 10.5.18 [ 28421 ]
          Fix Version/s 10.6.11 [ 28441 ]
          Fix Version/s 10.7.7 [ 28442 ]
          Fix Version/s 10.8.6 [ 28443 ]
          Fix Version/s 10.9.4 [ 28444 ]
          Fix Version/s 10.10.2 [ 28410 ]
          Fix Version/s 10.4 [ 22408 ]
          Fix Version/s 10.5 [ 23123 ]
          Fix Version/s 10.6 [ 24028 ]
          Fix Version/s 10.7 [ 24805 ]
          Fix Version/s 10.8 [ 26121 ]
          Fix Version/s 10.9 [ 26905 ]
          Fix Version/s 10.10 [ 27530 ]
          Resolution Fixed [ 1 ]
          Status In Progress [ 3 ] Closed [ 6 ]
          Debaro Marcos Ramos added a comment - - edited

          Hello everyone, I am having the same problem with MaridaDB 11.0.2, but this is my first bug report ever. It would be nice if you added this version to the list of affected versions and maybe reopened the issue? I don't think I can do it myself. Here is my output. I think the bug might also be stopping my nodes from resolving IPs correctly and finding each other? I started a thread on stack exchange and here is the output I get from my instance.

          -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

          Variable_name Value

          -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

          wsrep_local_state_uuid 232842bc-2a5b-11ee-9942-1224fb5b0d29
          wsrep_protocol_version 10
          wsrep_last_committed 330
          wsrep_replicated 252
          wsrep_replicated_bytes 92112
          wsrep_repl_keys 986
          wsrep_repl_keys_bytes 13936
          wsrep_repl_data_bytes 61281
          wsrep_repl_other_bytes 0
          wsrep_received 3
          wsrep_received_bytes 152
          wsrep_local_commits 218
          wsrep_local_cert_failures 0
          wsrep_local_replays 0
          wsrep_local_send_queue 0
          wsrep_local_send_queue_max 1
          wsrep_local_send_queue_min 0
          wsrep_local_send_queue_avg 0
          wsrep_local_recv_queue 0
          wsrep_local_recv_queue_max 2
          wsrep_local_recv_queue_min 0
          wsrep_local_recv_queue_avg 0.333333
          wsrep_local_cached_downto 1
          wsrep_flow_control_paused_ns 0
          wsrep_flow_control_paused 0
          wsrep_flow_control_sent 0
          wsrep_flow_control_recv 0
          wsrep_flow_control_active false
          wsrep_flow_control_requested false
          wsrep_cert_deps_distance 34.7778
          wsrep_apply_oooe 0
          wsrep_apply_oool 0
          wsrep_apply_window 1
          wsrep_apply_waits 0
          wsrep_commit_oooe 0
          wsrep_commit_oool 0
          wsrep_commit_window 1
          wsrep_local_state 4
          wsrep_local_state_comment Synced
          wsrep_cert_index_size 103
          wsrep_causal_reads 0
          wsrep_cert_interval 0
          wsrep_open_transactions 0
          wsrep_open_connections 0
          wsrep_incoming_addresses 192.168.50.1:0
          wsrep_cluster_weight 1
          wsrep_desync_count 0
          wsrep_evs_delayed  
          wsrep_evs_evict_list  
          wsrep_evs_repl_latency 0/0/0/0/0
          wsrep_evs_state OPERATIONAL
          wsrep_gcomm_uuid a58d9b00-2c06-11ee-a234-268a7a230a30
          wsrep_gmcast_segment 0
          wsrep_applier_thread_count 1
          wsrep_cluster_capabilities  
          wsrep_cluster_conf_id 1
          wsrep_cluster_size 1
          wsrep_cluster_state_uuid 232842bc-2a5b-11ee-9942-1224fb5b0d29
          wsrep_cluster_status Primary
          wsrep_connected ON
          wsrep_local_bf_aborts 0
          wsrep_local_index 0
          wsrep_provider_capabilities :MULTI_MASTER:CERTIFICATION:PARALLEL_APPLYING:TRX_REPLAY:ISOLATION:PAUSE:CAUSAL_READS:INCREMENTAL_WRITESET:UNORDERED:PREORDERED:STREAMING:NBO:
          wsrep_provider_name Galera
          wsrep_provider_vendor Codership Oy <info@codership.com>
          wsrep_provider_version 26.4.14(rXXXX)
          wsrep_ready ON
          wsrep_rollbacker_thread_count 1
          wsrep_thread_count 2

          -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

          Debaro Marcos Ramos added a comment - - edited Hello everyone, I am having the same problem with MaridaDB 11.0.2, but this is my first bug report ever. It would be nice if you added this version to the list of affected versions and maybe reopened the issue? I don't think I can do it myself. Here is my output. I think the bug might also be stopping my nodes from resolving IPs correctly and finding each other? I started a thread on stack exchange and here is the output I get from my instance. ------------------------------ -----------------------------------------------------------------------------------------------------------------------------------------------+ Variable_name Value ------------------------------ -----------------------------------------------------------------------------------------------------------------------------------------------+ wsrep_local_state_uuid 232842bc-2a5b-11ee-9942-1224fb5b0d29 wsrep_protocol_version 10 wsrep_last_committed 330 wsrep_replicated 252 wsrep_replicated_bytes 92112 wsrep_repl_keys 986 wsrep_repl_keys_bytes 13936 wsrep_repl_data_bytes 61281 wsrep_repl_other_bytes 0 wsrep_received 3 wsrep_received_bytes 152 wsrep_local_commits 218 wsrep_local_cert_failures 0 wsrep_local_replays 0 wsrep_local_send_queue 0 wsrep_local_send_queue_max 1 wsrep_local_send_queue_min 0 wsrep_local_send_queue_avg 0 wsrep_local_recv_queue 0 wsrep_local_recv_queue_max 2 wsrep_local_recv_queue_min 0 wsrep_local_recv_queue_avg 0.333333 wsrep_local_cached_downto 1 wsrep_flow_control_paused_ns 0 wsrep_flow_control_paused 0 wsrep_flow_control_sent 0 wsrep_flow_control_recv 0 wsrep_flow_control_active false wsrep_flow_control_requested false wsrep_cert_deps_distance 34.7778 wsrep_apply_oooe 0 wsrep_apply_oool 0 wsrep_apply_window 1 wsrep_apply_waits 0 wsrep_commit_oooe 0 wsrep_commit_oool 0 wsrep_commit_window 1 wsrep_local_state 4 wsrep_local_state_comment Synced wsrep_cert_index_size 103 wsrep_causal_reads 0 wsrep_cert_interval 0 wsrep_open_transactions 0 wsrep_open_connections 0 wsrep_incoming_addresses 192.168.50.1:0 wsrep_cluster_weight 1 wsrep_desync_count 0 wsrep_evs_delayed   wsrep_evs_evict_list   wsrep_evs_repl_latency 0/0/0/0/0 wsrep_evs_state OPERATIONAL wsrep_gcomm_uuid a58d9b00-2c06-11ee-a234-268a7a230a30 wsrep_gmcast_segment 0 wsrep_applier_thread_count 1 wsrep_cluster_capabilities   wsrep_cluster_conf_id 1 wsrep_cluster_size 1 wsrep_cluster_state_uuid 232842bc-2a5b-11ee-9942-1224fb5b0d29 wsrep_cluster_status Primary wsrep_connected ON wsrep_local_bf_aborts 0 wsrep_local_index 0 wsrep_provider_capabilities :MULTI_MASTER:CERTIFICATION:PARALLEL_APPLYING:TRX_REPLAY:ISOLATION:PAUSE:CAUSAL_READS:INCREMENTAL_WRITESET:UNORDERED:PREORDERED:STREAMING:NBO: wsrep_provider_name Galera wsrep_provider_vendor Codership Oy <info@codership.com> wsrep_provider_version 26.4.14(rXXXX) wsrep_ready ON wsrep_rollbacker_thread_count 1 wsrep_thread_count 2 ------------------------------ -----------------------------------------------------------------------------------------------------------------------------------------------+
          mariadb-jira-automation Jira Automation (IT) made changes -
          Zendesk Related Tickets 137217

          People

            jplindst Jan Lindström (Inactive)
            ramesh Ramesh Sivaraman
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.