Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-4442

FE ParserTests may report UnsatisfiedLinkError

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • Impala 2.8.0
    • Impala 2.8.0
    • Infrastructure

    Description

      In some development environments, the ParserTests may always fail with an UnsatisfiedLinkError:

      java.lang.UnsatisfiedLinkError: org.apache.impala.service.FeSupport.NativeGetStartupOptions()[B
      	at org.apache.impala.service.FeSupport.NativeGetStartupOptions(Native Method)
      	at org.apache.impala.service.FeSupport.GetStartupOptions(FeSupport.java:268)
      	at org.apache.impala.common.RuntimeEnv.<init>(RuntimeEnv.java:47)
      	at org.apache.impala.common.RuntimeEnv.<clinit>(RuntimeEnv.java:34)
      	at org.apache.impala.testutil.TestUtils.assumeKuduIsSupported(TestUtils.java:288)
      	at org.apache.impala.analysis.ParserTest.TestKuduUpdate(ParserTest.java:1697)
      

      lv reported seeing this last month, while no others saw this. As of this morning, I started to experience the same issue.

      I believe the issue is related to some static loading of classes and/or libraries in Java because changing the ParserTest to initialize the Frontend makes the error go away. I haven't been able to pin-point the exact issue with loading, but it makes sense that the ParserTest should initialize the Frontend static state if it will be called by libfesupport later since it seems to be an issue affecting some environments and not others, i.e. subject to environmental factors.

      Attachments

        Activity

          People

            mjacobs Matthew Jacobs
            mjacobs Matthew Jacobs
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: