Hubspot -- >> Snowflake connection issue

Connector Questions & Issues
1
  • Is this your first time deploying Airbyte?: Yes
  • OS Version / Instance: GCP
  • Memory / Disk: 8Gb / 500 gb
  • Deployment: Kubernetes
  • Airbyte Version: 0.35.65 Alpha
  • Source name/version: Hubspot
  • Destination name/version: Snowflake
  • Step: The issue is happening during sync/ connection
  • Description: We are on the early steps on setting up airbyte open-sources connection, from Hubspot to Snowflake(GCP Server) but we are having the following error:
2022-04-26 21:01:07 INFO i.a.v.j.JsonSchemaValidator(test):56 - JSON schema validation failed. 
....	
at sun.nio.ch.NioSocketImpl.beginWrite(NioSocketImpl.java:366) ~[?:?]
		at sun.nio.ch.NioSocketImpl.implWrite(NioSocketImpl.java:411) ~[?:?]
		at sun.nio.ch.NioSocketImpl.write(NioSocketImpl.java:440) ~[?:?]
		at sun.nio.ch.NioSocketImpl$2.write(NioSocketImpl.java:826) ~[?:?]
		at java.net.Socket$SocketOutputStream.write(Socket.java:1035) ~[?:?]
		at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:234) ~[?:?]
		at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:313) ~[?:?]
		at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:318) ~[?:?]
		at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:160) ~[?:?]
		at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:248) ~[?:?]
		at java.io.BufferedWriter.flush(BufferedWriter.java:257) ~[?:?]
		at io.airbyte.workers.protocols.airbyte.DefaultAirbyteDestination.notifyEndOfStream(DefaultAirbyteDestination.java:98) ~[io.airbyte-airbyte-workers-0.35.65-alpha.jar:?]
		at io.airbyte.workers.protocols.airbyte.DefaultAirbyteDestination.close(DefaultAirbyteDestination.java:111) ~[io.airbyte-airbyte-workers-0.35.65-alpha.jar:?]
		at io.airbyte.workers.DefaultReplicationWorker.run(DefaultReplicationWorker.java:126) ~[io.airbyte-airbyte-workers-0.35.65-alpha.jar:?]
		at io.airbyte.workers.DefaultReplicationWorker.run(DefaultReplicationWorker.java:57) ~[io.airbyte-airbyte-workers-0.35.65-alpha.jar:?]
		at io.airbyte.workers.temporal.TemporalAttemptExecution.lambda$getWorkerThread$2(TemporalAttemptExecution.java:155) ~[io.airbyte-airbyte-workers-0.35.65-alpha.jar:?]
		at java.lang.Thread.run(Thread.java:833) [?:?]
2022-04-26 21:01:23 INFO i.a.w.DefaultReplicationWorker(run):228 - sync summary: io.airbyte.config.ReplicationAttemptSummary@4b54d8af[status=cancelled,recordsSynced=215387,bytesSynced=4005240457,startTime=1651003433015,endTime=1651006883193,totalStats=io.airbyte.config.SyncStats@49e93c6a[recordsEmitted=215387,bytesEmitted=4005240457,stateMessagesEmitted=0,recordsCommitted=0],streamStats=[io.airbyte.config.StreamSyncStats@12e1e49a[streamName=companies,stats=io.airbyte.config.SyncStats@474eb705[recordsEmitted=132857,bytesEmitted=1408670912,stateMessagesEmitted=<null>,recordsCommitted=<null>]], io.airbyte.config.StreamSyncStats@2a328ee3[streamName=campaigns,stats=io.airbyte.config.SyncStats@2ab8fda3[recordsEmitted=1257,bytesEmitted=621001,stateMessagesEmitted=<null>,recordsCommitted=<null>]], io.airbyte.config.StreamSyncStats@37e0095a[streamName=contact_lists,stats=io.airbyte.config.SyncStats@524763c[recordsEmitted=1574,bytesEmitted=12505286,stateMessagesEmitted=<null>,recordsCommitted=<null>]], io.airbyte.config.StreamSyncStats@3b5fb5ed[streamName=contacts,stats=io.airbyte.config.SyncStats@56e712c0[recordsEmitted=79699,bytesEmitted=2583443258,stateMessagesEmitted=<null>,recordsCommitted=<null>]]]]
2022-04-26 21:01:23 INFO i.a.w.DefaultReplicationWorker(run):250 - Source did not output any state messages
2022-04-26 21:01:23 WARN i.a.w.DefaultReplicationWorker(run):258 - State capture: No new state, falling back on input state: io.airbyte.config.State@5df40ade[state={}]

We’ve already tried 2 times recreating the connections and doing a fresh start on the Kubernetes configuration.

Any clues on what could be the issue and how to solve it? I’ve attached the log for the whole session , this source has an estimated size of 25 GB.

logs-20.txt (84.9 KB)

2

Hey looks to me like destination has timed out can you try with some smaller data and see if it is getting successfull

4

Hi there from the Community Assistance team.
We’re letting you know about an issue we discovered with the back-end process we use to handle topics and responses on the forum. If you experienced a situation where you posted the last message in a topic that did not receive any further replies, please open a new topic to continue the discussion. In addition, if you’re having a problem and find a closed topic on the subject, go ahead and open a new topic on it and we’ll follow up with you. We apologize for the inconvenience, and appreciate your willingness to work with us to provide a supportive community.