Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-5877

New User Experience Challenges

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 23.10.5
    • N/A
    • None

    Description

      Error Messages
      1) what is bad in the query, what isnt supported (in their case CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP )

      ERROR 1178 (42000): The storage engine for the table doesn't support The syntax or the data type(s) is not supported by Columnstore. Please check the Columnstore syntax guide for supported syntax or data types.
      

      ideally: The storage engine for the table doesn't support CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP

      2) What does this mean, what location of the storage where to read more

      ERROR 1815 (HY000): Internal error: CAL0009: (6)Create table failed due to WE: Error creating column file for oid 5581; MCS-2012: Not able to add extent; adding extent would exceed max file system disk usage
      

      potential: adding extent would exceed max file system disk usage as configured by x.x in columnstore.xml

      3) should also include that -c is the read buffer flag or where to read more about cpimport

      cpimport.bin[3547476]: 52.704232 |0|0|0| E 34 CAL0087: BulkLoad Error: Error reading import file /Backup_storage/info_columnstore/hqi-fsc-dm-test/pdi_step_logging.csv; near line 4; Single row fills read buffer; try larger read buffer.
      

      potential: Single row fills read buffer of xxxx bytes; try larger read buffer via -c flag in cpimport

      4) SKIP

      5) SKIP - MCOL-5908 was created to be its own ticket
      user has no idea what went wrong or why its erroring or what to do about it

      Internal error: TupleAggregateStep::threadedAggregateRowGroups()[2] MCS-2058: Unknown Error
      

      ideally: exemgr ran out of ram, etc any further details so that the user knows or can guess what to adjust about the query

      6) note to parameter that can redefine where the disk join happens , where to learn more about disk joins

      CAL0000: DiskJoinStep::largeReader() Disk join could not write file /tmp/columnstore_tmp_files/joins//Columnstore-join-data-11578-large: No space left on device#012 %10%
      

      potential solution: Disk join could not write to configured path <key1>.<key2> in columnstore.xml - /tmp/columnstore_tmp_files/joins//Columnstore-join-data-11578 xxxxxx
      note to parameter that can redefine where the disk join happens , where to learn more about disk joins

      7) SKIP - https://jira.mariadb.org/browse/MCOL-5525
      At least in 23.02 and early 23.10 (unsure on latest) if cmapi is installed and mcs start or shutdown is run while x-api-key is not configured /etc/columnstore/cmapi_config.cnf
      The error message to the user could be way clearer indicating the file path and variable to check

      mcsShutdown resulting in 401 Unauthorized, No API key provided  customer doesnt know what to do
      

      8) SKIP - MCOL-6067 was created to be its own ticket
      What does this even mean, or what is the user supposed to do

      ERROR 1815 (HY000): Internal error: MCS-2004: Cannot connect to ExeMgr.
      

      split error message in two ( plugin error vs ddl/dml proc errors )
      potential: ERROR 1815 (HY000): Internal error: MCS-2004: Cannot connect to ExeMgr. Please check every node is running primproc process, consider restarting columnstore if this error persists.
      ddl/dml proc errors: suggest restarting mariadb
      ask @roman

      9) Again, what does this even mean, or what is the user supposed to do

      ERROR 1815 (HY000): Internal error: MCS-2033: Error occurred when calling system catalog.
      

      if this is a new installation, reinstall.
      if existing install, please open a support tickets with logs gathered

      10) where and what is being saved and why does it matter

      CAL0000: ExtentMap::save(): open: Permission denied
      

      Potential: CAL0000: ExtentMap::save(): open: Permission denied - Full file path: , suggested permissions etc.

      11) https://jira.mariadb.org/browse/MCOL-6162
      debug.log / message log that logs errors in query execution should reference query trans ID, or easily traceable which specific query failed. as written both of these messages are terrible

      Apr  8 08:57:25 mcs1prod ddlpackageproc[529551]: 25.882922 |0|0|0| E 23 CAL0009: Error in dropping table from systables. MCS-2045: At least one PrimProc closed the connection unexpectedly.
       
      Apr  8 08:59:26 mcs1prod dmlpackageproc[529518]: 26.766687 |0|0|0| E 21 CAL0001: dmlprocessor.cpp PackageHandler::run() package type 2 MCS-2045: At least one PrimProc closed the connection unexpectedly.
      

      include the reference query trans ID in the error message

      Attachments

        Issue Links

          Activity

            People

              kristina Kristina Pavlova
              allen.herrera Allen Herrera
              Votes:
              1 Vote for this issue
              Watchers:
              3 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.