// start one new transaction per invocation. On the other hand a busy
// system will generate many IO events and this method will be called
// frequently. It will likely achieve max transactions quickly on its own.
- if (getQueueCount() > 0) {
+ if (getQueueCount() > 0) {
if (getTransactionCount() >= max_transactions_) {
LOG_DEBUG(dhcp_to_d2_logger, isc::log::DBGLVL_TRACE_DETAIL_DATA,
DHCP_DDNS_AT_MAX_TRANSACTIONS).arg(getQueueCount())
while (it != transaction_list_.end()) {
NameChangeTransactionPtr trans = (*it).second;
if (trans->isModelDone()) {
- // @todo Additional actions based on NCR status could be
+ // @todo Additional actions based on NCR status could be
// performed here.
transaction_list_.erase(it++);
} else {
void D2UpdateMgr::pickNextJob() {
// Start at the front of the queue, looking for the first entry for
// which no transaction is in progress. If we find an eligible entry
- // remove it from the queue and make a transaction for it. If the
+ // remove it from the queue and make a transaction for it. If the
// transaction creation fails try the next entry in the queue.
// Requests and transactions are associated by DHCID. If a request has
// the same DHCID as a transaction, they are presumed to be for the same
/// transactions.
///
/// As part of the process of forming transactions, D2UpdateMgr matches each
-/// request with the appropriate list of DNS servers. This matching is based
+/// request with the appropriate list of DNS servers. This matching is based
/// upon request attributes, primarily the FQDN and update direction (forward
/// or reverse). D2UpdateMgr uses the services of D2CfgMgr to match requests
/// to DNS server lists.
/// Once created, each transaction is responsible for carrying out the steps
/// required to fulfill its specific request. These steps typically consist of
/// one or more DNS packet exchanges with the appropriate DNS server. As
-/// transactions complete, D2UpdateMgr removes them from the transaction list,
+/// transactions complete, D2UpdateMgr removes them from the transaction list,
/// replacing them with new transactions.
///
/// D2UpdateMgr carries out each of the above steps, with a method called
" \"ddns-domains\": [ "
" { \"name\": \"example.com.\" , "
" \"dns-servers\" : [ "
- " { \"ip-address\": \"127.0.0.1\", \"port\" : 5301 } "
+ " { \"ip-address\": \"127.0.0.1\", \"port\" : 5301 } "
" ] },"
" { \"name\": \"org.\" , "
" \"dns-servers\" : [ "
// test (currently, multiTransactionTimeout).
if (passes > max_passes) {
FAIL() << "processALL failed, too many passes: "
- << passes << ", total handlers executed: " << handlers;
+ << passes << ", total handlers executed: " << handlers;
}
}
}
update_mgr->getMaxTransactions());
- // Verify that constructor permits custom max transactions.
+ // Verify that constructor permits custom max transactions.
ASSERT_NO_THROW(update_mgr.reset(new D2UpdateMgr(queue_mgr, cfg_mgr,
io_service, 100)));
// Verify that the queue has been drained.
EXPECT_EQ(0, update_mgr_->getQueueCount());
- // Now verify that a subsequent request for a DCHID for which a
+ // Now verify that a subsequent request for a DCHID for which a
// transaction is in progress, is not dequeued.
// First add the "subsequent" request.
dhcp_ddns::NameChangeRequestPtr