[Enhancement] Optimize OffsetStorageWriterImpl#beginFlush method handle logic

[mxsm]

Search before asking

• I had searched in the issues and found no similar issues.

Enhancement Request

eventmesh/eventmesh-openconnect/eventmesh-openconnect-offsetmgmt-plugin/eventmesh-openconnect-offsetmgmt-api/src/main/java/org/apache/eventmesh/openconnect/offsetmgmt/api/storage/OffsetStorageWriterImpl.java

Lines 85 to 95 in 291d748

	public synchronized boolean beginFlush() {
	if (isFlushing()) {
	throw new RuntimeException("OffsetStorageWriter is already flushing");
	}
	if (data.isEmpty()) {
	return false;
	}
	this.toFlush = this.data;
	this.data = new HashMap<>();
	return true;
	}

When flushing is in progress, a RuntimeException will be thrown if SourceWorker#commitOffsets method calls beginFlush. This error will propagate upwards causing the Source to exit.

Describe the solution you'd like

replace this exception with log print and return false.

I hope you understand how offsets are managed. It's not just a simple replacement.

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct *