[jira] [Created] (HAWQ-1227) HAWQ init fails if User name contains capital character
Radar Lei created HAWQ-1227: --- Summary: HAWQ init fails if User name contains capital character Key: HAWQ-1227 URL: https://issues.apache.org/jira/browse/HAWQ-1227 Project: Apache HAWQ Issue Type: Bug Components: Command Line Tools Reporter: Radar Lei Assignee: Ed Espino If user name contains capital character, then HAWQ initialize will failed to load toolkit file. See log: [WARNING]:-psql:/tmp/_gp_toolkit_tmp_20161219_135052:1: ERROR: role "Tester" does not exist psql:/tmp/_gp_toolkit_tmp_20161219_135052:1: ERROR: role "tester" does not exist We should add single quote to ROLENAME in toolket sql file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HAWQ-1227) HAWQ init fails if User name contains capital character
[ https://issues.apache.org/jira/browse/HAWQ-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radar Lei reassigned HAWQ-1227: --- Assignee: Radar Lei (was: Ed Espino) > HAWQ init fails if User name contains capital character > --- > > Key: HAWQ-1227 > URL: https://issues.apache.org/jira/browse/HAWQ-1227 > Project: Apache HAWQ > Issue Type: Bug > Components: Command Line Tools >Reporter: Radar Lei >Assignee: Radar Lei > > If user name contains capital character, then HAWQ initialize will failed to > load toolkit file. > See log: > [WARNING]:-psql:/tmp/_gp_toolkit_tmp_20161219_135052:1: ERROR: role "Tester" > does not exist > psql:/tmp/_gp_toolkit_tmp_20161219_135052:1: ERROR: role "tester" does not > exist > We should add single quote to ROLENAME in toolket sql file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq pull request #1055: HAWQ-1001. Bugfix and refactor ranger log...
Github user xunzhang commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1055#discussion_r92972825 --- Diff: src/backend/libpq/rangerrest.c --- @@ -468,7 +440,7 @@ void call_ranger_rest(CURL_HANDLE curl_handle, char* request) } else { -elog(LOG, "%lu bytes retrieved from Ranger Restful API.", +elog(LOG, "%d bytes retrieved from Ranger Restful API.", --- End diff -- It should be, but this pull request is just a hotfix and small refactor. I think ranger codes should be largely refactored later on which is not relevant to this pull request. Thanks. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-hawq pull request #1055: HAWQ-1001. Bugfix and refactor ranger log...
Github user paul-guo- commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1055#discussion_r92972130 --- Diff: src/backend/libpq/rangerrest.c --- @@ -391,7 +363,7 @@ static size_t write_callback(char *contents, size_t size, size_t nitems, void *userp) { size_t realsize = size * nitems; -CURL_HANDLE curl = (struct curl_context *) userp; +CURL_HANDLE curl = (struct curl_context_t *) userp; --- End diff -- Usually if a type have a _t in end, that means no struct is needed. Either "struct curl_context" or curl_context_t. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-hawq pull request #1055: HAWQ-1001. Bugfix and refactor ranger log...
Github user paul-guo- commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1055#discussion_r92972165 --- Diff: src/backend/libpq/rangerrest.c --- @@ -468,7 +440,7 @@ void call_ranger_rest(CURL_HANDLE curl_handle, char* request) } else { -elog(LOG, "%lu bytes retrieved from Ranger Restful API.", +elog(LOG, "%d bytes retrieved from Ranger Restful API.", --- End diff -- Why not use size_t for size in struct? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-hawq pull request #1055: HAWQ-1001. Bugfix and refactor ranger log...
Github user paul-guo- commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1055#discussion_r92971978 --- Diff: src/backend/libpq/rangerrest.c --- @@ -273,10 +245,10 @@ json_object *create_ranger_request_json_batch(List *args) * } */ json_object* create_ranger_request_json(char* user, AclObjectKind kind, char* object, -List* actions, char* how) +List* actions, bool how) --- End diff -- Even change to bool, isn't another name better like is_*? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-hawq pull request #1055: HAWQ-1001. Bugfix and refactor ranger log...
Github user ictmalili commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1055#discussion_r92971308 --- Diff: src/backend/libpq/rangerrest.c --- @@ -273,10 +245,10 @@ json_object *create_ranger_request_json_batch(List *args) * } */ json_object* create_ranger_request_json(char* user, AclObjectKind kind, char* object, -List* actions, char* how) +List* actions, bool how) --- End diff -- What do we pass for "how", why change it from char* to bool? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-hawq issue #1055: HAWQ-1001. Bugfix and refactor ranger logic.
Github user xunzhang commented on the issue: https://github.com/apache/incubator-hawq/pull/1055 cc @linwen @ictmalili @zhangh43 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-hawq pull request #1055: HAWQ-1001. Bugfix and refactor ranger log...
GitHub user xunzhang opened a pull request: https://github.com/apache/incubator-hawq/pull/1055 HAWQ-1001. Bugfix and refactor ranger logic. You can merge this pull request into a Git repository by running: $ git pull https://github.com/xunzhang/incubator-hawq HAWQ-1001-BUGFIX Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq/pull/1055.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1055 commit 3568cbfb790a196e555ed067d13a7483ee872f34 Author: xunzhangDate: 2016-12-19T05:08:23Z HAWQ-1001. Bugfix and refactor ranger logic. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Assigned] (HAWQ-1226) Enable ranger while RPS is down will cause HAWQ core dump
[ https://issues.apache.org/jira/browse/HAWQ-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hongxu Ma reassigned HAWQ-1226: --- Assignee: Hongxu Ma (was: Ed Espino) > Enable ranger while RPS is down will cause HAWQ core dump > - > > Key: HAWQ-1226 > URL: https://issues.apache.org/jira/browse/HAWQ-1226 > Project: Apache HAWQ > Issue Type: Bug >Reporter: Hongxu Ma >Assignee: Hongxu Ma > > Core dump when starting hawq without starting RPS with enable_ranger is true. > {code} > (lldb) bt > * thread #1: tid = 0x, 0x7fffe9264dda > libsystem_kernel.dylib`__pthread_kill + 10, stop reason = signal SIGSTOP > * frame #0: 0x7fffe9264dda libsystem_kernel.dylib`__pthread_kill + 10 > frame #1: 0x7fffe9350787 libsystem_pthread.dylib`pthread_kill + 90 > frame #2: 0x7fffe917b497 libsystem_c.dylib`raise + 26 > frame #3: 0x00010cbdd93f > postgres`SafeHandlerForSegvBusIll(processName="Process", > postgres_signal_arg=11) + 591 at elog.c:4519 > frame #4: 0x00010cbdd6cb > postgres`StandardHandlerForSigillSigsegvSigbus_OnMainThread(processName="Process", > postgres_signal_arg=11) + 43 at elog.c:4597 > frame #5: 0x00010cab66ef > postgres`CdbProgramErrorHandler(postgres_signal_arg=11) + 319 at > postgres.c:3512 > frame #6: 0x7fffe9343bba libsystem_platform.dylib`_sigtramp + 26 > frame #7: 0x7fffe916cb53 libsystem_c.dylib`strlen + 19 > frame #8: 0x00010c951215 > postgres`parse_ranger_response(buffer=0x) + 21 at > rangerrest.c:59 > frame #9: 0x00010c951c8e > postgres`check_privilege_from_ranger(user="wuhong", kind=ACL_KIND_NAMESPACE, > object="template1", actions=0x7ff338036598, how=0x) + 254 > at rangerrest.c:339 > frame #10: 0x00010c7890c4 > postgres`pg_rangercheck(objkind=ACL_KIND_NAMESPACE, object_oid=2200, > roleid=10, mask=256, how=ACLMASK_ANY) + 164 at aclchk.c:2678 > frame #11: 0x00010c78b085 > postgres`pg_namespace_aclcheck(nsp_oid=2200, roleid=10, mode=256) + 101 at > aclchk.c:3752 > frame #12: 0x00010c77ea48 postgres`recomputeNamespacePath + 600 at > namespace.c:2010 > frame #13: 0x00010c77dec1 > postgres`RelnameGetRelid(relname="gp_segment_configuration") + 17 at > namespace.c:423 > frame #14: 0x00010c77db61 > postgres`RangeVarGetRelid(relation=0x7ff3388cef60, failOK='\0', > allowHcatalog='\x01') + 449 at namespace.c:278 > frame #15: 0x00010c671f6e > postgres`CdbOpenRelationRv(relation=0x7ff3388cef60, reqmode=3, > noWait='\0', lockUpgraded=0x) + 46 at heapam.c:1075 > frame #16: 0x00010c7f718c > postgres`setTargetTable(pstate=0x7ff3388cf460, > relation=0x7ff3388cef60, inh='\x01', alsoSource='\x01', requiredPerms=8) > + 140 at parse_clause.c:866 > frame #17: 0x00010c7b9a6e > postgres`transformDeleteStmt(pstate=0x7ff3388cf460, > stmt=0x7ff3388cf3c0) + 174 at analyze.c:943 > frame #18: 0x00010c7b5249 > postgres`transformStmt(pstate=0x7ff3388cf460, > parseTree=0x7ff3388cf3c0, extras_before=0x7fff535bcba0, > extras_after=0x7fff535bcb98) + 841 at analyze.c:769 > frame #19: 0x00010c7a5b60 > postgres`do_parse_analyze(parseTree=0x7ff3388cf3c0, > pstate=0x7ff3388cf460) + 112 at analyze.c:497 > frame #20: 0x00010c7a5acf > postgres`parse_analyze(parseTree=0x7ff3388cf3c0, sourceText="DELETE FROM > gp_segment_configuration WHERE role = 'p' or role = 'm'", > paramTypes=0x, numParams=0) + 95 at analyze.c:351 > frame #21: 0x00010cab5960 > postgres`pg_analyze_and_rewrite(parsetree=0x7ff3388cf3c0, > query_string="DELETE FROM gp_segment_configuration WHERE role = 'p' or role = > 'm'", paramTypes=0x, numParams=0) + 64 at postgres.c:812 > frame #22: 0x00010caba448 > postgres`exec_simple_query(query_string="DELETE FROM gp_segment_configuration > WHERE role = 'p' or role = 'm'", seqServerHost=0x, > seqServerPort=-1) + 1416 at postgres.c:1739 > frame #23: 0x00010cab8b15 postgres`PostgresMain(argc=8, > argv=0x7ff338818698, username="wuhong") + 7189 at postgres.c:4840 > frame #24: 0x00010ca62295 > postgres`BackendRun(port=0x7ff337416a60) + 981 at postmaster.c:5915 > frame #25: 0x00010ca5f6e5 > postgres`BackendStartup(port=0x7ff337416a60) + 373 at postmaster.c:5484 > frame #26: 0x00010ca5cbb0 postgres`ServerLoop + 1248 at > postmaster.c:2163 > frame #27: 0x00010ca5b2e3 postgres`PostmasterMain(argc=9, > argv=0x7ff337415af0) + 4835 at postmaster.c:1454 > frame #28: 0x00010c96742c postgres`main(argc=9, > argv=0x7ff337415af0) + 940 at main.c:226 > frame #29: 0x7fffe9136255 libdyld.dylib`start +
[jira] [Updated] (HAWQ-1226) Enable ranger while RPS is down will cause HAWQ core dump
[ https://issues.apache.org/jira/browse/HAWQ-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hongxu Ma updated HAWQ-1226: Description: Core dump when starting hawq without starting RPS with enable_ranger is true. {{ (lldb) bt * thread #1: tid = 0x, 0x7fffe9264dda libsystem_kernel.dylib`__pthread_kill + 10, stop reason = signal SIGSTOP * frame #0: 0x7fffe9264dda libsystem_kernel.dylib`__pthread_kill + 10 frame #1: 0x7fffe9350787 libsystem_pthread.dylib`pthread_kill + 90 frame #2: 0x7fffe917b497 libsystem_c.dylib`raise + 26 frame #3: 0x00010cbdd93f postgres`SafeHandlerForSegvBusIll(processName="Process", postgres_signal_arg=11) + 591 at elog.c:4519 frame #4: 0x00010cbdd6cb postgres`StandardHandlerForSigillSigsegvSigbus_OnMainThread(processName="Process", postgres_signal_arg=11) + 43 at elog.c:4597 frame #5: 0x00010cab66ef postgres`CdbProgramErrorHandler(postgres_signal_arg=11) + 319 at postgres.c:3512 frame #6: 0x7fffe9343bba libsystem_platform.dylib`_sigtramp + 26 frame #7: 0x7fffe916cb53 libsystem_c.dylib`strlen + 19 frame #8: 0x00010c951215 postgres`parse_ranger_response(buffer=0x) + 21 at rangerrest.c:59 frame #9: 0x00010c951c8e postgres`check_privilege_from_ranger(user="wuhong", kind=ACL_KIND_NAMESPACE, object="template1", actions=0x7ff338036598, how=0x) + 254 at rangerrest.c:339 frame #10: 0x00010c7890c4 postgres`pg_rangercheck(objkind=ACL_KIND_NAMESPACE, object_oid=2200, roleid=10, mask=256, how=ACLMASK_ANY) + 164 at aclchk.c:2678 frame #11: 0x00010c78b085 postgres`pg_namespace_aclcheck(nsp_oid=2200, roleid=10, mode=256) + 101 at aclchk.c:3752 frame #12: 0x00010c77ea48 postgres`recomputeNamespacePath + 600 at namespace.c:2010 frame #13: 0x00010c77dec1 postgres`RelnameGetRelid(relname="gp_segment_configuration") + 17 at namespace.c:423 frame #14: 0x00010c77db61 postgres`RangeVarGetRelid(relation=0x7ff3388cef60, failOK='\0', allowHcatalog='\x01') + 449 at namespace.c:278 frame #15: 0x00010c671f6e postgres`CdbOpenRelationRv(relation=0x7ff3388cef60, reqmode=3, noWait='\0', lockUpgraded=0x) + 46 at heapam.c:1075 frame #16: 0x00010c7f718c postgres`setTargetTable(pstate=0x7ff3388cf460, relation=0x7ff3388cef60, inh='\x01', alsoSource='\x01', requiredPerms=8) + 140 at parse_clause.c:866 frame #17: 0x00010c7b9a6e postgres`transformDeleteStmt(pstate=0x7ff3388cf460, stmt=0x7ff3388cf3c0) + 174 at analyze.c:943 frame #18: 0x00010c7b5249 postgres`transformStmt(pstate=0x7ff3388cf460, parseTree=0x7ff3388cf3c0, extras_before=0x7fff535bcba0, extras_after=0x7fff535bcb98) + 841 at analyze.c:769 frame #19: 0x00010c7a5b60 postgres`do_parse_analyze(parseTree=0x7ff3388cf3c0, pstate=0x7ff3388cf460) + 112 at analyze.c:497 frame #20: 0x00010c7a5acf postgres`parse_analyze(parseTree=0x7ff3388cf3c0, sourceText="DELETE FROM gp_segment_configuration WHERE role = 'p' or role = 'm'", paramTypes=0x, numParams=0) + 95 at analyze.c:351 frame #21: 0x00010cab5960 postgres`pg_analyze_and_rewrite(parsetree=0x7ff3388cf3c0, query_string="DELETE FROM gp_segment_configuration WHERE role = 'p' or role = 'm'", paramTypes=0x, numParams=0) + 64 at postgres.c:812 frame #22: 0x00010caba448 postgres`exec_simple_query(query_string="DELETE FROM gp_segment_configuration WHERE role = 'p' or role = 'm'", seqServerHost=0x, seqServerPort=-1) + 1416 at postgres.c:1739 frame #23: 0x00010cab8b15 postgres`PostgresMain(argc=8, argv=0x7ff338818698, username="wuhong") + 7189 at postgres.c:4840 frame #24: 0x00010ca62295 postgres`BackendRun(port=0x7ff337416a60) + 981 at postmaster.c:5915 frame #25: 0x00010ca5f6e5 postgres`BackendStartup(port=0x7ff337416a60) + 373 at postmaster.c:5484 frame #26: 0x00010ca5cbb0 postgres`ServerLoop + 1248 at postmaster.c:2163 frame #27: 0x00010ca5b2e3 postgres`PostmasterMain(argc=9, argv=0x7ff337415af0) + 4835 at postmaster.c:1454 frame #28: 0x00010c96742c postgres`main(argc=9, argv=0x7ff337415af0) + 940 at main.c:226 frame #29: 0x7fffe9136255 libdyld.dylib`start + 1 frame #30: 0x7fffe9136255 libdyld.dylib`start + 1 }} was: Core dump when starting hawq without starting RPS with enable_ranger is true. bq. {{ (lldb) bt * thread #1: tid = 0x, 0x7fffe9264dda libsystem_kernel.dylib`__pthread_kill + 10, stop reason = signal SIGSTOP * frame #0: 0x7fffe9264dda libsystem_kernel.dylib`__pthread_kill + 10 frame #1: 0x7fffe9350787 libsystem_pthread.dylib`pthread_kill + 90 frame #2: 0x7fffe917b497 libsystem_c.dylib`raise + 26 frame #3: 0x00010cbdd93f
[jira] [Updated] (HAWQ-1226) Enable ranger while RPS is down will cause HAWQ core dump
[ https://issues.apache.org/jira/browse/HAWQ-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hongxu Ma updated HAWQ-1226: Description: Core dump when starting hawq without starting RPS with enable_ranger is true. {code} (lldb) bt * thread #1: tid = 0x, 0x7fffe9264dda libsystem_kernel.dylib`__pthread_kill + 10, stop reason = signal SIGSTOP * frame #0: 0x7fffe9264dda libsystem_kernel.dylib`__pthread_kill + 10 frame #1: 0x7fffe9350787 libsystem_pthread.dylib`pthread_kill + 90 frame #2: 0x7fffe917b497 libsystem_c.dylib`raise + 26 frame #3: 0x00010cbdd93f postgres`SafeHandlerForSegvBusIll(processName="Process", postgres_signal_arg=11) + 591 at elog.c:4519 frame #4: 0x00010cbdd6cb postgres`StandardHandlerForSigillSigsegvSigbus_OnMainThread(processName="Process", postgres_signal_arg=11) + 43 at elog.c:4597 frame #5: 0x00010cab66ef postgres`CdbProgramErrorHandler(postgres_signal_arg=11) + 319 at postgres.c:3512 frame #6: 0x7fffe9343bba libsystem_platform.dylib`_sigtramp + 26 frame #7: 0x7fffe916cb53 libsystem_c.dylib`strlen + 19 frame #8: 0x00010c951215 postgres`parse_ranger_response(buffer=0x) + 21 at rangerrest.c:59 frame #9: 0x00010c951c8e postgres`check_privilege_from_ranger(user="wuhong", kind=ACL_KIND_NAMESPACE, object="template1", actions=0x7ff338036598, how=0x) + 254 at rangerrest.c:339 frame #10: 0x00010c7890c4 postgres`pg_rangercheck(objkind=ACL_KIND_NAMESPACE, object_oid=2200, roleid=10, mask=256, how=ACLMASK_ANY) + 164 at aclchk.c:2678 frame #11: 0x00010c78b085 postgres`pg_namespace_aclcheck(nsp_oid=2200, roleid=10, mode=256) + 101 at aclchk.c:3752 frame #12: 0x00010c77ea48 postgres`recomputeNamespacePath + 600 at namespace.c:2010 frame #13: 0x00010c77dec1 postgres`RelnameGetRelid(relname="gp_segment_configuration") + 17 at namespace.c:423 frame #14: 0x00010c77db61 postgres`RangeVarGetRelid(relation=0x7ff3388cef60, failOK='\0', allowHcatalog='\x01') + 449 at namespace.c:278 frame #15: 0x00010c671f6e postgres`CdbOpenRelationRv(relation=0x7ff3388cef60, reqmode=3, noWait='\0', lockUpgraded=0x) + 46 at heapam.c:1075 frame #16: 0x00010c7f718c postgres`setTargetTable(pstate=0x7ff3388cf460, relation=0x7ff3388cef60, inh='\x01', alsoSource='\x01', requiredPerms=8) + 140 at parse_clause.c:866 frame #17: 0x00010c7b9a6e postgres`transformDeleteStmt(pstate=0x7ff3388cf460, stmt=0x7ff3388cf3c0) + 174 at analyze.c:943 frame #18: 0x00010c7b5249 postgres`transformStmt(pstate=0x7ff3388cf460, parseTree=0x7ff3388cf3c0, extras_before=0x7fff535bcba0, extras_after=0x7fff535bcb98) + 841 at analyze.c:769 frame #19: 0x00010c7a5b60 postgres`do_parse_analyze(parseTree=0x7ff3388cf3c0, pstate=0x7ff3388cf460) + 112 at analyze.c:497 frame #20: 0x00010c7a5acf postgres`parse_analyze(parseTree=0x7ff3388cf3c0, sourceText="DELETE FROM gp_segment_configuration WHERE role = 'p' or role = 'm'", paramTypes=0x, numParams=0) + 95 at analyze.c:351 frame #21: 0x00010cab5960 postgres`pg_analyze_and_rewrite(parsetree=0x7ff3388cf3c0, query_string="DELETE FROM gp_segment_configuration WHERE role = 'p' or role = 'm'", paramTypes=0x, numParams=0) + 64 at postgres.c:812 frame #22: 0x00010caba448 postgres`exec_simple_query(query_string="DELETE FROM gp_segment_configuration WHERE role = 'p' or role = 'm'", seqServerHost=0x, seqServerPort=-1) + 1416 at postgres.c:1739 frame #23: 0x00010cab8b15 postgres`PostgresMain(argc=8, argv=0x7ff338818698, username="wuhong") + 7189 at postgres.c:4840 frame #24: 0x00010ca62295 postgres`BackendRun(port=0x7ff337416a60) + 981 at postmaster.c:5915 frame #25: 0x00010ca5f6e5 postgres`BackendStartup(port=0x7ff337416a60) + 373 at postmaster.c:5484 frame #26: 0x00010ca5cbb0 postgres`ServerLoop + 1248 at postmaster.c:2163 frame #27: 0x00010ca5b2e3 postgres`PostmasterMain(argc=9, argv=0x7ff337415af0) + 4835 at postmaster.c:1454 frame #28: 0x00010c96742c postgres`main(argc=9, argv=0x7ff337415af0) + 940 at main.c:226 frame #29: 0x7fffe9136255 libdyld.dylib`start + 1 frame #30: 0x7fffe9136255 libdyld.dylib`start + 1 {code}} was: Core dump when starting hawq without starting RPS with enable_ranger is true. {{ (lldb) bt * thread #1: tid = 0x, 0x7fffe9264dda libsystem_kernel.dylib`__pthread_kill + 10, stop reason = signal SIGSTOP * frame #0: 0x7fffe9264dda libsystem_kernel.dylib`__pthread_kill + 10 frame #1: 0x7fffe9350787 libsystem_pthread.dylib`pthread_kill + 90 frame #2: 0x7fffe917b497 libsystem_c.dylib`raise + 26 frame #3: 0x00010cbdd93f
[jira] [Created] (HAWQ-1226) Enable ranger while RPS is down will cause HAWQ core dump
Hongxu Ma created HAWQ-1226: --- Summary: Enable ranger while RPS is down will cause HAWQ core dump Key: HAWQ-1226 URL: https://issues.apache.org/jira/browse/HAWQ-1226 Project: Apache HAWQ Issue Type: Bug Reporter: Hongxu Ma Assignee: Ed Espino Core dump when starting hawq without starting RPS with enable_ranger is true. bq. {{ (lldb) bt * thread #1: tid = 0x, 0x7fffe9264dda libsystem_kernel.dylib`__pthread_kill + 10, stop reason = signal SIGSTOP * frame #0: 0x7fffe9264dda libsystem_kernel.dylib`__pthread_kill + 10 frame #1: 0x7fffe9350787 libsystem_pthread.dylib`pthread_kill + 90 frame #2: 0x7fffe917b497 libsystem_c.dylib`raise + 26 frame #3: 0x00010cbdd93f postgres`SafeHandlerForSegvBusIll(processName="Process", postgres_signal_arg=11) + 591 at elog.c:4519 frame #4: 0x00010cbdd6cb postgres`StandardHandlerForSigillSigsegvSigbus_OnMainThread(processName="Process", postgres_signal_arg=11) + 43 at elog.c:4597 frame #5: 0x00010cab66ef postgres`CdbProgramErrorHandler(postgres_signal_arg=11) + 319 at postgres.c:3512 frame #6: 0x7fffe9343bba libsystem_platform.dylib`_sigtramp + 26 frame #7: 0x7fffe916cb53 libsystem_c.dylib`strlen + 19 frame #8: 0x00010c951215 postgres`parse_ranger_response(buffer=0x) + 21 at rangerrest.c:59 frame #9: 0x00010c951c8e postgres`check_privilege_from_ranger(user="wuhong", kind=ACL_KIND_NAMESPACE, object="template1", actions=0x7ff338036598, how=0x) + 254 at rangerrest.c:339 frame #10: 0x00010c7890c4 postgres`pg_rangercheck(objkind=ACL_KIND_NAMESPACE, object_oid=2200, roleid=10, mask=256, how=ACLMASK_ANY) + 164 at aclchk.c:2678 frame #11: 0x00010c78b085 postgres`pg_namespace_aclcheck(nsp_oid=2200, roleid=10, mode=256) + 101 at aclchk.c:3752 frame #12: 0x00010c77ea48 postgres`recomputeNamespacePath + 600 at namespace.c:2010 frame #13: 0x00010c77dec1 postgres`RelnameGetRelid(relname="gp_segment_configuration") + 17 at namespace.c:423 frame #14: 0x00010c77db61 postgres`RangeVarGetRelid(relation=0x7ff3388cef60, failOK='\0', allowHcatalog='\x01') + 449 at namespace.c:278 frame #15: 0x00010c671f6e postgres`CdbOpenRelationRv(relation=0x7ff3388cef60, reqmode=3, noWait='\0', lockUpgraded=0x) + 46 at heapam.c:1075 frame #16: 0x00010c7f718c postgres`setTargetTable(pstate=0x7ff3388cf460, relation=0x7ff3388cef60, inh='\x01', alsoSource='\x01', requiredPerms=8) + 140 at parse_clause.c:866 frame #17: 0x00010c7b9a6e postgres`transformDeleteStmt(pstate=0x7ff3388cf460, stmt=0x7ff3388cf3c0) + 174 at analyze.c:943 frame #18: 0x00010c7b5249 postgres`transformStmt(pstate=0x7ff3388cf460, parseTree=0x7ff3388cf3c0, extras_before=0x7fff535bcba0, extras_after=0x7fff535bcb98) + 841 at analyze.c:769 frame #19: 0x00010c7a5b60 postgres`do_parse_analyze(parseTree=0x7ff3388cf3c0, pstate=0x7ff3388cf460) + 112 at analyze.c:497 frame #20: 0x00010c7a5acf postgres`parse_analyze(parseTree=0x7ff3388cf3c0, sourceText="DELETE FROM gp_segment_configuration WHERE role = 'p' or role = 'm'", paramTypes=0x, numParams=0) + 95 at analyze.c:351 frame #21: 0x00010cab5960 postgres`pg_analyze_and_rewrite(parsetree=0x7ff3388cf3c0, query_string="DELETE FROM gp_segment_configuration WHERE role = 'p' or role = 'm'", paramTypes=0x, numParams=0) + 64 at postgres.c:812 frame #22: 0x00010caba448 postgres`exec_simple_query(query_string="DELETE FROM gp_segment_configuration WHERE role = 'p' or role = 'm'", seqServerHost=0x, seqServerPort=-1) + 1416 at postgres.c:1739 frame #23: 0x00010cab8b15 postgres`PostgresMain(argc=8, argv=0x7ff338818698, username="wuhong") + 7189 at postgres.c:4840 frame #24: 0x00010ca62295 postgres`BackendRun(port=0x7ff337416a60) + 981 at postmaster.c:5915 frame #25: 0x00010ca5f6e5 postgres`BackendStartup(port=0x7ff337416a60) + 373 at postmaster.c:5484 frame #26: 0x00010ca5cbb0 postgres`ServerLoop + 1248 at postmaster.c:2163 frame #27: 0x00010ca5b2e3 postgres`PostmasterMain(argc=9, argv=0x7ff337415af0) + 4835 at postmaster.c:1454 frame #28: 0x00010c96742c postgres`main(argc=9, argv=0x7ff337415af0) + 940 at main.c:226 frame #29: 0x7fffe9136255 libdyld.dylib`start + 1 frame #30: 0x7fffe9136255 libdyld.dylib`start + 1 }} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq pull request #1054: HAWQ-870. Allocate target's tuple table s...
Github user interma closed the pull request at: https://github.com/apache/incubator-hawq/pull/1054 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-hawq issue #1054: HAWQ-870. Allocate target's tuple table slot in ...
Github user interma commented on the issue: https://github.com/apache/incubator-hawq/pull/1054 Thanks. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Closed] (HAWQ-870) Allocate target's tuple table slot in PortalHeapMemory during split partition
[ https://issues.apache.org/jira/browse/HAWQ-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hongxu Ma closed HAWQ-870. -- Resolution: Fixed already commit in. > Allocate target's tuple table slot in PortalHeapMemory during split partition > - > > Key: HAWQ-870 > URL: https://issues.apache.org/jira/browse/HAWQ-870 > Project: Apache HAWQ > Issue Type: Bug > Components: Query Execution >Reporter: Venkatesh >Assignee: Hongxu Ma > Fix For: backlog > > > This is a nice fix from QP team on GPDB. Please port this fix into HAWQ. Th > GPDB Commit: > https://github.com/greenplum-db/gpdb/commit/c0e1f00c2532d1e2ef8d3b409dc8fee901a7cfe2 > PR: https://github.com/greenplum-db/gpdb/pull/866 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq issue #1054: HAWQ-870. Allocate target's tuple table slot in ...
Github user paul-guo- commented on the issue: https://github.com/apache/incubator-hawq/pull/1054 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---