-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Open
Labels
area/ysqlYugabyte SQL (YSQL)Yugabyte SQL (YSQL)kind/bugThis issue is a bugThis issue is a bugkind/failing-testTests and testing infraTests and testing infrapriority/mediumMedium priority issueMedium priority issueqa_automationBugs identified via itest-system, LST, Stress automation or causing automation failuresBugs identified via itest-system, LST, Stress automation or causing automation failures
Description
Jira Link: DB-2757
Description
SQLsmith found this, happens sometimes when tserver is shutting down due to #11233 , but I can't reproduce it.
TRAP: FailedAssertion("!(bms_is_subset(appendrel->lateral_relids, required_outer))", File: "../../../../../../../src/postgres/src/backend/optimizer/util/relnode.c", Line: 1543)
2022-01-26 22:05:00.671 CET [82150] WARNING: there is no transaction in progress
2022-01-26 22:05:00.671 CET [63131] LOG: server process (PID 82149) was terminated by signal 6: Abort trap
2022-01-26 22:05:00.671 CET [63131] DETAIL: Failed process was running: select
subq_0.c4 as c0,
ref_1.datallowconn as c1,
74 as c2,
subq_1.c0 as c3
from
(select
ref_0.indexrelname as c0,
ref_0.relid as c1,
ref_0.indexrelname as c2,
37 as c3,
ref_0.relid as c4
from
pg_catalog.pg_statio_sys_indexes as ref_0
where true
limit 93) as subq_0
inner join pg_catalog.pg_database as ref_1
on (subq_0.c3 = ref_1.encoding ),
lateral (select
subq_0.c2 as c0
from
information_schema.role_column_grants as ref_2
right join pg_catalog.pg_file_settings as ref_3
on (ref_1.datistemplate is NULL)
where cast(null as tinterval) #<> cast(null as reltime)) as subq_1
where ((select sent_lsn from pg_catalog.pg_stat_replication limit 1 offset 3)
< pg_catalog.pg_current_wal_flush_lsn())
and ((select type from pg_catalog.pg_hba_file_rules limit 1 offset 1)
>= cast(nullif(cast(null as text),
cast(null as text)) as text))
lim
2022-01-26 22:05:00.671 CET [63131] LOG: terminating any other active server processes
2022-01-26 22:05:00.671 CET [82150] WARNING: terminating connection because of crash of another server process
2022-01-26 22:05:00.671 CET [82150] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2022-01-26 22:05:00.671 CET [82150] HINT: In a moment you should be able to reconnect to the database and repeat your command.
TRAP: BadArgument("!(((context) != ((void*)0) && (((((const Node*)((context)))->type) == T_AllocSetContext) || ((((const Node*)((context)))->type) == T_SlabContext) || ((((const Node*)((context)))->type) == T_GenerationContext))))", File: "../../../../../../../src/postgres/src/include/utils/memutils.h", Line: 134)
2022-01-26 22:05:00.671 CET [82152] WARNING: terminating connection because of crash of another server process
2022-01-26 22:05:00.671 CET [82152] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2022-01-26 22:05:00.671 CET [82152] HINT: In a moment you should be able to reconnect to the database and repeat your command.
2022-01-26 22:05:00.671 CET [82148] WARNING: terminating connection because of crash of another server process
2022-01-26 22:05:00.671 CET [82148] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2022-01-26 22:05:00.671 CET [82148] HINT: In a moment you should be able to reconnect to the database and repeat your command.
2022-01-26 22:05:00.671 CET [82147] WARNING: terminating connection because of crash of another server process
2022-01-26 22:05:00.671 CET [82147] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2022-01-26 22:05:00.671 CET [82147] HINT: In a moment you should be able to reconnect to the database and repeat your command.
I0126 22:05:00.671818 1869312000 poller.cc:66] Poll stopped: Service unavailable (yb/rpc/scheduler.cc:80): Scheduler is shutting down (system error 58)
W0126 22:05:00.671958 1869885440 outbound_call.cc:131] Failed to schedule invoking callback on response for request yb.tserver.TabletServerService.Read to 127.0.0.1: Aborted (yb/rpc/thread_pool.cc:260): Service is shutting down
I0126 22:05:00.671972 1868165120 poller.cc:66] Poll stopped: Service unavailable (yb/rpc/scheduler.cc:80): Scheduler is shutting down (system error 58)
I0126 22:05:00.672281 1868738560 poller.cc:66] Poll stopped: Service unavailable (yb/rpc/scheduler.cc:80): Scheduler is shutting down (system error 58)
W0126 22:05:00.672427 1869885440 rpc.cc:179] Aborted (yb/rpc/rpc.cc:178): Failed to schedule: 0x0000000125e105b8 -> Read(tablet: 00000000000000000000000000000000, num_ops: 1, num_attempts: 2, txn: 00000000-0000-0000-0000-000000000000, subtxn: [none])
I0126 22:05:00.672461 1868738560 poller.cc:66] Poll stopped: Service unavailable (yb/rpc/scheduler.cc:80): Scheduler is shutting down (system error 58)
2022-01-26 22:05:00.676 CET [63131] LOG: all server processes terminated; reinitializing
The context null pointer looks like it could cause more trouble in Release builds too.
Metadata
Metadata
Assignees
Labels
area/ysqlYugabyte SQL (YSQL)Yugabyte SQL (YSQL)kind/bugThis issue is a bugThis issue is a bugkind/failing-testTests and testing infraTests and testing infrapriority/mediumMedium priority issueMedium priority issueqa_automationBugs identified via itest-system, LST, Stress automation or causing automation failuresBugs identified via itest-system, LST, Stress automation or causing automation failures