Query Not Using Index as Expected

I an using phpMyAdmin with MariaDB Server version: 10.3.31-MariaDB-0ubuntu0.20.04.1-log - Ubuntu 20.04. My Linux version is actually Mint 20.2. I decided to look "under the hood" with phpAdmin's "Advisor" to check things out. I have what should be considered a small home database. I have not observed any performance concerns, but based on what the "Advisor" is reporting in phpMyAdmin, I have significant "tuning" concerns. I believe that I may have narrowed one issue down to the variable "handler_read_rnd". The following query serves as an example:

Select IssueIDNUM, IssueDate, MagazineName 
    FROM tblMagazineIssueList
	JOIN tblMagazineList
        ON MagazineIDNUM = MagazineNUM 
	ORDER BY  IssueDate DESC, MagazineNUM,IssueIDNUM;

MagazineIDNUM is the primary key in tblMagazineIssueList.
MagazineNUM is a foreign key in tblMagazineIssueList which derives from the primary key in tblMagazineList

The slow query log did not show anything after the query was run. However, the query immediately prior to the query above did show-up in the slow query log.

slow query log reports:
--------------------------------------------------------------------------

---------------------------------------------------------------
Slow query log ends here. Nothing below the "ORDER BY". As such the slow query log does not identify any problem with the query.

After refreshing the tab "status", the following red items increased in value:
--------------------------------------------------------------
"handler_read_rnd" went from 80.4 k to 82.6K
"handler_read_rnd" went from 27 to 29

All other "notifications" in red, remained the same.
---------------------------------------------------------------

The message associate with the variable "handler_read_rnd" reads: "The number of requests to read a row based on a fixed position. This is high if you are doing a lot of queries that require sorting of the result. You probably have a lot of queries that require MySQL to scan whole tables or you have joins that don't use keys properly."

I suspect the message above means that something, but what, is wrong?

-----------------------------------------------------------------------------------------
Increased the values of some variables by x100 (added two 00) as an attempt to eliminate the variables below as a potential issue. These changes are probably unnecessary as this is a small database for home use and not an enterprise sized database. Included for reference purposes.

tmp_table_size=1677721600 #Default=16777216
max_heap_table_size=1677721600 #Default=16777216
table_open_cache=20000 #Default=2000
key_buffer_size=1342177280 #Default=134217728
sort_buffer_size=209715200 #Default=2097152