"No mapping between account names and security IDs was done.", "The security ID structure is invalid.",
            "The file system is full.", "All pipe instances are busy.", "All pipe instances are busy.", "The pipe state is invalid.",
            "All pipe instances are busy.", "No process is on the other end of the pipe.", "The pipe is being closed.",

            "No mapping between account names and security IDs was done.", "The security ID structure is invalid.",
            "All pipe instances are busy.", "All pipe instances are busy.", "The pipe state is invalid.", "All pipe instances are busy.",
            "No process is on the other end of the pipe.", "The pipe is being closed.",

    @Test
    @DisplayName("Should track elapsed time")
    void testElapsedTime() throws InterruptedException {
        // Given
        exception = new SmbOperationException(SmbOperationException.ErrorCode.BUSY, "Server busy");

        // When
        Thread.sleep(100);

        // Then
        assertTrue(exception.getElapsedTime() >= 100);
        assertTrue(exception.getElapsedTime() < 200);
    }

    @Test

                true), RESOURCE_LOCKED("Resource is locked", ErrorCategory.RESOURCE, true),

        // Transient errors
        BUSY("Server busy", ErrorCategory.TRANSIENT, true), TRY_AGAIN("Try again later", ErrorCategory.TRANSIENT,
                true), SERVICE_UNAVAILABLE("Service temporarily unavailable", ErrorCategory.TRANSIENT, true),

        // Generic errors

     *
     * @return channel score
     */
    public int getScore() {
        int score = 100;

        // Adjust based on state
        if (state == ChannelState.ACTIVE)
            score -= 20; // Busy channel penalty
        if (state != ChannelState.ESTABLISHED && state != ChannelState.ACTIVE)
            return 0;

        // Adjust based on error rate
        double errorRate = getErrorRate();

      if (compareAndSet(currentRunner, blocker)) {
        // Thread.interrupt can throw arbitrary exceptions due to the nio InterruptibleChannel API
        // This will make sure that tasks don't get stuck busy waiting.
        // Some of this is fixed in jdk11 (see https://bugs.openjdk.org/browse/JDK-8198692) but
        // not all.  See the test cases for examples on how this can happen.
        try {

    
    public int getScore() {
        // Calculate channel score for load balancing
        int score = 100;
        
        // Adjust based on state
        if (state == ChannelState.ACTIVE) score -= 20;  // Busy channel
        if (state != ChannelState.ESTABLISHED && state != ChannelState.ACTIVE) return 0;
        
        // Adjust based on error rate
        double errorRate = getErrorRate();

//
//	Generic S3 HTTP handler errors.
//
// //////////////////////////////////////////////////////////////////////
func errBusy(err error) *s3Error {
	return &s3Error{
		code:       "Busy",
		message:    "The service is unavailable. Please retry.",
		statusCode: 503,
		cause:      err,
	}
}

func errUnauthorizedAccess(err error) *s3Error {
	return &s3Error{

   * requests become more likely to trigger expensive operations (a more extreme case of this
   * example is when a server has just booted, and it is mostly busy with getting itself up to
   * speed).
   *
   * To deal with such scenarios, we add an extra dimension, that of "past underutilization",

		readsAwait:        "Average time for read requests to be served on a drive",
		writesAwait:       "Average time for write requests to be served on a drive",
		percUtil:          "Percentage of time the disk was busy",
		usedBytes:         "Used bytes on a drive",
		totalBytes:        "Total bytes on a drive",
		usedInodes:        "Total inodes used on a drive",
		totalInodes:       "Total inodes on a drive",