Understanding "active slave" in OVS with LACP and balance-tcp mode

I'm using Open vSwitch (OVS) with a bonded interface configured for LACP and balance-tcp mode. After running ovs-appctl bond/show, I see output like this:

bond-m-2274c5f6 --- 
bond mode: balance-tcp
bond may use recirculation: yes, Recirc-ID :3
bond-hash-basis:0
updelay:0 ms
downdelay:0 ms
next rebalance:9367 ms
lacp_status: negotiated
lacp fallback ab: true
active slave mac: 34:73:79:f7:77:12(ens1f1np1)

slave ens1f1np1: enabled
  active slave
  may_enable: true

slave ens4f1np1: enabled
  may_enable: true

My questions are: 1. What exactly does the active slave field mean in the context of balance-tcp mode? 2. In LACP, is there a concept of an "active" slave interface, or are all aggregated links treated equally? 3. Are there any actual differences between the two slave interfaces (e.g., ens1f1np1 vs ens4f1np1) in this setup? From my understanding, balance-tcp should distribute traffic based on a hash (TCP/IP/MAC), and both interfaces should be actively used. I just want to make sure I'm interpreting the ovs-appctl bond/show output correctly. Any insights or clarifications would be appreciated!