You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2019/03/06 00:28:00 UTC
[jira] [Commented] (IMPALA-532) Impala should tolerate bad locale
settings.
[ https://issues.apache.org/jira/browse/IMPALA-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16785090#comment-16785090 ]
Tim Armstrong commented on IMPALA-532:
--------------------------------------
Simple repro. I think one variant of the issue might have been fixed where it crashes on startup, but it's totally reproducible by running a query.
{noformat}
$ LC_ALL="bad lang" start-impala-cluster.py && impala-shell.sh -q "select count(*) from functional.alltypes";
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (bad lang)
16:25:16 MainThread: Starting State Store logging to /home/tarmstrong/Impala/incubator-impala/logs/cluster/statestored.INFO
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (bad lang)
16:25:17 MainThread: Starting Catalog Service logging to /home/tarmstrong/Impala/incubator-impala/logs/cluster/catalogd.INFO
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (bad lang)
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (bad lang)
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (bad lang)
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (bad lang)
16:25:18 MainThread: Starting Impala Daemon logging to /home/tarmstrong/Impala/incubator-impala/logs/cluster/impalad.INFO
16:25:18 MainThread: Starting Impala Daemon logging to /home/tarmstrong/Impala/incubator-impala/logs/cluster/impalad_node1.INFO
16:25:18 MainThread: Starting Impala Daemon logging to /home/tarmstrong/Impala/incubator-impala/logs/cluster/impalad_node2.INFO
16:25:21 MainThread: Found 3 impalad/1 statestored/1 catalogd process(es)
16:25:21 MainThread: Getting num_known_live_backends from tarmstrong-box:25000
16:25:21 MainThread: 'backends'
16:25:21 MainThread: Waiting for num_known_live_backends=3. Current value: None
16:25:22 MainThread: Getting num_known_live_backends from tarmstrong-box:25000
16:25:22 MainThread: Waiting for num_known_live_backends=3. Current value: 0
16:25:23 MainThread: Getting num_known_live_backends from tarmstrong-box:25000
16:25:23 MainThread: Waiting for num_known_live_backends=3. Current value: 0
16:25:24 MainThread: Getting num_known_live_backends from tarmstrong-box:25000
16:25:24 MainThread: Waiting for num_known_live_backends=3. Current value: 0
16:25:25 MainThread: Getting num_known_live_backends from tarmstrong-box:25000
16:25:25 MainThread: Waiting for num_known_live_backends=3. Current value: 0
16:25:26 MainThread: Getting num_known_live_backends from tarmstrong-box:25000
16:25:26 MainThread: num_known_live_backends has reached value: 3
16:25:27 MainThread: Getting num_known_live_backends from tarmstrong-box:25001
16:25:27 MainThread: num_known_live_backends has reached value: 3
16:25:27 MainThread: Getting num_known_live_backends from tarmstrong-box:25002
16:25:27 MainThread: num_known_live_backends has reached value: 3
16:25:28 MainThread: Impala Cluster Running with 3 nodes (3 coordinators, 3 executors).
Starting Impala Shell without Kerberos authentication
Opened TCP connection to localhost:21000
Connected to localhost:21000
Server version: impalad version 3.2.0-SNAPSHOT DEBUG (build 2e5c45fe20e74afc24e24999a31bddbfa6fdd4f7)
Query: select count(*) from functional.alltypes
Query submitted at: 2019-03-05 16:25:28 (Coordinator: http://tarmstrong-box:25000)
Query progress can be monitored at: http://tarmstrong-box:25000/query_plan?query_id=f74cdb69fbc45292:94becc4d00000000
Socket error 104: Connection reset by peer
Could not execute command: select count(*) from functional.alltypes
{noformat}
> Impala should tolerate bad locale settings.
> -------------------------------------------
>
> Key: IMPALA-532
> URL: https://issues.apache.org/jira/browse/IMPALA-532
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 1.1
> Reporter: Ishaan Joshi
> Priority: Minor
>
> Currently, the Statestore does not tolerate a bad locale setting and crashes while starting up.
> {code}
> USE_DEBUG_BUILD=false
> + perl -pi -e 's#{{CMF_CONF_DIR}}#/var/run/cloudera-scm-agent/process/2469-impala-STATESTORE#g' /var/run/cloudera-scm-agent/process/2469-impala-STATESTORE/impala-conf/state_store_flags
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
> LANGUAGE = (unset),
> LC_ALL = (unset),
> LANG = "fr_FR.UTF-8"
> are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
> + '[' -f /var/run/cloudera-scm-agent/process/2469-impala-STATESTORE/impala-conf/.htpasswd ']'
> + chmod 600 /var/run/cloudera-scm-agent/process/2469-impala-STATESTORE/impala-conf/.htpasswd
> + false
> + export IMPALA_BIN=/opt/cloudera/parcels/IMPALA-1.1-1.p0.8/lib/impala/sbin-retail
> + IMPALA_BIN=/opt/cloudera/parcels/IMPALA-1.1-1.p0.8/lib/impala/sbin-retail
> + '[' impalad = statestore ']'
> + '[' statestore = statestore ']'
> + exec /opt/cloudera/parcels/IMPALA-1.1-1.p0.8/lib/impala/../../bin/statestored --flagfile=/var/run/cloudera-scm-agent/process/2469-impala-STATESTORE/impala-conf/state_store_flags
> terminate called after throwing an instance of 'std::runtime_error'
> what(): locale::facet::_S_create_c_locale name not valid
> {code}
> It should fall back to the standard locale ("C"), if the user's locale is messed up.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org