~ubuntu-branches/ubuntu/precise/mysql-5.1/precise

is the process that is used to handle all the data in tables using the NDB Cluster storage engine\&. This is the process that empowers a data node to accomplish distributed transaction handling, node recovery, checkpointing to disk, online backup, and related tasks\&.

.PP

In a MySQL Cluster, a set of

\fBndbd\fR

processes cooperate in handling data\&. These processes can execute on the same computer (host) or on different computers\&. The correspondences between data nodes and Cluster hosts is completely configurable\&.

.\" MySQL Cluster: administration

.\" MySQL Cluster: commands

.\" command options (MySQL Cluster): ndbd

.\" MySQL Cluster: ndbd process

.PP

The following table includes command options specific to the MySQL Cluster data node program

\fBndbd\fR\&. Additional descriptions follow the table\&. For options common to all MySQL Cluster programs, see

Section\ \&17.4.2, \(lqOptions Common to MySQL Cluster Programs\(rq\&.

.if n \{\

.sp

.\}

.RS 4

.it 1 an-trap

.nr an-no-space-flag 1

.nr an-break-flag 1

.br

.ps +1

\fBNote\fR

.ps -1

.br

.PP

All of these options also apply to the multi\-threaded version of this program \(em

\fBndbmtd\fR, which is available in MySQL Cluster NDB 7\&.0 \(em and you may substitute

\(lq\fBndbmtd\fR\(rq

for

\(lq\fBndbd\fR\(rq

wherever the latter occurs in this section\&.

.sp .5v

.RE

.PP

For options common to all

NDBCLUSTER

programs, see

Section\ \&17.4.2, \(lqOptions Common to MySQL Cluster Programs\(rq\&.

.sp

.RS 4

.ie n \{\

\h'-04'\(bu\h'+03'\c

.\}

.el \{\

.sp -1

.IP \(bu 2.3

.\}

\fB\-\-bind\-address\fR

.TS

allbox tab(:);

l l s

^ l l

^ l l.

\fBVersion Introduced\fR

T}:T{

5\&.1\&.12

\fBCommand\-Line Format\fR

T}:T{

\-\-bind\-address=name

100

101

\ \&

102

T}:T{

103

\fBPermitted Values \fR

104

105

:T{

106

\fBType\fR

107

T}:T{

108

string

109

110

:T{

111

\fBDefault\fR

112

T}:T{

113

114

.TE

115

.sp 1

116

Causes

117

\fBndbd\fR

118

to bind to a specific network interface (host name or IP address)\&. This option has no default value\&.

119

.sp

120

This option was added in MySQL 5\&.1\&.12\&.

121

.RE

122

.sp

123

.RS 4

124

.ie n \{\

125

\h'-04'\(bu\h'+03'\c

126

.\}

127

.el \{\

128

.sp -1

129

.IP \(bu 2.3

130

.\}

131

\fB\-\-daemon\fR,

132

\fB\-d\fR

133

.TS

134

allbox tab(:);

135

l l s

136

l l s

137

^ l l

138

^ l l.

139

140

\fBCommand\-Line Format\fR

141

T}:T{

142

\-\-daemon

143

144

145

\ \&

146

T}:T{

147

\fBPermitted Values \fR

148

149

:T{

150

\fBType\fR

151

T}:T{

152

boolean

153

154

:T{

155

\fBDefault\fR

156

T}:T{

157

TRUE

158

159

.TE

160

.sp 1

161

Instructs

162

\fBndbd\fR

163

to execute as a daemon process\&. This is the default behavior\&.

164

\fB\-\-nodaemon\fR

165

can be used to prevent the process from running as a daemon\&.

166

.sp

167

This option has no effect when running

168

\fBndbd\fR

169

170

\fBndbmtd\fR

171

on Windows platforms\&.

172

.RE

173

.sp

174

.RS 4

175

.ie n \{\

176

\h'-04'\(bu\h'+03'\c

177

.\}

178

.el \{\

179

.sp -1

180

.IP \(bu 2.3

181

.\}

182

.\" --initial option (ndbd)

183

.\" --initial option (ndbmtd)

184

\fB\-\-initial\fR

185

.TS

186

allbox tab(:);

187

l l s

188

l l s

189

^ l l

190

^ l l.

191

192

\fBCommand\-Line Format\fR

193

T}:T{

194

\-\-initial

195

196

197

\ \&

198

T}:T{

199

\fBPermitted Values \fR

200

201

:T{

202

\fBType\fR

203

T}:T{

204

boolean

205

206

:T{

207

\fBDefault\fR

208

T}:T{

209

FALSE

210

211

.TE

212

.sp 1

213

Instructs

214

\fBndbd\fR

215

to perform an initial start\&. An initial start erases any files created for recovery purposes by earlier instances of

216

\fBndbd\fR\&. It also re\-creates recovery log files\&. Note that on some operating systems this process can take a substantial amount of time\&.

217

.sp

218

219

\fB\-\-initial\fR

220

start is to be used

221

\fIonly\fR

222

when starting the

223

\fBndbd\fR

224

process under very special circumstances; this is because this option causes all files to be removed from the Cluster file system and all redo log files to be re\-created\&. These circumstances are listed here:

225

.sp

226

.RS 4

227

.ie n \{\

228

\h'-04'\(bu\h'+03'\c

229

.\}

230

.el \{\

231

.sp -1

232

.IP \(bu 2.3

233

.\}

234

When performing a software upgrade which has changed the contents of any files\&.

235

.RE

236

.sp

237

.RS 4

238

.ie n \{\

239

\h'-04'\(bu\h'+03'\c

240

.\}

241

.el \{\

242

.sp -1

243

.IP \(bu 2.3

244

.\}

245

When restarting the node with a new version of

246

\fBndbd\fR\&.

247

.RE

248

.sp

249

.RS 4

250

.ie n \{\

251

\h'-04'\(bu\h'+03'\c

252

.\}

253

.el \{\

254

.sp -1

255

.IP \(bu 2.3

256

.\}

257

As a measure of last resort when for some reason the node restart or system restart repeatedly fails\&. In this case, be aware that this node can no longer be used to restore data due to the destruction of the data files\&.

258

.RE

259

.RS 4

260

Use of this option prevents the

261

StartPartialTimeout

262

and

263

StartPartitionedTimeout

264

configuration parameters from having any effect\&.

265

.if n \{\

266

.sp

267

.\}

268

.RS 4

269

.it 1 an-trap

270

.nr an-no-space-flag 1

271

.nr an-break-flag 1

272

.br

273

.ps +1

274

\fBImportant\fR

275

.ps -1

276

.br

277

This option does

278

\fInot\fR

279

affect either of the following:

280

.sp

281

.RS 4

282

.ie n \{\

283

\h'-04'\(bu\h'+03'\c

284

.\}

285

.el \{\

286

.sp -1

287

.IP \(bu 2.3

288

.\}

289

Backup files that have already been created by the affected node

290

.RE

291

.sp

292

.RS 4

293

.ie n \{\

294

\h'-04'\(bu\h'+03'\c

295

.\}

296

.el \{\

297

.sp -1

298

.IP \(bu 2.3

299

.\}

300

MySQL Cluster Disk Data files (see

301

Section\ \&17.5.10, \(lqMySQL Cluster Disk Data Tables\(rq)\&.

302

.RE

303

.RS 4

304

.sp

305

This option also has no effect on recovery of data by a data node that is just starting (or restarting) from data nodes that are already running\&. This recovery of data occurs automatically, and requires no user intervention in a MySQL Cluster that is running normally\&.

306

.sp .5v

307

.RE

308

It is permissible to use this option when starting the cluster for the very first time (that is, before any data node files have been created); however, it is

309

\fInot\fR

310

necessary to do so\&.

311

.RE

312

.sp

313

.RS 4

314

.ie n \{\

315

\h'-04'\(bu\h'+03'\c

316

.\}

317

.el \{\

318

.sp -1

319

.IP \(bu 2.3

320

.\}

321

.\" --initial-start option (ndbd)

322

.\" --initial-start option (ndbmtd)

323

\fB\-\-initial\-start\fR

324

.TS

325

allbox tab(:);

326

l l s

327

l l s

328

l l s

329

^ l l

330

^ l l.

331

332

\fBVersion Introduced\fR

333

T}:T{

334

5\&.1\&.11

335

336

337

\fBCommand\-Line Format\fR

338

T}:T{

339

\-\-initial\-start

340

341

342

\ \&

343

T}:T{

344

\fBPermitted Values \fR

345

346

:T{

347

\fBType\fR

348

T}:T{

349

boolean

350

351

:T{

352

\fBDefault\fR

353

T}:T{

354

FALSE

355

356

.TE

357

.sp 1

358

This option is used when performing a partial initial start of the cluster\&. Each node should be started with this option, as well as

359

\fB\-\-nowait\-nodes\fR\&.

360

.sp

361

Suppose that you have a 4\-node cluster whose data nodes have the IDs 2, 3, 4, and 5, and you wish to perform a partial initial start using only nodes 2, 4, and 5 \(em that is, omitting node 3:

362

.sp

363

.if n \{\

364

.RS 4

365

.\}

366

.nf

367

shell> \fBndbd \-\-ndb\-nodeid=2 \-\-nowait\-nodes=3 \-\-initial\-start\fR

368

shell> \fBndbd \-\-ndb\-nodeid=4 \-\-nowait\-nodes=3 \-\-initial\-start\fR

369

shell> \fBndbd \-\-ndb\-nodeid=5 \-\-nowait\-nodes=3 \-\-initial\-start\fR

370

.fi

371

.if n \{\

372

.RE

373

.\}

374

.sp

375

Prior to MySQL 5\&.1\&.19, it was not possible to perform DDL operations involving Disk Data tables on a partially started cluster\&. (See

376

\m[blue]\fBBug#24631\fR\m[]\&\s-2\u[1]\d\s+2\&.)

377

.sp

378

When using this option, you must also specify the node ID for the data node being started with the

379

\fB\-\-ndb\-nodeid\fR

380

option\&.

381

.sp

382

This option was added in MySQL 5\&.1\&.11\&.

383

.if n \{\

384

.sp

385

.\}

386

.RS 4

387

.it 1 an-trap

388

.nr an-no-space-flag 1

389

.nr an-break-flag 1

390

.br

391

.ps +1

392

\fBImportant\fR

393

.ps -1

394

.br

395

Do not confuse this option with the

396

\fB\-\-nowait\-nodes\fR

397

option added for

398

\fBndb_mgmd\fR

399

in MySQL Cluster NDB 7\&.0\&.10, which can be used to allow a cluster configured with multiple management servers to be started without all management servers being online\&.

400

.sp .5v

401

.RE

402

.RE

403

.sp

404

.RS 4

405

.ie n \{\

406

\h'-04'\(bu\h'+03'\c

407

.\}

408

.el \{\

409

.sp -1

410

.IP \(bu 2.3

411

.\}

412

.\" --nowait-nodes option (ndbd)

413

.\" --nowait-nodes option (ndbmtd)

414

\fB\-\-nowait\-nodes=\fR\fB\fInode_id_1\fR\fR\fB[, \fR\fB\fInode_id_2\fR\fR\fB[, \&.\&.\&.]]\fR

415

.TS

416

allbox tab(:);

417

l l s

418

l l s

419

l l s

420

^ l l

421

^ l l.

422

423

\fBVersion Introduced\fR

424

T}:T{

425

5\&.1\&.9

426

427

428

\fBCommand\-Line Format\fR

429

T}:T{

430

\-\-nowait\-nodes=list

431

432

433

\ \&

434

T}:T{

435

\fBPermitted Values \fR

436

437

:T{

438

\fBType\fR

439

T}:T{

440

string

441

442

:T{

443

\fBDefault\fR

444

T}:T{

445

446

.TE

447

.sp 1

448

This option takes a list of data nodes which for which the cluster will not wait for before starting\&.

449

.sp

450

This can be used to start the cluster in a partitioned state\&. For example, to start the cluster with only half of the data nodes (nodes 2, 3, 4, and 5) running in a 4\-node cluster, you can start each

451

\fBndbd\fR

452

process with

453

\fB\-\-nowait\-nodes=3,5\fR\&. In this case, the cluster starts as soon as nodes 2 and 4 connect, and does

454

\fInot\fR

455

wait

456

StartPartitionedTimeout

457

milliseconds for nodes 3 and 5 to connect as it would otherwise\&.

458

.sp

459

If you wanted to start up the same cluster as in the previous example without one

460

\fBndbd\fR

461

\(em say, for example, that the host machine for node 3 has suffered a hardware failure \(em then start nodes 2, 4, and 5 with

462

\fB\-\-nowait\-nodes=3\fR\&. Then the cluster will start as soon as nodes 2, 4, and 5 connect and will not wait for node 3 to start\&.

463

.sp

464

This option was added in MySQL 5\&.1\&.9\&.

465

.RE

466

.sp

467

.RS 4

468

.ie n \{\

469

\h'-04'\(bu\h'+03'\c

470

.\}

471

.el \{\

472

.sp -1

473

.IP \(bu 2.3

474

.\}

475

.\" --nodaemon option (ndbd)

476

.\" --nodaemon option (ndbmtd)

477

\fB\-\-nodaemon\fR

478

.TS

479

allbox tab(:);

480

l l s

481

l l s

482

^ l l

483

^ l l

484

l l s

485

^ l l

486

^ l l.

487

488

\fBCommand\-Line Format\fR

489

T}:T{

490

\-\-nodaemon

491

492

493

\ \&

494

T}:T{

495

\fBPermitted Values \fR

496

497

:T{

498

\fBType\fR

499

T}:T{

500

boolean

501

502

:T{

503

\fBDefault\fR

504

T}:T{

505

FALSE

506

507

508

\ \&

509

T}:T{

510

\fBPermitted Values \fR

511

512

:T{

513

\fBType\fR (windows)

514

T}:T{

515

boolean

516

517

:T{

518

\fBDefault\fR

519

T}:T{

520

TRUE

521

522

.TE

523

.sp 1

524

Instructs

525

\fBndbd\fR

526

not to start as a daemon process\&. This is useful when

527

\fBndbd\fR

528

is being debugged and you want output to be redirected to the screen\&.

529

.sp

530

As of MySQL Cluster NDB 7\&.0\&.8, the default behavior for

531

\fBndbd\fR

532

and

533

\fBndbmtd\fR

534

on Windows is to run in the foreground, making this option unnecessary on Windows platforms\&. (\m[blue]\fBBug#45588\fR\m[]\&\s-2\u[2]\d\s+2)

535

.RE

536

.sp

537

.RS 4

538

.ie n \{\

539

\h'-04'\(bu\h'+03'\c

540

.\}

541

.el \{\

542

.sp -1

543

.IP \(bu 2.3

544

.\}

545

.\" --nostart option (ndbd)

546

.\" -n option (ndbd)

547

.\" --nostart option (ndbmtd)

548

.\" -n option (ndbmtd)

549

\fB\-\-nostart\fR,

550

\fB\-n\fR

551

.TS

552

allbox tab(:);

553

l l s

554

l l s

555

^ l l

556

^ l l.

557

558

\fBCommand\-Line Format\fR

559

T}:T{

560

\-\-nostart

561

562

563

\ \&

564

T}:T{

565

\fBPermitted Values \fR

566

567

:T{

568

\fBType\fR

569

T}:T{

570

boolean

571

572

:T{

573

\fBDefault\fR

574

T}:T{

575

FALSE

576

577

.TE

578

.sp 1

579

Instructs

580

\fBndbd\fR

581

not to start automatically\&. When this option is used,

582

\fBndbd\fR

583

connects to the management server, obtains configuration data from it, and initializes communication objects\&. However, it does not actually start the execution engine until specifically requested to do so by the management server\&. This can be accomplished by issuing the proper

584

START

585

command in the management client (see

586

Section\ \&17.5.2, \(lqCommands in the MySQL Cluster Management Client\(rq)\&.

587

.RE

588

.\" MySQL Cluster: log files

589

.\" log files (MySQL Cluster)

590

.PP

591

\fBndbd\fR

592

generates a set of log files which are placed in the directory specified by

593

DataDir

594

in the

595

config\&.ini

596

configuration file\&.

597

.PP

598

These log files are listed below\&.

599

\fInode_id\fR

600

is the node\'s unique identifier\&. Note that

601

\fInode_id\fR

602

represents the node\'s unique identifier\&. For example,

603

ndb_2_error\&.log

604

is the error log generated by the data node whose node ID is

605

2\&.

606

.sp

607

.RS 4

608

.ie n \{\

609

\h'-04'\(bu\h'+03'\c

610

.\}

611

.el \{\

612

.sp -1

613

.IP \(bu 2.3

614

.\}

615

.\" MySQL Cluster: error logs

616

.\" error logs (MySQL Cluster)

617

ndb_\fInode_id\fR_error\&.log

618

is a file containing records of all crashes which the referenced

619

\fBndbd\fR

620

process has encountered\&. Each record in this file contains a brief error string and a reference to a trace file for this crash\&. A typical entry in this file might appear as shown here:

621

.sp

622

.if n \{\

623

.RS 4

624

.\}

625

.nf

626

Date/Time: Saturday 30 July 2004 \- 00:20:01

627

Type of error: error

628

Message: Internal program error (failed ndbrequire)

629

Fault ID: 2341

630

Problem data: DbtupFixAlloc\&.cpp

631

Object of reference: DBTUP (Line: 173)

632

ProgramName: NDB Kernel

633

ProcessID: 14909

634

TraceFile: ndb_2_trace\&.log\&.2

635

***EOM***

636

.fi

637

.if n \{\

638

.RE

639

.\}

640

.sp

641

Listings of possible

642

\fBndbd\fR

643

exit codes and messages generated when a data node process shuts down prematurely can be found in

644

\m[blue]\fBndbd Error Messages\fR\m[]\&\s-2\u[3]\d\s+2\&.

645

.if n \{\

646

.sp

647

.\}

648

.RS 4

649

.it 1 an-trap

650

.nr an-no-space-flag 1

651

.nr an-break-flag 1

652

.br

653

.ps +1

654

\fBImportant\fR

655

.ps -1

656

.br

657

\fIThe last entry in the error log file is not necessarily the newest one\fR

658

(nor is it likely to be)\&. Entries in the error log are

659

\fInot\fR

660

listed in chronological order; rather, they correspond to the order of the trace files as determined in the

661

ndb_\fInode_id\fR_trace\&.log\&.next

662

file (see below)\&. Error log entries are thus overwritten in a cyclical and not sequential fashion\&.

663

.sp .5v

664

.RE

665

.RE

666

.sp

667

.RS 4

668

.ie n \{\

669

\h'-04'\(bu\h'+03'\c

670

.\}

671

.el \{\

672

.sp -1

673

.IP \(bu 2.3

674

.\}

675

.\" MySQL Cluster: trace files

676

.\" trace files (MySQL Cluster)

677

ndb_\fInode_id\fR_trace\&.log\&.\fItrace_id\fR

678

is a trace file describing exactly what happened just before the error occurred\&. This information is useful for analysis by the MySQL Cluster development team\&.

679

.sp

680

It is possible to configure the number of these trace files that will be created before old files are overwritten\&.

681

\fItrace_id\fR

682

is a number which is incremented for each successive trace file\&.

683

.RE

684

.sp

685

.RS 4

686

.ie n \{\

687

\h'-04'\(bu\h'+03'\c

688

.\}

689

.el \{\

690

.sp -1

691

.IP \(bu 2.3

692

.\}

693

ndb_\fInode_id\fR_trace\&.log\&.next

694

is the file that keeps track of the next trace file number to be assigned\&.

695

.RE

696

.sp

697

.RS 4

698

.ie n \{\

699

\h'-04'\(bu\h'+03'\c

700

.\}

701

.el \{\

702

.sp -1

703

.IP \(bu 2.3

704

.\}

705

ndb_\fInode_id\fR_out\&.log

706

is a file containing any data output by the

707

\fBndbd\fR

708

process\&. This file is created only if

709

\fBndbd\fR

710

is started as a daemon, which is the default behavior\&.

711

.RE

712

.sp

713

.RS 4

714

.ie n \{\

715

\h'-04'\(bu\h'+03'\c

716

.\}

717

.el \{\

718

.sp -1

719

.IP \(bu 2.3

720

.\}

721

ndb_\fInode_id\fR\&.pid

722

is a file containing the process ID of the

723

\fBndbd\fR

724

process when started as a daemon\&. It also functions as a lock file to avoid the starting of nodes with the same identifier\&.

725

.RE

726

.sp

727

.RS 4

728

.ie n \{\

729

\h'-04'\(bu\h'+03'\c

730

.\}

731

.el \{\

732

.sp -1

733

.IP \(bu 2.3

734

.\}

735

ndb_\fInode_id\fR_signal\&.log

736

is a file used only in debug versions of

737

\fBndbd\fR, where it is possible to trace all incoming, outgoing, and internal messages with their data in the

738

\fBndbd\fR

739

process\&.

740

.RE

741

.PP

742

It is recommended not to use a directory mounted through NFS because in some environments this can cause problems whereby the lock on the

743

\&.pid

744

file remains in effect even after the process has terminated\&.

745

.PP

746

To start

747

\fBndbd\fR, it may also be necessary to specify the host name of the management server and the port on which it is listening\&. Optionally, one may also specify the node ID that the process is to use\&.

748

.sp

749

.if n \{\

750

.RS 4

751

.\}

752

.nf

753

shell> \fBndbd \-\-connect\-string="nodeid=2;host=ndb_mgmd\&.mysql\&.com:1186"\fR

754

.fi

755

.if n \{\

756

.RE

757

.\}

758

.PP

759

See

760

Section\ \&17.3.2.3, \(lqThe MySQL Cluster Connectstring\(rq, for additional information about this issue\&.

761

\fBndbd\fR(8), describes other options for

762

\fBndbd\fR\&.

763

.PP

764

When

765

\fBndbd\fR

766

starts, it actually initiates two processes\&. The first of these is called the

767

\(lqangel process\(rq; its only job is to discover when the execution process has been completed, and then to restart the

768

\fBndbd\fR

769

process if it is configured to do so\&. Thus, if you attempt to kill

770

\fBndbd\fR

771

via the Unix

772

\fBkill\fR

773

command, it is necessary to kill both processes, beginning with the angel process\&. The preferred method of terminating an

774

\fBndbd\fR

775

process is to use the management client and stop the process from there\&.

776

.PP

777

The execution process uses one thread for reading, writing, and scanning data, as well as all other activities\&. This thread is implemented asynchronously so that it can easily handle thousands of concurrent actions\&. In addition, a watch\-dog thread supervises the execution thread to make sure that it does not hang in an endless loop\&. A pool of threads handles file I/O, with each thread able to handle one open file\&. Threads can also be used for transporter connections by the transporters in the

778

\fBndbd\fR

779

process\&. In a multi\-processor system performing a large number of operations (including updates), the

780

\fBndbd\fR

781

process can consume up to 2 CPUs if permitted to do so\&.

782

.PP

783

For a machine with many CPUs it is possible to use several

784

\fBndbd\fR

785

processes which belong to different node groups; however, such a configuration is still considered experimental and is not supported for MySQL 5\&.1 in a production setting\&. See

786

Section\ \&17.1.5, \(lqKnown Limitations of MySQL Cluster\(rq\&.

787

.SH "COPYRIGHT"

788

.br

789

.PP

790

791

.PP

792

This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.

793

.PP

794

This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

795

.PP

796

You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA or see http://www.gnu.org/licenses/.

797

.sp

798

.SH "NOTES"

799

.IP " 1." 4

800

Bug#24631

801

.RS 4

802

\%http://bugs.mysql.com/bug.php?id=24631

803

.RE

804

.IP " 2." 4

805

Bug#45588

806

.RS 4

807

\%http://bugs.mysql.com/bug.php?id=45588

808

.RE

809

.IP " 3." 4

810

ndbd Error Messages

811

.RS 4

812

\%http://dev.mysql.com/doc/ndbapi/en/ndbd-error-messages.html

813

.RE

814

.SH "SEE ALSO"

815

For more information, please refer to the MySQL Reference Manual,

816

which may already be installed locally and which is also available

817

online at http://dev.mysql.com/doc/.

818

.SH AUTHOR

819

Sun Microsystems, Inc. (http://www.mysql.com/).

Older »