Android embedded client triggers EDIAG logs, timeout, and abort on second startup if previous instance is not fully cleaned up

Open
#353 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
android, cpp
Domain
embedded-iot, mobile-dev

Research direction

Start by reproducing the second startup of libembedded_client.so in the Android virtual environment, using the same data directory before the first instance has fully exited. Trace the client startup and shutdown entry points and inspect the EDIAG, OB_TRANS_TIMEOUT (4012), and abort sequence. Done means the overlapping startup is handled without the reported timeout and process abort.

Written by the indexing model from the issue text.

Description

dima

Description

In an Android virtual environment, after the libembedded_client.so successfully starts for the first time, if a second instance is started using the same data directory before the previous instance has fully exited, a large number of EDIAG logs are generated. This is followed by an OB_TRANS_TIMEOUT (4012) error, and the process ultimately aborts.

Environment

  • Machine: 30.249.210.127
  • Environment: Android Virtual Device created by Android Studio
  • Package Name: com.seek...
Dominant language
C++
Stars
2.9k
Forks
342
Avg merge
2d 14h
Merged PRs (30d)
53

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from oceanbase/seekdb

All issues in oceanbase/seekdb

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.