You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The default/example table source files include a semaphore name - cf_1_sem and cf_2_sem - for throttling on channel 1 and 2, respectively.
However, CF does not actually create the throttling semaphores, it expects the semaphore to be created before CF starts. If a new user is starting CF by itself with no other support apps running, this semaphore will not exist.
Describe the solution you'd like
To make it simpler to build and run CF with a default configuration, the example table should have an empty string for the semaphore name - this means no throttle.
Additional context
This will make CF at least boot up and load "out of the box" ... but probably any real deployment will need a throttle, so this means that we don't have an example of a throttling semaphore anymore.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered:
Unless something actually instantiates this semaphore, this
prevents CF from initializing correctly.
With this, at least CF should start up with the out-of-box config.
Is your feature request related to a problem? Please describe.
The default/example table source files include a semaphore name - cf_1_sem and cf_2_sem - for throttling on channel 1 and 2, respectively.
However, CF does not actually create the throttling semaphores, it expects the semaphore to be created before CF starts. If a new user is starting CF by itself with no other support apps running, this semaphore will not exist.
Describe the solution you'd like
To make it simpler to build and run CF with a default configuration, the example table should have an empty string for the semaphore name - this means no throttle.
Additional context
This will make CF at least boot up and load "out of the box" ... but probably any real deployment will need a throttle, so this means that we don't have an example of a throttling semaphore anymore.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: