## Nim - the first high performance language with full support for hot codereloading at runtime by Viktor Kirilov ## Me, myself and I • my name is Viktor Kirilov - from Bulgaria • creator of doctest performant programming language landscape - read: heavily biased C++ rant • Nim compilation model • hot code reloading ☐ usage & implementation ☐ ".dll" => assume .so/.dylib (platform-agnostic) libraries OR hot-patching: ☐ possible for decades - but not widely used ■ usually quite intrusive (interfaces, constraints, complicated setup) ☐ in game engines: Unreal, others... ■ hot-patching (with

Checkpoints.....435 18.5.3. Archiving .....436 18.5.4. Streaming Replication.....437 18.5.5. Standby Servers .....438 18.6. Query Planning .....438 18.6.1. Planner Method Configuration.....439 526 24.3.4. Timelines ..... 528 24.3.5. Tips and Examples ..... 529 24.3.5.1. Standalone hot backups ..... 529 24.3.5.2. Compressed Archive Logs ..... 529 24.3.5.3. archive_command scripts Log-Shipping Standby Servers.....538 25.2.1. Planning.....538 25.2.2. Standby Server Operation.....539 25.2.3. Preparing the Master for Standby Servers.....539 25.2.4. Setting Up a Standby Server

Checkpoints ..... 406 18.5.3. Archiving ..... 407 18.5.4. Streaming Replication ..... 407 18.5.5. Standby Servers ..... 408 18.6. Query Planning ..... 409 18.6.1. Planner Method Configuration ..... 409 492 24.3.4. Timelines ..... 493 24.3.5. Tips and Examples ..... 494 24.3.5.1. Standalone hot backups ..... 494 24.3.5.2. Compressed Archive Logs ..... 495 24.3.5.3. archive_command scripts 499 25.2. Log-Shipping Standby Servers ..... 502 25.2.1. Planning ..... 503 25.2.2. Standby Server Operation ..... 503 25.2.3. Preparing the Master for Standby Servers ..... 504 25.2

214:2181/;serviceDiscoveryMode=zooKeeper; →zooKeeperNamespace=kyuubi' -n kentyao ## How to Hot Upgrade Kyuubi Server Kyuubi supports hot upgrade one of server in a HA cluster which is transparent to users. • If you ThriftServer, namely Active/Standby and LoadBalancing. The Active/Standby mode consists of active Spark ThriftServer and several standby servers. When the active crashes or hangs, the standby nodes trigger the active server to handle the coming flood of client retries. It's very likely to crash again. The Standby node causes serious waste of cluster resources, whether Spark dynamic resource allocation is enabled

calling `subject$.next(value)` • Have all operators on them any observable would • Multicast, or hot ## I mporting RxJS … this is where a lot of people make a mistake. A^s puns.component.ts

Replication.....493 18.6.1. Sending Server(s).....493 18.6.2. Master Server.....494 18.6.3. Standby Servers.....495 18.7. Query Planning.....496 18.7.1. Planner Method Configuration.....496 .....593 24.3.5. Timelines .....594 24.3.6. Tips and Examples .....595 24.3.6.1. Standalone Hot Backups .....595 24.3.6.2. Compressed Archive Logs .....596 24.3.6.3. archive_command Scripts Log-Shipping Standby Servers .....602 25.2.1. Planning .....602 25.2.2. Standby Server Operation .....603 25.2.3. Preparing the Master for Standby Servers .....603 25.2.4. Setting Up a Standby Server

Replication.....448 18.6.1. Sending Server(s).....449 18.6.2. Master Server.....449 18.6.3. Standby Servers.....450 18.7. Query Planning.....451 18.7.1. Planner Method Configuration.....452 541 24.3.5. Timelines ..... 542 24.3.6. Tips and Examples ..... 543 24.3.6.1. Standalone Hot Backups ..... 543 24.3.6.2. Compressed Archive Logs ..... 544 24.3.6.3. archive_command Scripts 546 25.2. Log-Shipping Standby Servers ..... 549 25.2.1. Planning ..... 550 25.2.2. Standby Server Operation ..... 550 25.2.3. Preparing the Master for Standby Servers ..... 551 25.2

Replication .....478 18.6.1. Sending Server(s) .....479 18.6.2. Master Server .....479 18.6.3. Standby Servers .....480 18.7. Query Planning .....482 18.7.1. Planner Method Configuration .... .....576 24.3.5. Timelines .....578 24.3.6. Tips and Examples .....579 24.3.6.1. Standalone Hot Backups .....579 24.3.6.2. Compressed Archive Logs .....580 24.3.6.3. archive_command Scripts 582 25.2. Log-Shipping Standby Servers .....586 25.2.1. Planning .....586 25.2.2. Standby Server Operation .....587 25.2.3. Preparing the Master for Standby Servers .....587 25.2.4

3. Archiving ..... 453 18.6. Replication ..... 454 18.6.1. Master Server ..... 454 18.6.2. Standby Servers ..... 456 18.7. Query Planning ..... 457 18.7.1. Planner Method Configuration ..... 457 551 24.3.4. Timelines .....553 24.3.5. Tips and Examples .....554 24.3.5.1. Standalone Hot Backups .....554 24.3.5.2. Compressed Archive Logs .....555 24.3.5.3. archive_command Scripts 557 25.2. Log-Shipping Standby Servers .....561 25.2.1. Planning .....561 25.2.2. Standby Server Operation .....562 25.2.3. Preparing the Master for Standby Servers .....562 25.2.4

Replication ..... 512 18.6.1. Sending Server(s) ..... 512 18.6.2. Master Server ..... 513 18.6.3. Standby Servers ..... 514 18.7. Query Planning ..... 515 18.7.1. Planner Method Configuration ..... 516 .. 609 24.3.5. Timelines ..... 611 24.3.6. Tips and Examples ..... 612 24.3.6.1. Standalone Hot Backups ..... 612 24.3.6.2. Compressed Archive Logs ..... 613 24.3.6.3. archive_command Scripts Log-Shipping Standby Servers ..... 618 25.2.1. Planning ..... 619 25.2.2. Standby Server Operation ..... 619 25.2.3. Preparing the Master for Standby Servers ..... 620 25.2.4. Setting Up a Standby Server