[jira] [Created] (IMPALA-5322) Potential crash in Frontend & Catalog JNI startup

["bharath v (JIRA)" <ji...@apache.org>]

bharath v created IMPALA-5322:
---------------------------------

             Summary: Potential crash in Frontend & Catalog JNI startup
                 Key: IMPALA-5322
                 URL: https://issues.apache.org/jira/browse/IMPALA-5322
             Project: IMPALA
          Issue Type: Bug
          Components: Backend
    Affects Versions: Impala 2.8.0
            Reporter: bharath v
            Assignee: bharath v
            Priority: Critical
             Fix For: Impala 2.9.0


{noformat}
 cfg.__set_load_auth_to_local_rules(FLAGS_load_auth_to_local_rules);
  cfg.__set_principal(FLAGS_principal);
  cfg.__set_impala_log_lvl(FlagToTLogLevel(FLAGS_v));
  cfg.__set_non_impala_java_vlog(FlagToTLogLevel(FLAGS_non_impala_java_vlog));
  cfg.__set_inc_stats_size_limit_bytes(FLAGS_inc_stats_size_limit_bytes);
  cfg.__set_lineage_event_log_dir(FLAGS_lineage_event_log_dir);
  cfg.__set_local_library_path(FLAGS_local_library_dir);
  cfg.__set_kudu_operation_timeout_ms(FLAGS_kudu_operation_timeout_ms);
  JniLocalFrame jni_frame; <---
  RETURN_IF_ERROR(jni_frame.push(jni_env));  <----
  RETURN_IF_ERROR(SerializeThriftMsg(jni_env, &cfg, cfg_bytes));
  return Status::OK();
{noformat}

We use a local frame that could be GC'ed by the JVM. There is no need to use it. This was found in testing where we instantiate multiple fe instances.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)